May 16, 2026 at 5:00 am
Comments posted to this topic are about the item We Are Eating Our Own Seed Corn
May 16, 2026 at 11:47 am
One has to wonder as well, how much of this push to use AI on the tech side stems from businesses STILL often seeing IT not as the force-multiplier it really is, but still as a cost-sink? That still in some way have the attitude (we've all run into in some fashion) of, when things go wrong, "what are we paying you for?" and when things are working smoothly, "what are we paying you for?"
Chatting with someone (not in IT) yesterday about AI, one of the things I pointed out that's going to come back and burn businesses is developers doing full-on "vibe coding." Not having AI throw together a first-draft of what they want, that they then go through and clean-up and optimize, but the ones who vibe-code to a "finished" product. The problem they'll run into is when that product inevitably breaks, or needs updating, or has security vulnerabilities, the original developer won't have a clue how it does what it does, yet they'll have to try to support it.
Sure, they could throw the code back into AI and try to get it fixed, but...
That'd just be kicking the can down the road, maybe for the same dev, maybe for the next person.
Honestly, I think the editorial has the right of it. Keep hiring in the juniors, hand them the AIs to use as a force-multiplier, similar to how the previous generations of juniors had search engines and the internet to use as their force-multiplier (like me!) The important part of this though, would be the SENIORS would need to challenge the juniors to show they understand what they're doing and what the AIs are producing for them.
May 16, 2026 at 12:41 pm
No arguments from me, you know that.
I will make one small point. A thing that can't go on, won't. We may be seeing the end of the ecosystem we came up in, but if another ecosystem is needed, it's pretty likely going to develop. There will likely be another way for the junior IT people to become senior. Heck, maybe it will be better. Speaking for myself, my journey from junior to senior was rocky and uneven at best.
We'll see how it goes.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 18, 2026 at 10:54 pm
This editorial is something all upper level management that pushes AI should read. It is straightforward and lays out legitimate concerns I have that I'm not nearly this eloquent to state so well. The company I work for fortunately is dedicated training its people across the board so isn't an immediate concern, however management reads how companies have been able to replace AI with people and start getting the wrong idea. AI can help people be more productive, it won't replace them. We need more well thought out discussions what to be wary of with AI instead of so many discussion on just vibe code everything.
In the late 90s people were on the VB bandwagon because you could drag and drop something that looked cool and did a couple of things. I made a lot of money going in and fixing so much trash VB code because people didn't realize you need to be able to code even VB. This caused people to think of VB as a garbage language since there was so much horrible code written in it so it is mostly shunned. Don't want to see that kind of backlash with AI.
Please keep up explaining the truth!
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply