Damus
Sheena · 6w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq3s57k3vxf263ffpzfwjgupcr9e694agy74zkdekzd6ss5tfv3zeq0rxl2p (2) Facts, as described here, seem to be quite high resolution. They might miss some...
Sheena profile picture
@nprofile1q...
(3)
My current impression is that anyone working on brownfield or serious projects should make their own workflow instead of taking something someone else made. Bake in the things you care about.

Human collaboration is being made difficult by these tools - code review is a beast even for solo devs. But early workflow artefact review seems feasible. So it's useful from that perspective too.

But making your own SDD-ish workflow is not very obvious. It's a new set of skills
1
Paul Everitt · 6w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqhxedrnr8366gz30xxuec5yl6t4xnywql4t5cqruk95rzu4am02xs4crfjk Your instinct and takeaway matches my takeaway. Especially, wants to synthesize specs and facts. Similar to how skills (non-deterministic) can wrap CLIs.