Mastodawn

So my work is mandating agentic coding. One thing I have found is that it shifts to the right (as opposed to you know...shiftLeft), both in terms of quality and understanding. I have adjusted by scrutinizing the output (code) much deeper than if I owned more of the workflow (discovery at minimum).
But ofc, that annuls much of the time saved using an agentic workflow. #programming #agents #AI

Show thread

Dr. Thaddeus Q. They Mar 23

@marytzu
It's kinda like pair programming, and the critics say the same - you're wasting time putting two people to produce the output of one.
But in the long term, having better reviewed code actually pays. Perhaps it's the same case here, as long you don't just vibe code

Show thread

Marytzu

@mattesilver depends what you mean by vibe code, haha. My old workflow was good ole ctrl c +v albeit with heavy modifications, & as for what was copied; mostly existing design patterns in the codebase. New workflow is feed tech design & ticket to planner bot -->implementation plan--->copilot in VS-->QA bot-->I review it. Mgmt at my work is pushing for full agentic workflow though, so god knows how long this will last b4 a full hands-off workflow is mandated.🙃

Show thread

Dr. Thaddeus Q. They Apr 4

what about over-fitting?

@marytzu

Show thread

Marytzu Apr 5

@mattesilver I haven't seen it with my work, yet. I have "use existing patterns" in the prompts/skills among others. Design debt is a concern of mine. We have no BA's so it's just a matter of time before we are laden down with spaghetti business logic.

Speed and agentic workflow are the mandates though. 🙃 I'm trying very hard to care less at/about work. It's challenging 🥲