• 6 Posts
  • 190 Comments
Joined 3 years ago
cake
Cake day: June 19th, 2023

help-circle
  • I’m allergic to YouTube videos, so I’ll rely on your text, instead.

    I do believe it goes back to the Mongols where the Russian “ingenuity” was to embrace being slaves. They realised that at any moment the “guard” can come and take everything away.

    Which means that stealing is not wrong.

    And it also means that the best way of protecting yourself is by making the guard look at somebody else. Thus insatiable need for expansion.

    Which is ironic since the guards left more than a millennium ago, but the system kept going.






  • I’ve not used speckit and likely reinventing the bicycle, but here’s my process.

    Idea.md in the root with a pitch of the system Readme.md in the root with technical information

    Then I’m using moth (https://github.com/tailoredshapes/moth) to file ideas and track tasks. Those files are definitely not full specs, just several lines of the core of the issue.

    Then I have a command /moth that instructs to read current moth, brainstorm design with me and when agreed, implement. Also as the agent works it should keep an up to date spec under ./spec describing the scope (explicitly no code details) as it evolves, decisions taken and rejected (adr like). It underscores that the task is only done when I say so. Superpowers skill is essential here.

    Then there’s the back and forth on development and testing.

    Eventually another command /moth-done that instructs to run the full test suite and mark moth as done.

    So the essence is that I don’t expect to know the full specification beforehand, but I keep track of decisions and expect to refactor often and aggressively. Conveniently writing tests is now easy and I have plenty of both unit and e2e.