zlacker

[parent] [thread] 6 comments
1. icedch+(OP)[view] [source] 2026-01-14 23:55:02
This is how we wound up with non-technical "engineering managers." Looks good to me.
replies(1): >>tired_+R7
2. tired_+R7[view] [source] 2026-01-15 00:42:45
>>icedch+(OP)
I think this misses the point, see the other comments. Fully scaled agentic coding replaces managers too :) cause for celebration all around
replies(2): >>icedch+Lq >>satvik+Zb1
◧◩
3. icedch+Lq[view] [source] [discussion] 2026-01-15 02:55:56
>>tired_+R7
I don't believe that. If you go fully agentic and you don't understand the output, you become the manager. You're in no better position than the pointy-haired boss from Dilbert.
replies(1): >>tired_+bQ2
◧◩
4. satvik+Zb1[view] [source] [discussion] 2026-01-15 09:58:05
>>tired_+R7
No, it becomes only managers, because they are the ones who dictate the business needs (because otherwise, what is the software the agents are making even doing without such goals), and now even worse with non technical ones.
◧◩◪
5. tired_+bQ2[view] [source] [discussion] 2026-01-15 18:18:00
>>icedch+Lq
Hey just wanted to thank you for the healthy back and forth! I respect your opinion and don't hold mine strongly. That said I'm eager for this space to mature and for us all to figure out the best way to interact with fault prone code generation tooling... Especially at scale where we all have the hardest time navigating complexity.
replies(1): >>icedch+Vt3
◧◩◪◨
6. icedch+Vt3[view] [source] [discussion] 2026-01-15 20:57:45
>>tired_+bQ2
Thanks. It's fun chatting about this stuff! I don't hold mine strongly, either, though I am dealing with lots of AI generated slop code from others.

Interesting times ahead.

replies(1): >>tired_+nG4
◧◩◪◨⬒
7. tired_+nG4[view] [source] [discussion] 2026-01-16 07:04:52
>>icedch+Vt3
I feel for you. Hopefully your colleagues come around and realize that if they submit the code they are responsible for the slop.
[go to top]