Ask HN: Best tool for mapping out a new software project? I usually find at the outset of a new project there seems to be a nest of spreadsheets for schema, photos of whiteboards for how everything clicks together and either wireframes or figma files for front end prototypes. Is there an all in one mapping tool for this kind of exercise or is the best way to either write it all down on paper or adhere to the above nest? |
Here are some options:
- "Project Name" bookmarks folder in your browser
- GDoc
- README in a git repo
- Miro board
- Obsidian Canvas/Notes vault backed by a git repo
For a large project with non-tech collaborators, I think Miro board is the best option. For a solo project, or small project were everyone knows git, git repo + Obsidian vault in the /docs folder of the same git repo.
You can also use Miro board to facilitate kick-start of a new project using various methods/frameworks such as Design Sprint, EventStorming, or Event Modeling.
For Software Design I would use docs-as-code formats stored in the git repo, such as:
- Markdown - GFM (GitHub Flavoured Markdown) for OSS, Obsidian Markdown if everyone on the team comfortable with Obsidian.
- PlantUML or mermaid (use mermaid since it's natively supported in GitHub and Obsidian, fallback to PlantUML for more complex cases)
- C4 Model + C3Model PlatUML (Architecture Design diagrams)
- ADR (Architecture Design Records)
- arc42 - Software Design Document templates in various formats (including GFM - GitHub Flavoured Markdown)
Personally I start with exploratory code and wiki for documentation (these days notion)