Comment by skeledrew
9 hours ago
Technically it's just a role change. You're now the project manager or something, not the developer. It isn't a project manager's job to understand the code, only to ensure it does what it should and doesn't do what it shouldn't. And to ensure the developers, etc str unblocked and doing well. Embrace the new role.
Why would you need to embrace something forced upon you?
There is no escape from Dario's basement. It's best just to accept our fate. Rub the lotion on our skin or else we get the hose again.
We just need to hold until people realize the crappy codebases that AI is generating
1 reply →
Perhaps it will make it easier to cope with? Fighting something beyond your control is pretty exhausting
Or just ignore AI. As long as you do your job, who cares if you use AI or not
So you can pay rent?
In most workplaces, when supervisor/boss says "we need you working over here now; you start tomorrow", you either embrace or quit. Again, nothing fundamentally different.
And in most jobs, you don't get promoted to manager if you don't want to
1 reply →
Then whose role is it now to understand the code?
That's the neat part; you don't!
Same thing is happening in academia.
How much understanding is needed? If it works as specified (you did a complete spec and occasional check-ins to ensure things are on track and then tested the delivery, right?), then what more is needed?
The moment you fully make you spec and requirement water-tight, what you have is similar to source code.
Understanding is needed when something breaks and you need to fix it immediately. Otherwise you become a meat proxy and now you’ve added Anthropic’s uptime as a single point of failure to your application.
3 replies →
So you just click around the UI, assuming there is one?
Can you break down for me exactly how the unit and integration tests are made? Do you ask the AI what to assert?
3 replies →
> (you did a complete spec and occasional check-ins to ensure things are on track and then tested the delivery, right?)
I have never in my career been afforded the time to make a complete spec.
1 reply →
Ah yes the Santa dev fallacy.
Noone understood the code to begin with. People understand the concepts, the primitives, the "theory" as Naur said, the basis upon which a project is built. Noone ever understood a codebase worth understanding to begin with.
I'd like to meet Noone someday. He's done so many amazing things.
Noone always gets it right, Noone went there after that horrible incident, Noone actually dances like that...
Project managers just take the engineers word for it.
And engineers have a lot of leeway to just make shit up and the PM would have no idea until it blows up.
So the million dollar question: will you (ie those getting pushed into the role) continue that trend?
Except you can't blame Claude when sh-- hits the fan.
You don't - want to - blame humans either.
- https://dev.to/ayanozturk/dont-blame-the-developer-lessons-f...
- https://www.linkedin.com/pulse/blame-game-why-blaming-develo...
- https://thedevopsdojo.substack.com/p/stop-blaming-developers...
If you were forced into an "AI native" position, not given time for proper reviews, etc... you absolute can.