405
The Dumbest Move in Tech Right Now: Laying Off Developers Because of AI
(ppaolo.substack.com)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
That middle graph is absolute fucking bullshit. AI is not fucking ever going to replace 75% of developers or I've been working way too fucking hard for way to little pay these past 30 years. It might let you cut staff 5-10% because it enables folks to accomplish certain things a bit faster.
Christ on a fucking crutch. Ask developers who are currently using AI (not the ones working for AI companies) how much time and effort it actually saves them. They will tell you.
I use it so much. All my Google searches for syntax or snippets? Web searches are unuseable at this point, AI can spit it out faster. But the real savings? Repetitive code. I suck at it, I always make typos and it's draining. I just toss in a table or an api response and tell it what I want and boom
It probably does write 75% of my code by lines, but maybe 5% of the business logic is AI (sometimes I just let it take a crack at a problem, but usually if I have to type it out I might as well code it)
What it's good at drains my concentration, so doing the grunt work for me is a real force multiplier. I don't even use it every day, but it might be a 3x multiplier for me and could improve
But here's the thing - programmers are not replaceable. Not by other humans, not by AI - you learn hyper specific things about what you work on
It's hard to say without being immersed in the codebase you work on, but wouldn't making your code DRY (when possible) take care of a lot of the repetition without needing to write a bunch of incredibly similar code (be it by hand or with an LLM)?
No, it's all different - like a normal use case is "write me a stored procedure to optionally update all fields on a row on this table" or "given the following json response, build a class to parse it into"
We have a ridiculous database and multiple new api's to integrate with every year, so this comes up a lot