Comment by softwaredoug

A lot of examples of creating clones of existing products don't resonate with new products we build

For example, most development work involves discovering correctness, not writing to a fullproof spec (like cloning slack)

Usually work goes like:

* Team decides some vague requirement

* Developer must implement requirement into executable decisions

Now I use Claude Code to do step 2 now, and its great. But I'm looking over whether the implementation's little decisions actually do what the business would want. Or more accurately, I'm making decisions to the level of specificity that matters to the problem at hand.

I have to try, backtrack, and rebuild all the time when my assumptions get broken.

In some cases decisions have low specificity: I could one-shot a complex feature (or entire app if trying to test PMF or something). In other cases, the tradeoffs in 10 lines of code become crucially important.