Short intro
Research writing is not separate from engineering. It is a way to slow down, compare tradeoffs, and make the unknown parts visible.
What I was trying to do
I wanted the Research section to contain exploratory papers and technical comparisons that feed back into project and blueprint thinking.
What I learned
- Exploratory papers help clarify tradeoffs.
- Quantum computing architecture research belongs here because it is technical, comparative, and early-stage.
- Technical writing improves system design thinking.
- Research should connect back to projects, blueprints, and artifacts instead of living in isolation.
Technical notes
- A useful research note should state assumptions, compare alternatives, and end with open questions.
- Neutral-atom and superconducting qubit comparisons are architecture discussions, not just physics summaries.
- Research entries can become future artifacts when they mature into PDFs or diagrams.
Problems / open questions
- How formal should research entries be before publishing?
- Should papers have version history?
- Which research notes should become downloadable artifacts?
Next steps
- Connect research entries to related blueprints.
- Add status labels for Draft, Planned, In Progress, and Published.
- Keep paper downloads marked Coming Soon until files exist.