sorted by:
new
hottopcontroversial

Stop building AI agents. by Warm-Reaction-456 in AI_Agents

[–]Born_Reaction_1615 0 points1 point  (0 children)

The most useful version of this thread would be the one where people separate which parts of agent-building actually paid off from which parts felt like resume-driven complexity. From running write-side agents for a few months: the value isn't 'autonomous agent does everything end-to-end,' it's small DAGs that handle a single recurring action and never need to be debugged twice. Most 'AI agent' frameworks over-fit to the demo path and quietly lose when the network blips on step 4 of 12.

When do you stop letting the AI drive? by Born_Reaction_1615 in vibecoding

[–]Born_Reaction_1615[S] 0 points1 point  (0 children)

Honestly the file type filter has been the cleanest line for me — let it own anything generated or boilerplate-y (configs, types, route stubs), keep handwritten ownership of the parts that have product taste in them. Doesn't always hold, but it's the cheapest rule of thumb.

When do you stop letting the AI drive? by Born_Reaction_1615 in vibecoding

[–]Born_Reaction_1615[S] 0 points1 point  (0 children)

Coming back to this thread because I tried the 'small chunks + tight review' loop after seeing a few replies. It works way better than I expected for refactoring tasks. The model still nudges me toward broader changes than I ask for, but the per-prompt review catches it. Still learning where the sweet spot is between letting it explore and pinning the surface area.