upvote
Survival instincts. If everyone and everything around you (your job included) is shouting "use AI" it's difficult to take any stand or introduce caution. I think it's less about being excited, more about hoping to not miss the wave and get "left behind."

I think both groups (pro vs anti) will be a bit surprised when the long-term data shows productivity gains were modest on average and producing quality software still needs care/human attention, even with the support of advanced, frontier models. Same job as before, now we just have a power drill instead of a screwdriver. Some people build houses that stand for hundreds of years, others less so.

reply
Because we've been automating large parts of our former jobs for decades. Otherwise we'd all be trying to build things in the least efficient way possible to maximize how long the job takes, which IMO isn't a great idea.

Humans have been minimizing how much work is needed to get a certain level of output for as long as we can track. It's civilization. Should we go back to farming by hand with hoes, to maximize labor used? Go back to streetlights that are individually lit? The society that falls behind on automation becomes poorer, and eventually just dies, as even the people born there tend to choose to leave to higher productivity places. It happened to eastern europe, it happens to the Amish. To any poor society which gets emigration. Doing more with less has always been exciting.

reply
Because usually the people who lose their jobs are people who do not adapt to the market.

Right now it's not clear in which direction everything is involving and that's why people experiment with handing all their data to random agents, figuring out how to store and access context, re-use prompts and other attempts to harness this tech. Most of these will maybe be useless in a year as they might be deeply integrated into the next wave of models but staying on top of the development has always been part of the fun of working in this field.

reply
People are building bots to do the most legible thing possible which is feature in X amount of time. But it doesn't matter if the bottleneck is human thinking time required to output quality code rather than X amount of code written.
reply
I am so much faster with the bots. If you're not faster with the bots then either you write very very little code, or you're doing it very wrong. Tactically they outsmart me 10-100x if you account for the write speed. Even if you just consider the knowledge of languages, libraries, patterns they clearly outperform me. Strategically I do not trust them at all, poor things suck at it, mainly because they always try to take the shortest possible path to the current destination.

And if you think that your personal protest against the automation will in any way affect the direction in which the industry goes then you're delusional. You would have to start something like a political party and collect way more people.

reply
Wake me up when LLMs help me write better code and let me understand the codebase, and not before. Not faster, not more productive, but a more comprehensible codebase that I can reason in my own head.

Otherwise, if they write so much better code, than it's pointless to have a human in the loop.

reply
It's likely the people that were not good developers that suddenly got accelerated "to the top" that seem the most for it. All of the good devs I know have been a bit more cautious on the uptake.
reply
I think it's more subtle than that. There are a lot of measures of what a 'good developer' is, and one of them is 'shipping things'. AI is specifically accelerating that part of the industry - it's much easier to ship code faster now. If you're in a domain that doesn't need quality (easy horizontal scaling, bugs rarely have a critical impact, customers are relatively loyal) then AI is proving that shipping features is more important than code quality.

If you're in a part of the software industry that needs well-optimized and bug-free code then it's less useful. The problem for devs is that those parts of the industry are much smaller.

reply
I don't understand this thinking as a computer programmer. My whole life has been about getting a computer to do work so humans don't have to anymore. Every single piece of software written is supposed to take away work from someone.

Do you feel this way about every automation you create? I do know some old school sys admins who felt this way about a lot of infrastructure automation advancements, and didn't like that we were creating scripts and systems to do the work that used to be done by hand. My team created an automated patching system at a job that would automatically run patching across our 30,000 servers, taking systems in and out of production autonomously, allowing the entire process to be hands free. We used to have a team whose full time job was running that process manually. Did we take their jobs by automating it?

Sure, in a sense. But there was other work that needed to be done, and now they could do it.

The whole reason I like programming and computers and technology is precisely because it does things for us so we don't have to do it. My utopia is robots doing all the hard work so humans can do whatever we want. AI is bringing us one step closer to that, and I would rather focus on trying to figure out how we can make sure the whole world can benefit from robots taking our jobs (and not just the rich owners), rather than focus on trying to make sure we leave enough work for humans to stay busy doing shit they don't actually want to do.

reply
Some people are playing the global optimization game; a world where anyone can have any (production grade) software they want.
reply
people are now being encouraged to use ai notetaking features under the guise of productivity.

a worker is just the sum total of all work related context. to collate, verify and organize this context is just asking to be replaced.

reply
Month 30 of software engineers not existing in 6 months
reply