Building Software: Risk and Validation
A quick sketch illustrating why frequent iteration and learning validates direction to prevent going too far of course.
software delivery
12 posts
-
-
Clarity in Decision Making, from Org to Architecture
Clear boundaries, ownership, and guidance across org structure and software architecture empower teams to not get bogged down with compounding hidden coordination costs.
-
Aligning Software Teams
Without clarity and alignment software teams risk interpreting activity as progress.
-
Github Action for Javascript Vulnerability Scanning
Third-party JavaScript can become a liability without you changing a single line. A GitHub Action that scans loaded JS libraries against Snyk's vulnerability database on every push and weekly.
-
Dev Team Productivity - Technical Practices
Busyness and productivity are not the same thing in software teams. A twelve-point rundown of the technical practices — version control hygiene through observability — that actually move the needle.
-
Goodbye Broken links: Ghost + Muffet + Github Actions
Link rot is invisible until a reader hits it. Muffet + GitHub Actions turned broken link detection into a CI check that runs on push, schedule, and content updates.
-
Book thoughts and notes: Accelerate
Accelerate is the rare software book that brings data instead of opinions. It ties deployment frequency, lead time, MTTR, and change failure rate to real business outcomes — and has the receipts.
-
Shift Left on Documentation
Documentation is most accurate the day it's written and wrong when needed. Shift left by making docs executable, generated, or version-controlled — leave hand-crafted prose as the last resort, not the default.
-
DevOps Book Trio
Most DevOps books are one person's opinion. This trio earns more trust. The Phoenix Project, The DevOps Handbook, and Accelerate in sequence: story first, then implementation, then data.
-
Continual Transformation
Renaming things Agile isn't transformation. What separates useful change from ceremony: eliminating waste and making small, steady investments in delivery capability that compound.
-
Constraints, Chunking, and Confidence
A 48-hour deadline teaches scoping faster than any process ever will. A Ludum Dare game jam as a lens on prioritization, chunking, and the delivery confidence that transfers to real projects.
-
Great Software Teams IMHO
Great software starts with hiring, not process. Six maxims that hold across company sizes — vision, feedback loops, focus, honesty, passion, learning — from teams that consistently ship well.