Even pros fuck up. I know of one very capable embedded guy who supports multiple companies, who has at least one or two colossal fuckups during the course of a project. His fuckups are usually several layers deep involving complicated interactions between modules or rare stackups, that only uGod himself would have forseen.
However, the fuckups I see today in commercially released software are superficial fuckups; obvious errors that students learn about their first two weeks. For example, I've seen this particular error SO MANY F-ING TIMES:
object reference not set to an instance of an object
If you know what that error means, enough said.
Don't get me started on the stupid shit the MS Office I'm forced to use does on a regular basis...
object reference? He's doing embedded in something other than C??
No, I was giving two examples. One example in embedded land, where the fuckup is several layers deep, where even an expert would struggle to catch it. These errors get caught by skilled pros, we don't see these too often.
The other example I gave was a toilet-paper degree H1B pajeet programming in C# for example, who has absolutely no clue what the fuck he's doing. These errors are being shipped out the door on a regular basis.
(post is archived)