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
18.08.2025 23:29 β π 0 π 0 π¬ 0 π 0@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).
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
18.08.2025 23:29 β π 0 π 0 π¬ 0 π 0Hey π 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
Open to recommendations π
26.03.2025 02:38 β π 1 π 1 π¬ 0 π 0Ever 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)
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.
Hot take, I don't think Notion/Confluence were designed for devs, that's why weβre building Joggr to change that.
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
"less aggravating" lol that's a great way to put it!
12.02.2025 20:03 β π 2 π 0 π¬ 0 π 0thanks for sharing @bolte.id
12.02.2025 20:02 β π 0 π 0 π¬ 0 π 0Where 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?
06.02.2025 01:22 β π 5 π 0 π¬ 2 π 0Hello world! Looking forward to being a part of this community :)
20.01.2025 16:25 β π 2 π 0 π¬ 0 π 0