Originally published on robatdasorvi.com
The onboarding doc said three steps. By step two, I had a broken Homebrew dependency, two conflicting Node versions, and an .env.example that referenced secrets nobody could remember who owned. By the time I had a working local environment it was nearly 5 PM and I had produced nothing.
That afternoon was developer experience. Not the polished version that gets cited in engineering blog posts. The real version: the aggregate friction between a person's intent and their output, made visible in the worst possible way on somebody's first day at a job they were actually excited about.
What does "developer experience" actually mean?
Developer experience is the sum of every system, process, and decision that either helps a developer stay in focused work or drags them out of it. It's not about individual tools—it's about the total friction between intent and output.
