3 ms·

"The system they built feels slightly foreign even as it functions correctly." This is exactly the same issue that engineers who become managers have. You are f

by juanre 8mo ago

"The system they built feels slightly foreign even as it functions correctly." This is exactly the same issue that engineers who become managers have. You are further away from the code; your understanding is less grounded, it feels disconnected. When software engineers become agent herders their day-to-day starts to resemble more that of a manager than that of an engineer.

allan_s 8mo ago
exactly, as a manager and a sometimes a developer, "vibe-coding" has been looking more and more as my day job (in a good way, it's good to not have to do all the dirty work for your pet projects) and it's all about having the same discipline in term of: * thinking about the big picture * knowing how you can verify that the code match the big picture. In both case, somtimes you are happily surprised, sometimes you discover that the things you told 3 times the one writing code to do was still not done.
- deleted 8mo ago
  [deleted]
- mort96 8mo ago
  Do you view it as an issue at all that when everyone takes on a more manager-like role, no human remains who has the hands-on experience and understanding of the system?
- archagon 8mo ago
  Engineering is not "dirty work." Management is not "engineering."
  - allan_s 8mo ago
    It's not what I've written. To clarify, by "dirty work on my pet project" , I meant ,spending times to fix some compilation issues that after 2 hours you told yourself "damnit, I forgot this!" , or when you want to adapt your old python project from python2 to python3. And I didn't even talked about managment itself. But , thinking about the big picture, telling claude code to not use this but that. To not overengineer etc. is engineering in my book, and what I've been been doing for the last 8 years at least with more junior engineers.
konschubert 8mo ago
And like good management, the solution is to define clear domain boundaries, quality requirements, and a process that enables iterative improvement both within and across domains.

by juanre 8mo ago

allan_s 8mo ago

exactly, as a manager and a sometimes a developer, "vibe-coding" has been looking more and more as my day job (in a good way, it's good to not have to do all the dirty work for your pet projects) and it's all about having the same discipline in term of: * thinking about the big picture * knowing how you can verify that the code match the big picture. In both case, somtimes you are happily surprised, sometimes you discover that the things you told 3 times the one writing code to do was still not done.

deleted 8mo ago
[deleted]
mort96 8mo ago
Do you view it as an issue at all that when everyone takes on a more manager-like role, no human remains who has the hands-on experience and understanding of the system?
archagon 8mo ago
Engineering is not "dirty work." Management is not "engineering."
- allan_s 8mo ago
  It's not what I've written. To clarify, by "dirty work on my pet project" , I meant ,spending times to fix some compilation issues that after 2 hours you told yourself "damnit, I forgot this!" , or when you want to adapt your old python project from python2 to python3. And I didn't even talked about managment itself. But , thinking about the big picture, telling claude code to not use this but that. To not overengineer etc. is engineering in my book, and what I've been been doing for the last 8 years at least with more junior engineers.

konschubert 8mo ago

And like good management, the solution is to define clear domain boundaries, quality requirements, and a process that enables iterative improvement both within and across domains.