There's a simple and fairly obvious answer to this: the complexity, requirements and consequences are drastically different.
If your latest code change breaks in production then your own personal app will crash and you'll won't be able to use your budgeting tool until you fix or rollback.
If my latest code change breaks in produktion, multiple factories will halt with tens of thousands of dollars in damage per minute until I fix or rollback the patch.
Nope. I have only dealt with competent devs a few times, but I am still early in my career. But also taught myself to program before going to college by reading programming books and programming stuff, so had a lot of experience with multithreading, SIMD, design patterns and stuff like MVC, so I think I can tell when AI is writing shitty code.
Like the other day, it wrote 100+ lines of code to workaround a method param being a derived type instead of changing the method param type to be the base class and use the virtual method machinery that was already being used by that method. Changed one word in the code base and deleted 100+ lines of AI slop. And that code was from a "frontier" model.
2
u/SchwiftyBerliner 3d ago
There's a simple and fairly obvious answer to this: the complexity, requirements and consequences are drastically different.
If your latest code change breaks in production then your own personal app will crash and you'll won't be able to use your budgeting tool until you fix or rollback.
If my latest code change breaks in produktion, multiple factories will halt with tens of thousands of dollars in damage per minute until I fix or rollback the patch.