Seth Rosenbauer
@sethrosenbauer.bsky.social
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.
🏕️ Also into sports, the outdoors, and getting off the grid (sometimes).
🏙️ Based in NYC, wandering Manhattan.
⚡ My code works 99% of the time… the other 1% is spent figuring out why.
🏕️ Also into sports, the outdoors, and getting off the grid (sometimes).
Hey y'all - sharing in case it would be valuable for you too, just launched Vitval (viteval.dev), JS framework for writing/running evals just like you do with Vitest
August 18, 2025 at 11:29 PM
Hey y'all - sharing in case it would be valuable for you too, just launched Vitval (viteval.dev), 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 🙏
Curious why you switched + what you use for docs.
DM me for a quick chat—swag included 🙏
April 1, 2025 at 5:59 PM
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 🙏
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
Common causes:
Poor requirements → Define them early
Poor design → Review RFCs/Tech Specs
Misunderstood code → Improve code docs
March 28, 2025 at 12:29 AM
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
Common causes:
Poor requirements → Define them early
Poor design → Review RFCs/Tech Specs
Misunderstood code → Improve code docs
Reposted by Seth Rosenbauer
Open to recommendations 🙃
March 26, 2025 at 2:38 AM
Open to recommendations 🙃
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 [senior dev]" as a service.
🔥 Features:
✅ Answers lost in Slack & Notion
✅ 99.9% uptime… until PTO
✅ Self-healing (if you brute-force the code)
Every company has it. No one meant to build it. Yet here we are, running on "ask [senior dev]" as a service.
🔥 Features:
✅ Answers lost in Slack & Notion
✅ 99.9% uptime… until PTO
✅ Self-healing (if you brute-force the code)
March 18, 2025 at 11:06 PM
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 [senior dev]" as a service.
🔥 Features:
✅ Answers lost in Slack & Notion
✅ 99.9% uptime… until PTO
✅ Self-healing (if you brute-force the code)
Every company has it. No one meant to build it. Yet here we are, running on "ask [senior 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??
What do others feel is the most important doc to create as a dev??
March 14, 2025 at 12:47 AM
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??
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 🤡
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 🤡
March 11, 2025 at 11:41 PM
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 🤡
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
I agree within reason…
Prioritize docs when it matters:
🆕 New hires
🚀 New projects
🔀 Cross-team work
🌍 Async teams
March 7, 2025 at 1:32 AM
"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
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.
Hot take, I don't think Notion/Confluence were designed for devs, that's why we’re building Joggr to change that.
Because they’re a disaster right now:
❌ Can’t find them
❌ Outdated when you do
❌ Scattered across wikis, confluence/notion etc.
Hot take, I don't think Notion/Confluence were designed for devs, that's why we’re building Joggr to change that.
March 4, 2025 at 4:20 PM
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.
Hot take, I don't think Notion/Confluence were designed for devs, that's why we’re building Joggr to change that.
Because they’re a disaster right now:
❌ Can’t find them
❌ Outdated when you do
❌ Scattered across wikis, confluence/notion etc.
Hot take, I don't think Notion/Confluence were designed for devs, that's why we’re building Joggr to change that.
Reposted by Seth Rosenbauer
Give a 🦆 about developer docs? Check out our open beta 👉 joggr.io!
@sethrosenbauer.bsky.social and hated all the internal docs tools we tried, so we built something for devs. Would love folks feedback!
Our story 👉 joggr.io/about
#devdocs #techdoc #docs #developers #giveaduck #nodejs
@sethrosenbauer.bsky.social and hated all the internal docs tools we tried, so we built something for devs. Would love folks feedback!
Our story 👉 joggr.io/about
#devdocs #techdoc #docs #developers #giveaduck #nodejs
Documentation for developers · Joggr
Documentation platform for developers that keeps your documentation up to date.
joggr.io
February 27, 2025 at 9:06 PM
Give a 🦆 about developer docs? Check out our open beta 👉 joggr.io!
@sethrosenbauer.bsky.social and hated all the internal docs tools we tried, so we built something for devs. Would love folks feedback!
Our story 👉 joggr.io/about
#devdocs #techdoc #docs #developers #giveaduck #nodejs
@sethrosenbauer.bsky.social and hated all the internal docs tools we tried, so we built something for devs. Would love folks feedback!
Our story 👉 joggr.io/about
#devdocs #techdoc #docs #developers #giveaduck #nodejs
Where are all the devs at? Would love to connect with fellow devs on here, curious how this is different than Twitter or do I have to call it X lol?
February 6, 2025 at 1:22 AM
Where are all the devs at? Would love to connect with fellow devs on here, curious how this is different than Twitter or do I have to call it X lol?
Hello world! Looking forward to being a part of this community :)
January 20, 2025 at 4:25 PM
Hello world! Looking forward to being a part of this community :)