The job has changed from a craft to operating an unreliable machine.
Instead of satisfaction of solving challenging problems with your own skill and creativity, you babysit a text extruder and slog through mistakes in its generated output.
Arguably this may make software cheaper to make and accessible to non-programmers, but for people who liked their job it's like being demoted from a restaurant chef to a microwave button pusher.
I find it very difficult to learn a new thing by reading it, vs by doing it.
And indeed, most mathematicians, who do get paid to do math, work a lot with pencil and paper. If math is secondary to your job, you likely will not, but if it’s your primary job, you likely spend a lot of time working ideas out in the more primitive fashion.
The whole point of the discussion about LLMs in our field is exactly what you say. Yes, we do often find ourselves doing new things. They are exciting the first and the second time we do them. Later they become a chore.
When you’re doing something that requires a lot of typing for the 17th time… why! Like, how many times are you going to write that golang http server scaffold. Or, how many times are you going to create that new terraform project with those same modules. I hear people say “oh yeah, write a generator”. To which my answer is: do you have a budget for it, or do I need to invest my own time.
It’s possible to guard the model so that it acts according to your expectations. Just invest the time in that tooling. It’s as exciting as any other problem. You learn the domain by writing software guardrails, your effort results in a software analysis of the business domain problem. It’s a much more valuable and rewarding work than writing some code.
Instead of solving things yourself, you need to learn how to describe them in a way others can solve them. Otherwise you will just be fighting the instinct to just do it yourself.
Many tech/software people were completely unsympathetic if not downright arrogant when their products displaced people in other professions who felt the same way.
The lesson here is that ultimately, change comes for everyone.
Nah, they want to think beyond the superficial prompting level. A lot of real programmers feel exactly the same.
It is hard to notice this sometimes on HN because this site is rife with the very idea-man-VC-pilled-finance-bro-pseudo-hackers that over the past 15-20 years have turned the tech industry from one of optimism for a brighter future to one that most normal people now distrust and hate.