This is a consequence of introducing LLMs in software development. If you imagine it as a pyramid that starts from the bottom, the easiest tasks that happen more frequently, to the top, the hardest challenges that happen once in a while, LLMs can definitely help in automating the base of such pyramid, leaving the human with an harder job to do because now he statistically encounters harder tasks more often.
If this is the price to pay to unlock this productivity boost, so be it but let’s keep in mind that:
- we need to be more careful not to burnout since our job became de facto harder (if done at the maximum potential);
- we always need to control and have a way to verify what LLMs are doing on the easiest tasks, because even if rarely, they can fail even there (...but we had to do this anyway with Junior devs, or didn’t you?)
> If your email is on the commit, you are responsible.
Humans shouldn't exist as whipping-boys for machines. It's a cop-out for shitty technology. People weren't designed for continuous passive monitoring and do really poorly at that task.
Yes, very much so, in detail. Just as I would with programmers. Also, LLM doesn't just "generate code" for me, we work together on design documents first. See, I started saying "we", because I found it to be such a good partner.
No, because I do not understand what "kinds of coding" there are. Also, given the tone of this discussion, I am not sure I want to invest my time into it.
I actually think *more* than I used to, because I only get the hardest problems to solve. I mostly work on architectural documents these days.