Developer Experience Tooling

A one-command local setup, pinned toolchains, a doctor script, fast feedback loops and the routines that keep engineers solving problems instead of fighting their machines.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Developer Experience Tooling, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Developer Experience Tooling

Improving local setup, build speed, scripts and tooling so engineers spend time solving problems rather than fighting their environment.

  1. Developer friction survey of the team
  2. Timed setup on a clean machine
  3. One-command local setup script
  4. Pinned runtime versions with a version manager
  5. Local environment variables and secrets template
  6. Standard task runner command vocabulary
  7. Local databases and queues in containers
  8. Seed data and local database reset
  9. Doctor command for broken environments
  10. Monthly developer experience pulse
  11. Weekly friction log triage
  12. Local build and test timing record
  13. Quarterly clean-machine setup rehearsal
  14. Dev container base image refresh
  15. Scripts folder review and pruning
  16. Weekly tooling office hours
  17. Tooling support channel rota
  18. Laptop disk and cache hygiene
  19. Shell scripts that work on other people's machines
  20. Profiling a slow local rebuild
  21. Editor and terminal fluency practice
  22. Debugger set up for the main app
  23. Git tooling beyond the basics
  24. Writing a small internal command line tool
  25. Dotfiles in version control
  26. Dev containers or native setup decision
  27. Hot reload for the main app
  28. Fast targeted test runs from the editor
  29. Faster local test database
  30. Cloud development environments evaluation
  31. README setup steps replaced with scripts
  32. Local stubs for third-party APIs
  33. Local HTTPS and stable dev hostnames
  34. ARM and Intel compatibility in local images
  35. Papercut fix-it day
  36. Team laptop refresh migration
  37. Version manager switch-over for the team
  38. Friction survey results readout
  39. Annual developer tooling retrospective
  40. Solo developer's personal tooling kit
  41. Isolated environments for client codebases
  42. Windows engineers in a macOS-first team
  43. Small team with no tooling owner
  44. Setup for slow or metered connections
  45. New lead inheriting a painful dev environment
  46. Opt-in local build telemetry
  47. AI coding assistant setup with team guardrails
  48. Internal tooling repository with releases
  49. Code generators for repetitive boilerplate
  50. Business case for developer experience investment

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Developer friction survey of the team

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before changing any tooling, find out where the time actually goes, because the loudest complaint is rarely the most expensive one.

First tasks

  • Draft eight survey questions that ask for minutes lost per week
  • Send the survey to every engineer with a one-week deadline
  • Group the answers into themes and total the estimated hours
  • Share the top five friction points with the team

Timed setup on a clean machine

Nobody knows how long setup really takes until someone does it from nothing and writes down every stall. Timing a fresh setup on a wiped laptop or a new user account, following only the written instructions, gives the baseline number that the bootstrap script, the docs and onboarding all need.

First tasks

  • Create a fresh user account or virtual machine with no tools installed
  • Follow the written setup steps literally while timing each one
  • Log every missing step, wrong command and stall with minutes lost
  • Record the total time to a running app as the setup baseline

One-command local setup script

A README with twenty manual steps decays the moment a version changes, while a script is either working or visibly broken. Turning the setup steps into a single idempotent command that installs dependencies, creates config and starts the app takes the clean-machine baseline from hours to minutes.

First tasks

  • List every manual step from the clean-machine run in order
  • Write the setup script so each step checks before it acts
  • Add a clear error message that names the failing step
  • Time a fresh-clone run and compare it with the baseline

Make it yours.

Install Developer Experience Tooling, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.