Your Dev Environment Is an Asset. Treat It Like One.

Every developer has the same ritual when they sit down at a new machine: install the basics, alias the commands they type fifty times a day, wrestle the editor config into shape, and clean up the Docker cruft that accumulates on every project. It’s an hour of setup you repeat every time — and most people never get it quite right.

Your dev environment is an asset. It’s the difference between spending a morning configuring and spending a morning shipping. A small, opinionated starter pack changes the math.

1. Dotfiles: Make Every Machine Feel Like Home

A consistent shell and editor setup means you don’t have to think about where you are — only what you’re building. Two files carry most of the weight:

• .bashrc — aliases, prompts, and functions that turn your shell into a tool instead of a blank prompt. The small conveniences (shortcuts for your most-used commands, a sane prompt) compound into real speed across a day.
• .editorconfig — a single file that tells every editor the same thing: this project uses spaces, this width, this line ending. One less class of merge-conflict noise, forever, across every tool that opens the repo.

Dotfiles are the foundation: set them once, copy them to every machine and every container, and your environment stops being a per-machine lottery.

2. Git Aliases: The Commands You Actually Type

Git’s default commands are verbose. The commands you type daily deserve shortcuts — and more importantly, the safe workflows deserve to be one word. A curated .gitconfig with well-chosen aliases turns the ten keystrokes of git checkout -- . into something you’ll actually use instead of reaching for a GUI.

The real win isn’t speed. It’s that you stop avoiding Git operations that feel fiddly, which means cleaner history, fewer “undo my bad commit” emergencies, and less friction on every project you touch.

3. Docker Helpers: Reclaim the Disk You Forgot You Lost

Docker is the best and worst thing about modern development. Left alone, it silently accumulates:

• dangling images from every build iteration
• stopped containers you’ll never restart
• build cache that eats gigabytes

A docker-cleanup script that prunes the dead weight in one command keeps your disk honest. Pair it with a project-init script — a single command that scaffolds a new project with your standard structure, config, and Git setup — and starting something new goes from a ten-minute chore to a ten-second one.

The One-Time-Purchase Shape

Environment tooling is exactly the kind of thing the subscription economy has ruined. Paying $10–30 a month forever for dotfiles and a couple of scripts is absurd — you set this up once and it works for years. That’s what a one-time purchase is for.

DevKit is a $9 one-time purchase — a developer environment starter pack with dotfiles, Git aliases, and Docker helpers you can read, adapt, and own. No subscription, no telemetry, no account required. It’s your setup, versioned, portable, and under your control.

Next Steps

1. Grab DevKit and drop the dotfiles into your home directory.
2. Read the .gitconfig aliases — keep the ones you’ll actually type, change the rest.
3. Wire the Docker cleanup script into your weekly routine.
4. Use project-init.sh next time you start something new — and notice how much faster the boring part is.

The best time to fix your dev environment was your last fresh install. The second-best time is today — before the next one.

More from the Ezra Labs shop

ScaffoldKit scaffold the project your dotfiles configure; ScaffoldKit + DevKit Bundle get both for less. Explore everything at the Ezra Labs shop.