About
Erwin Everts. Currently contracting on an enterprise cloud platform, with prior stints in software development, agile process work, and data processing and analytics.
Cloud-native on the AWS side, focused on serverless and container-based workloads (ECS, Kubernetes). Run Kubernetes at home, and keep an eye on EU-native alternatives to the hyperscalers.
Who it’s for
Section titled “Who it’s for”Written for people doing the work: developers, platform and cloud engineers, test engineers, technical leads, and IT generalists working across delivery, operations, and governance. Useful too for new engineers finding their footing and for managers who want a concise view of what “good” looks like.
What’s not in scope
Section titled “What’s not in scope”- Vendor-specific how-tos. No “click here in the AWS console” walkthroughs. Tools get named and linked when they matter — Dependabot, Renovate, that kind of pointer — but the handbook isn’t a tutorial for any of them.
- Policy or compliance templates. Recommends defaults; does not produce audit artefacts.
- Textbook depth. Enough context to act, not to teach a subject.
- Language- or framework-specific guidance. Stays technology-agnostic unless a topic genuinely needs the specifics.
How opinionated it is
Section titled “How opinionated it is”Semi-opinionated. Every page states a default and names the tradeoff, so you can follow it or override it deliberately — not survey the options. “It depends” is not a handbook.
How current it is
Section titled “How current it is”Actively drafted. Each page shows a “Last updated” date from git, and
material changes are logged in a Changelog at the bottom of the page.
Sections still being written are marked as drafts and don’t appear in the
published site.
Where it comes from
Section titled “Where it comes from”Not lifted from one employer’s wiki. The defaults come from a mix of places — enterprise cloud work, smaller delivery teams, agile process, data platforms — sanity-checked against how other teams actually solve the same thing.
License
Section titled “License”The handbook content is licensed under Creative Commons Attribution-ShareAlike 4.0 International.
Fork it. The whole point is fewer teams starting from scratch — take a copy, change the defaults to match your context, keep the attribution and the same licence on the fork.
What earns a page
Section titled “What earns a page”The aim is to cover the basics across every generic aspect of software development, and go deeper on advanced topics where there’s a real need. A topic earns a page when practitioners hit it repeatedly and a defensible default exists. If the honest answer is “it depends,” or if a canonical external source already covers it well, it stays out — or gets a pointer instead of a page.
Why this handbook exists
Section titled “Why this handbook exists”There are plenty of good blog posts on individual ways of working. There is almost nowhere that puts them together.
The first time this itch showed up was on a project where the code was the easy part. Security, SEO, observability, deployment safety — the non-functional work — kept surfacing late, one topic at a time, and each one needed its own hunt through unfamiliar territory. A handbook is what I wanted to hand the next engineer in that spot: the recommended default, the tradeoff, and where to look next.
Work with me
Section titled “Work with me”Beyond the handbook, I do practice reviews and advisory work for teams that want a second opinion on how they build software. Scope and how to get in touch is on the Work with me page.
Contact
Section titled “Contact”Email: [email protected].