I give a 🦆 about docs. Building @joggr.io
🏙️ Based in NYC, wandering Manhattan.
⚡ My code works 99% of the time… the other 1% is spent figuring out why.
Hey y'all - sharing in case it would be valuable for you too, just launched Vitval (https://t.co/Qt6B5o9FTI), JS framework for writing/running evals just like you do with Vitest
Hey 👋 Looking to chat with Heads of Eng, CTOs, Tech Leads & Eng Managers at Seed–Series B startups who switched to Linear in the past year.
Curious why you switched + what you use for docs.
DM me for a quick chat, swag included 🙏
If you’re a Sr. Dev drowning in code reviews, the root cause is likely upstream…
Common causes:
Poor requirements → Define them early
Poor design → Review RFCs/Tech Specs
Misunderstood code → Improve code docs
Ever heard of IaaS? Institutional Knowledge as a Service
Every company has it. No one meant to build it. Yet here we are, running on "ask [sr. dev]" as a service
🔥 Features:
Answers lost in Slack/Notion
99.9% uptime…until PTO
Self-healing (if you brute-force the code)
The one doc I wish every team I’ve worked with had is a system diagram, but only if it’s up to date 😀
What do others feel is the most important doc to create as a dev??
Step by step guide on how to find any answer as a dev:
1️⃣ Check docs → outdated
2️⃣ Search Slack → 37 conflicting answers
3️⃣ Ask a teammate → wait 4 hours for a response
4️⃣ Google it → find a 2016 GitHub issue
5️⃣ Reverse-engineer it
6️⃣ Forget to document it 🤡
"Docs take too much time, we have to ship code!" I hear this a lot.
I agree within reason…
Prioritize docs when it matters:
🆕 New hires
🚀 New projects
🔀 Cross-team work
🌍 Async teams
Devs often ask why we say, “we give a 🦆 about docs?”
Because they’re a disaster right now:
❌ Can’t find them.
❌ Outdated when you do.
❌ Scattered across wikis, confluence, notion etc.
Docs platforms weren’t built for devs, we’re building Joggr to change that.
Give a 🦆 about developer docs? Check out our open beta @ https://t.co/94fnxZkna9!
We hated all the internal docs tools we tried, so we built something for devs. Would love folks feedback!
Our story => https://t.co/iOPccMFvt6
#documentation#devs#devdocs#developer
@i_code_daily@striver_79 depends on what you want to do, I usually suggest code comments for gotcha's in the codebase. Then markdown files for guides, project overviews, walkthroughs of complex parts. Diagrams for architecture, everything else (rfcs, tech specs) I see as ephemeral
@klinskyc@mitch_troy @joggrdocs Thanks for the shoutout @klinskyc! Happy to chat/help @mitch_troy. DM me or sign up for our waitlist @ https://t.co/94fnxZjPkB and I'll jump in and help however I can😀
Would love to talk with any devs who have dealt with documentation getting out of date or not being easy to find the right doc, would love feedback on what we are building @joggrdocs! #developer#documentation