Re:We promoted developers into architects without informing ...
by lordnacho on Friday November 20, 2026 @04:43PM
(#50582646)
If instead of becoming a software engineer, you became a civil engineer, you would not be pouring concrete and tightening steel cables.
Until very recently, a software engineer did the equivalent things: looking for small coding errors, hooking up libraries, writing unit tests.
Now, those things can be done by an LLM. All that is left for a software engineer is to do the actual understanding of architecture, and to be responsible.
Of course I can understand that people mourn being able to look over their implementation of some algorithm deep in the bowels of the product. That used to be fun. I can understand that young people in the field now face uncertainty, because doing the little things used to be how you paid your dues so that the seniors could explain to you how the big things were done.
It was like a deal, you would join the firm and do the stuff that was necessary, in exchange for training. You had time to learn the big things, because the little things took time.
There's another business that I started in where the gap also went away. In the old days, traders used to do their work on paper. There would be clerks who would note down trades, and check that the firm's positions were in fact what the senior trader thought. Pretty mundane stuff. But at the end of the day, you would sit with the boss and he would explain what had actually happened while you checked things.
I happened to land just as the transition was finishing: instead of taxing your physical conditioning by having you jog around the floor in a coloured jacket, the work went on a computer. The computer would let you solve the small things faster and better than you could ever do yourself. But it would also be the end of that guy who was just a good grinder. Now you had to use the machine to do new things in the market, and people started needing degrees to get the job in the first place.
The very nature of the entry-level job changed. The job itself opened up as well, though the fundamentals at a high level remained.
Until very recently, a software engineer did the equivalent things: looking for small coding errors, hooking up libraries, writing unit tests.
Now, those things can be done by an LLM. All that is left for a software engineer is to do the actual understanding of architecture, and to be responsible.
Of course I can understand that people mourn being able to look over their implementation of some algorithm deep in the bowels of the product. That used to be fun. I can understand that young people in the field now face uncertainty, because doing the little things used to be how you paid your dues so that the seniors could explain to you how the big things were done.
It was like a deal, you would join the firm and do the stuff that was necessary, in exchange for training. You had time to learn the big things, because the little things took time.
There's another business that I started in where the gap also went away. In the old days, traders used to do their work on paper. There would be clerks who would note down trades, and check that the firm's positions were in fact what the senior trader thought. Pretty mundane stuff. But at the end of the day, you would sit with the boss and he would explain what had actually happened while you checked things.
I happened to land just as the transition was finishing: instead of taxing your physical conditioning by having you jog around the floor in a coloured jacket, the work went on a computer. The computer would let you solve the small things faster and better than you could ever do yourself. But it would also be the end of that guy who was just a good grinder. Now you had to use the machine to do new things in the market, and people started needing degrees to get the job in the first place.
The very nature of the entry-level job changed. The job itself opened up as well, though the fundamentals at a high level remained.