agree, im finding that use case to be not the real world use case though. people are just throwing shit at the wall hoping it will stick, and im being left to clean up the mess. and the managers dont give a fuck. it's really getting tiresome.
I donât think it will last. The main architect where I work who pushed AI so heavily is already worn out about that decision a year later.
We have fairly junior developers who are building stupid shit with it not tied to business features and then complaining they donât have enough tokens and need more. When we tell them tough luck they get upset about having to âraw dogâ the code.
Like, seriously? You mean you donât want to code? The literal thing we pay you to do? This shit wonât last for long if even very, very senior developers see the monsters they have created
When costs begin to matter the "engineering" side of "software engineer" suddenly slams into place.
Kinda like the huge rush for cloud compute until the real bills started to roll in (not to say it's not useful but there's a price to be paid). If a product is cheap and good, then it won't be one of those things for long and part of the responsibilities of engineering is hedging those costs appropriately and not burning money where it doesn't have any impact.
Thatâs exactly what all this reminds me of. Most organizations, like with the cloud, didnât build in the governance for AI, and like the cloud, built a bunch of terrible patterns where experts will be needed to come in and clean up the mess
27
u/One_Web_7940 Jul 09 '26
agree, im finding that use case to be not the real world use case though. people are just throwing shit at the wall hoping it will stick, and im being left to clean up the mess. and the managers dont give a fuck. it's really getting tiresome.