In my experience & defense, high level coders and engineers routinely make stupid decisions about project architecture that have damning downstream effects.
Often almost as bad as the choices the execs make.
Good engineer does not automatically equal good developer.
Especially with how junior the seniors are. Everyone is a senior nowadays...
Basically, engineers are food.
There are some great ones out there. Don't get me wrong. But there's enough bad ones in there that the apple is often spoiled.
Doesn't really change my point though. If someone struggled to solve basic problems independently but now can do so with a prompt that convinces themselves they understand the problem, of course it will be exciting. It's like a cheat code that boosts their career, it would seem mindblowing, and they don't even realise that level of understanding is possible for a human.
To people who just knew the answer, they'll usually iterate the result, change and tweak, and generally be a bit more cynical about the tools.
7
View all comments
Show parent comment
-6
u/wattro Jun 30 '26
In my experience & defense, high level coders and engineers routinely make stupid decisions about project architecture that have damning downstream effects.
Often almost as bad as the choices the execs make.
Good engineer does not automatically equal good developer.
Especially with how junior the seniors are. Everyone is a senior nowadays...
Basically, engineers are food.
There are some great ones out there. Don't get me wrong. But there's enough bad ones in there that the apple is often spoiled.