My automated doubt development process

My automated doubt development process(alexself.dev)

34 points by aself101 4 hours ago | 14 comments

watersb 46 minutes ago |

Strangely reminiscent of an Electric Monk:

The Electric Monk was a labor-saving device, like a dishwasher or a video recorder. Dishwashers washed tedious dishes for you, thus saving you the bother of washing them yourself, video recorders watched tedious television for you, thus saving you the bother of looking at it yourself; Electric Monks believed things for you, thus saving you what was becoming an increasingly onerous task, that of believing all the things the world expected you to believe.

-- Douglas Adams, "Dirk Gently's Holistic Detective Agency"

docheinestages 3 hours ago |

Most writings about the spec-driven development I see start with a product requirements document that is assumed to be valid. But I doubt that's the case. If so, you would've written about it, and probably would've involved agents in the research that goes into it. My gut feeling tells me there's much more emphasis on implementing the feature than on questioning if it's relevant, feasible, and based on valid assumptions.

HPsquared 1 hour ago | |

Yes, it's called "questioning attitude", one of the traits of a healthy nuclear safety culture (and a good thing to apply in other fields!)

https://www.nrc.gov/docs/ML1433/ML14338A739.pdf

ben30 3 hours ago | |

Most of my energy is refining a prd these days.

docheinestages 3 hours ago | | |

Then how come that process is not agentic and not well-described?

m12k 1 hour ago |

I've stumbled on the same workflow. Except for one thing: If I just do as OP does, Claude Code will tend to overengineer. For example it'll build complex solutions to super rare race conditions that have trivial fallout. But I've found that all it takes is a "skeptical pass". Here's how it goes: After having a bunch of specialist subagents review the (plan/implementation), after doing the deduplication/synthesis of their findings, the main agent will bucket them into A) Trivial/obvious fix B) there's multiple possible resolutions, but the LLM had a strong lean, so it went with it on its own C) Genuine ambiguity, where it asks me what to do (and presents its lean) and D) Wontfix. Crucially, after doing this, I have it run a "skeptical pass" where it takes a hard look at these findings and see if maybe some of them deserve to be downgraded. Generally, a lot of things make their way into wontfix this way. I find, I don't need to push back against overengineering, I can have the LLM do so itself, and it'll actually do a decent job of it.

ErroneousBosh 14 minutes ago | |

This sounds harder than just writing the code.

aself101 4 hours ago |

This has been my attempt at wrangling the new A.I. assisted development that seems to be overtaking the software engineering profession. I jumped head first into LLM development after observing the trends from the last year and it appears this process might be a viable path forward.

jnewton_dev 3 hours ago | |

There's a selection bias here that nobody's mentioned. The people who had bad experiences with this approach probably aren't commenting.

ben30 3 hours ago | |

I’ve had similar feelings how can I trust this if I no longer write the code directly.

I wrote an /assess tool. I designed it to be token light but assesses on everything I could do to regain trust and help AI to improve my code base not by add features but by adding discipline.