DevScribe

I wanted to share why I started building DevScribe and what I learned along the way.

Like many developers, I used note-taking tools (especially Obsidian) for years. They’re great for ideas, notes, and documentation. But as my projects grew more complex, I kept running into the same problem:

My actual engineering work was scattered across too many tools.

A typical workflow looked like this:

• Notes & docs in a note app

• API testing in Postman

• Database queries in DBeaver / DataGrip

• Diagrams in Draw.io or similar

Everything was documented — but nothing was connected.

The Core Problem I Hit

Documentation tools are optimized for writing, not for engineering.

I wanted a place where I could:

• Write documentation

• Run real database queries

• Test APIs

• Design ERD / HLD / LLD diagrams

• Keep everything offline and local

But no single tool supported this workflow without heavy plugin hacks or constant context switching.

So I decided to build one.

What I Built

DevScribe is an offline-first developer workspace where:

• Documentation lives next to:

  • Database queries (MySQL, SQLite, PostgreSQL, MongoDB, Elasticsearch)

  • API tests (Postman-like interface)

  • System diagrams (ERD, HLD, LLD, UML, sequence diagrams)

• Projects are organized like real codebases

• Everything works locally without cloud dependency

It’s not meant to replace note apps for personal knowledge.
It’s meant to support real engineering work.

What I Learned Building It

A few honest lessons from the journey so far:

1. Developers don’t want more tools — they want fewer

2. Plugins can’t replace deep integration

3. Offline-first still matters more than marketing suggests

4. “Executable documentation” resonates more than “note-taking”

5. Distribution is harder than building (by far)

Where I Am Now

I released DevScribe recently and got early users mainly through:

• Reddit posts

• Comparison articles

• Word-of-mouth from developers who felt the pain

No paid ads yet — still learning how to distribute properly.

What I’d Love Feedback On

If you’re a developer or builder, I’d love your thoughts on:

• Do you feel this tool-fragmentation pain?

• Would you prefer an all-in-one engineering workspace?

• What would stop you from switching to something like this?

Happy to answer any questions or share more details.

Thanks for reading 🙌