> The result, in my case, is that I code more than I have in years. Three years ago I coded maybe once a fortnight, mostly throwaway PoCs to demonstrate concepts. Now I code most days of the week, in between other work.
This kind of senior engineering role really depends on the type/size of an org. I've had jobs like this on & off and generally don't stick around for long. There have always been high-impact hands-on-keyboard senior roles that involve coding most/every day..
> The other thing that gave way was thinking time. There's very little of it in my working day now. The productivity gains from AI got captured by output volume rather than output quality.
I actually see this externally from b2b vendors I am a client of. Companies that used to churn out X new products/month are now pushing 4X products but they all suck. The quantity over quality market is going to produce new opportunities for others.
There's also this part:
> Three years ago [...], the process was familiar: write a proposal, get feedback, iterate, build a small PoC to demonstrate value, get a team assigned to take it to MVP, ship something fully featured and integrated with the rest of the platform six to twelve months later.
This to me smells of large, slow, very political organisation where actual work gets done at glacial pace. The increase in speed is probably not due to LLMs, rather to the fact that this person now has an excuse to present working products while before, by their own admission, they were mostly dedicated to producing corporate slop.
It’s not corporate slop, its risk avoidance. Now leaders are so enchanted with productivity they are willing to lower the risk avoidance bar. “Move fast and break things” is meta now. It was before too, but AI is giving it a fresh breath.
Yeah, and it could have been (and in many place has been) like this all the time, LLMs or not. That was my point. The change is not due to the (albeit very real) help given by LLMs, it's due to a change of attitude in management. Magically this person who used to write code once every two weeks now has time to fully focus on coding, again.
Ya. And strangely for me it’s the opposite. I went from 50% coding to 10% because coding is so much faster and it’s easier to delegate to more junior engineers. Seems like a codebases needs to be VERY technically deep to justify spending a senior+ engineers time coding all day, as opposites to problem solving and design.
> The quantity over quality market is going to produce new opportunities for others
once the linkedin anti-ai hype train starts in earnest that’ll be when there’ll be money to be made.
monkey see, monkey do.
there's no anti-ai hype train. It doesn't exist. There'll merely be more and more bots crowding into every space that the only people left will not care.
The rest will be out touching grass.
not yet. but given the growing backlash my bet is that at some point linkedin monkeys will eventually all begin posting about the importance of “human centric design” or whatever.
at that point there’ll be some money to be made for the supposedly “replaceable” software engineers they’ve been shitting on this whole time.
i’m hoping my bet pays off, cos i would like nothing more than to rinse these people for everything they’ve got. it’ll be payback time baby.
its a existential pzombie problem, not a movement against.