Because companies don't care about how 'clean' you code is, what design patterns you use or what cool new technology you are using. They just care that you manage to release quickly so the company can start making money.
So even if you don't know the best way to do things or the best pattern to use, as long as you can hack something together that works reasonably well for some time then you're good enough. Sure, it might be flimsy, break easily, unreadable etc. but if the company is making money then business is happy.
Think about it...code becomes legacy so quickly. 2-3 year old code is considered legacy, especially if it's not used/modified much. You could have spent 15% more time to make it more maintainable but it will still be considered bad code by the next guy who had to work on it because he has absolutely no idea how the code works and what it is meant to do. Chances are, it would be re-written anyway even if you spent that extra 15%. The in the meantime the company might have missed their initial release date and some potential revenue.
Not saying I agree with it but that is how it is unfortunately.
I tested this. It asked for a shovel and I drew an aeroplane and it guessed aeroplane. I did the same thing a number of times and I got around a 60% correct response rate.
I'm not sure if I am understanding it well. Does the EU have an issue with Google Chrome coming pre-installed with Android? In that case, shouldn't Microsoft face the same penalties since IE/Edge comes pre-installed on the Windows OS? I believe that these pre-installed apps can't be uninstalled (because it might happen that you end up with no browsers on your phone), but would making the app uninstallable solve this issue? I know that on Windows I only use IE to install Chrome, then I ignore it for ever.
I think that it is only fair that Android are allowed to bundle soft of their software with each Android release. Then again, I hate bloat ware so I kind of understand that point of view too. Maybe Android versions can ship a blank OS (no pre-bundled apps) and you have the option to opt-in to a 'suggested' package which would include apps such as Chrome, search function etc.
I'm not 100% sure I understood the EU commission's problem here (or rather why they targeted specifically Android/Google). Feel free to correct me where I am wrong.
So even if you don't know the best way to do things or the best pattern to use, as long as you can hack something together that works reasonably well for some time then you're good enough. Sure, it might be flimsy, break easily, unreadable etc. but if the company is making money then business is happy.
Think about it...code becomes legacy so quickly. 2-3 year old code is considered legacy, especially if it's not used/modified much. You could have spent 15% more time to make it more maintainable but it will still be considered bad code by the next guy who had to work on it because he has absolutely no idea how the code works and what it is meant to do. Chances are, it would be re-written anyway even if you spent that extra 15%. The in the meantime the company might have missed their initial release date and some potential revenue.
Not saying I agree with it but that is how it is unfortunately.