Here’s a fun thing. Using the latest AI to code backend and front-end code. Every couple of weeks, have to stop, go through every line and module, and throw out pretty much 90% of the code, manually refactor, and rewrite it.
It offers a good starting point, but the minute things get slightly complicated, you have to step in. I feel bad for people who think this will make it so they don’t need experienced developers and architects. They’re in for a rough ride.
An interesting point I heard the other day: if AI can replace entry level jobs, doing simple scripts that AI can definitely do (because it essentially just spits out the stack overflow/Reddit/etc training data verbatim), then companies no longer need entry level programmers.
If they don’t need entry level programmers, how do you get future senior programmers? Skipping directly to advanced stuff without getting practical experience on the simple stuff is incredibly hard.
What happens when the current senior programmers retire in larger numbers, and there’s very few replacements because the ladder is gone?
That’s a problem for Q72 and they’re incapable of looking past Q4. Besides, they’ll have already jumped ship by then, what do the execs care if they make this quarter just ever so slightly more profitable
What happens when the current senior programmers retire in larger numbers, and there’s very few replacements because the ladder is gone?
I don’t have a solution. I’m just stocking up on physical paper books, so I’ll have something to entertain me while nothing works, until someone figures it out.
(I’m sort of joking, and sort of serious. I do expect Internet service outages to become a lot more common. But I actually just like books, anyway.)
Agree. Software engineering is a marathon - not a sprint. These AI tools are useful to get something up real quick, but I have a hard time seeing how they can be useful for long term maintenance work.
The first draft is fun.
The second draft is pain.
The third draft is cathartic.
Figure out features, add add add.
Add/change features, realise the spaghetti mess and poor design decisions you made in the first draft.
Clean everything up with better design and code.
Here’s a fun thing. Using the latest AI to code backend and front-end code. Every couple of weeks, have to stop, go through every line and module, and throw out pretty much 90% of the code, manually refactor, and rewrite it.
It offers a good starting point, but the minute things get slightly complicated, you have to step in. I feel bad for people who think this will make it so they don’t need experienced developers and architects. They’re in for a rough ride.
An interesting point I heard the other day: if AI can replace entry level jobs, doing simple scripts that AI can definitely do (because it essentially just spits out the stack overflow/Reddit/etc training data verbatim), then companies no longer need entry level programmers.
If they don’t need entry level programmers, how do you get future senior programmers? Skipping directly to advanced stuff without getting practical experience on the simple stuff is incredibly hard.
What happens when the current senior programmers retire in larger numbers, and there’s very few replacements because the ladder is gone?
That’s a problem for Q72 and they’re incapable of looking past Q4. Besides, they’ll have already jumped ship by then, what do the execs care if they make this quarter just ever so slightly more profitable
They’re incapable of looking past a single quarter, let alone 4.
I don’t have a solution. I’m just stocking up on physical paper books, so I’ll have something to entertain me while nothing works, until someone figures it out.
(I’m sort of joking, and sort of serious. I do expect Internet service outages to become a lot more common. But I actually just like books, anyway.)
Agree. Software engineering is a marathon - not a sprint. These AI tools are useful to get something up real quick, but I have a hard time seeing how they can be useful for long term maintenance work.
Plus “getting something up real quick” is the fun part.
The first draft is fun.
The second draft is pain.
The third draft is cathartic.
Figure out features, add add add.
Add/change features, realise the spaghetti mess and poor design decisions you made in the first draft.
Clean everything up with better design and code.
It doesn’t sound like a good starting point if you have to throw out 90% of it every couple of weeks.
Drag feels schadenfreude for them. If they’re going to fire their workforce to chase trends, it would be fun for them to go out of business about it.
i think the rough ride is a necessary learning experience