Remove the friction.
Session 4 of 8 · Developer Experience Engineering
CI made the pipeline fast.
DevEx makes the whole job faster.
A fast pipeline is only one part of the developer's day. The hour they spend setting up their environment, the README that lies to them, the script that breaks on a typo: those cost just as much.
Today we fix the human-shaped parts of the codebase.
© The Build Fellowship 2024
© The Build Fellowship 2024
Agenda
What developer�experience means.
© The Build Fellowship 2024
© The Build Fellowship 2024
The Shift in Thinking
Developer experience is a product
Traditional Product
The Product: The software, SaaS app, or external system being sold.
The Users: External customers and end-users.
The Checkout Funnel: Landing page to sign-up to purchase.
Developer Experience (DevEx)
The Product: The engineering organization, tools, and codebase itself.
The Users: Your teammates and fellow software engineers.
The Onboarding Funnel: From "I got my laptop" to "my first PR is merged."
DORA
Four Metrics: deployment frequency, lead time for changes, change failure rate, mean time to recovery.
These came out of the State of DevOps research. We use them in Session 6.
Core Focus: "Is the team shipping well?"
SPACE
Five Dimensions: satisfaction, performance, activity, communication, efficiency. Broader than DORA.
SPACE is more about the "soft side" of engineering. Worth reading; we won't drill into it today.
Core Focus: "Is the team happy and effective?"
Evaluation Frameworks
Two frameworks worth knowing
© The Build Fellowship 2024
What real DevEx teams measure
© The Build Fellowship 2024
01
Time to First PR
The duration it takes for a newly onboarded engineer to merge their first pull request.
02
Local Build Speed
% of engineers who can successfully build the codebase locally in under 5 minutes.
03
Build System Touch
% of pull requests that require changes to or touch the build system in a given month.
04
Developer Sentiment
Standardized developer satisfaction and experience surveys, conducted quarterly.
Audit the�repo.
© The Build Fellowship 2024
Pretend you've never seen this codebase
© The Build Fellowship 2024
01
The Setup
Open OrbitTasks together like it's a brand-new repo. Read the README top to bottom.
02
The Run
Follow the onboarding instructions literally
03
The Friction
What’s incorrect? Ambiguous? Missing?
04
The Logbook
Don't fix anything yet; just collect data and record it as we go.
© The Build Fellowship 2024
01
The README Gap
The README promises a simple flow but skips required setup steps like env vars, migrations, or seeds.
02
Fragile Scripts
A script exits with an error because of a small bug or platform-specific assumption.
03
Stale Docs
Documentation references tools, libraries, or architectures that aren't actually used anymore.
04
Inconsistencies
Scripts in package.json are named inconsistently: dev here, start there, serve elsewhere.
© The Build Fellowship 2024
Now switch hats: you're on the platform team
01
Maintainability
What about this codebase makes it hard for your team to maintain it across many similar projects?
02
Missing Conventions
What standards, structures, or configurations are missing from the current repository?
03
The Org Wishlist
What capabilities or standards do you wish every single repository in the organization had?
Now build�the fixes.
© The Build Fellowship 2024
© The Build Fellowship 2024
The single biggest DevEx win
The one-command setup script
01 / THE GOAL
5 Minutes
Run make setup to boot a fully working environment instantly.
02 / TODAY'S FRICTION
50 Minutes
No root dev script exists. Setting up manually is slow and error-prone.
Makefile
Works for any project regardless of language. Great for monorepos with mixed stacks.
make setup make dev make test make ci
Some love it, some hate it but any simple tool will do.
npm scripts
Simpler for some, sometimes harder to remember as they grow.
Today's Setup: Makefile at the root, npm scripts inside each app.
Makefile or npm scripts?�Either is fine.
© The Build Fellowship 2024
Make make setup actually work
01 / TASKS & TARGETS
Write or fix the setup automation scripts to boot the environment.
02 / VERIFICATION & DONE
The acceptance test: a teammate clones the repo and runs setup.
© The Build Fellowship 2024
Documentation that doesn't lie to you.
Out-of-date docs are worse than no docs at all. Three rules:
01
Document only what you actually do.
Aspirational documentation rots fastest.
02
Keep the README to one page.
Link out to deeper docs in docs/.
03
Verify every single command.
For every command in the README, verify by running it on a fresh clone.
© The Build Fellowship 2024
A few small tools that pay back fast
Pick one or two to add today. You don't need all of these. Choose what solves your biggest pain point.
01
Pre-commit hooks
Catch formatting issues before pushing code with Husky.
02
Dev containers
Speed up developer onboarding with Devcontainers and .env.example files.
03
Single-command servers
Use concurrently and wait-on to manage multi-process dev servers cleanly.
04
Secret management
Handle sensitive environment credentials safely using dotenv-vault or 1Password CLI.
© The Build Fellowship 2024
Measure�the win.
© The Build Fellowship 2024
Time it.
© The Build Fellowship 2024
01
The Setup
Together, on a fresh clone (or run make clean then a fresh make setup).
02
The Measurement
We time how long it takes to go from "I just cloned" to "I have the app running locally."
03
The Delta
Compare this to the estimated original flow. The delta is your improvement. Record both numbers in your logbook.
The DevEx career path is real and growing.
Five years ago DevEx wasn't a job title. Today it is, at every company over ~50 engineers.
Job Titles
Developer Experience, Productivity Engineer, or Internal Tooling.
Salary Bands
$150k–$270k for mid-senior roles in major markets, tracking closely with Platform Engineering.
The Work
A multi-disciplinary blend of software engineering, product sense, and human-factors thinking.
Your Portfolio
The portfolio you build here is an interview-quality artifact designed specifically for this role.
© The Build Fellowship 2024
© The Build Fellowship 2024
What changes next session
Session 5: AI-Assisted Development & Evaluation
01
AI-Assisted Build
You'll use AI coding tools (Claude, Copilot, ChatGPT) to refactor a real module, generate unit tests for an untested service, and produce documentation.
02
The Critique
Then we critique the output together. We will carefully analyze and review the generated assets, testing their validity and structure.
03
The Core Lesson
Some of the output will be great; some of it will be wrong. Learning to critically tell the difference is the real lesson.
Questions?
© The Build Fellowship 2024