Writing

Blog

Deep-dives on software architecture and the way source code is structured — written to be understood by beginners, yet useful to teams shipping at scale. Diagrams, real examples, no hand-waving.

Browse by topic

Source & Architecture

How to structure source code so it survives growth, teams, and change.

11 articles

Engineering Culture

The human side of building software — reviews, feedback, mentorship, and teams that grow people instead of burning them out.

6 articles

AI & The Future

Making sense of AI — from context engineering to building reliable, production-ready AI products.

9 articles

Perspectives & Field Notes

Personal reflections from work, learning, people, and the quiet moments that shape a career.

1 article

Ways of Working

How software teams actually operate and work together — from Agile and Scrum to how delivery really happens in big corps, startups, and outsourcing.

20 articles

Latest articles

Popular tags

47 articles

AI & The Future

Cognitive Debt in AI-Assisted Development: When Code Grows Faster Than Understanding

AI coding tools can make a team produce code faster than it can understand, review, debug, and safely operate that code. This article explains cognitive debt, how it differs from technical debt and intent debt, why agentic coding makes it more visible, and the practical controls teams can use: smaller batches, better PR rationale, human-owned invariants, disposable prototypes, and AI used to repay understanding instead of only generating more work.

Jun 17, 202615 min read

Ways of Working

Lean Business Analysis: Start from Value, Not Requirements

A practical introduction to Lean Business Analysis: why BA starts with value, how needs assessment protects teams from solving the wrong problem, and how a business case keeps decisions grounded without turning analysis into ceremony.

Jun 17, 202613 min read

Ways of Working

Lean BA Planning: Stakeholders, Elicitation, and the Questions Behind Requirements

A practical guide to Lean BA planning: stakeholder analysis, predictive versus adaptive BA rhythms, elicitation planning, and the difference between collecting stated requests and uncovering the need behind them.

Jun 17, 202614 min read

Ways of Working

Requirements Modeling: How BA Turns Messy Conversations into Shared Pictures

A calm, practical guide to requirements modeling: scope, process, rule, data, and interface models, with examples of how diagrams and structured descriptions help teams reason together before building.

Jun 17, 202615 min read

Ways of Working

Requirements Quality, Traceability, and Solution Evaluation: Keep the Promise After Sign-off

A practical reflection on the later half of Business Analysis: requirement quality, prioritization, traceability, change control, UAT, rollout choices, transition, and evaluating whether the delivered solution actually worked.

Jun 17, 202615 min read

Ways of Working

Software Measurement and Estimation: Fewer Gut Feelings, Better Engineering Decisions

A practical reflection on Software Measurement and Estimation: A Practical Approach by Linda M. Laird and M. Carol Brennan. The article focuses on the ideas engineers can use at work: measure from decisions, estimate as uncertainty instead of promise, track quality before release, and keep dashboards useful instead of decorative.

Jun 17, 202616 min read

Ways of Working

Agile Estimating and Planning: Estimates Are Conversations, Not Promises

A practical reflection from Mike Cohn’s Agile Estimating and Planning on story points, velocity, planning poker, ideal days, and why estimates should expose uncertainty instead of pretending to remove it.

Jun 17, 202613 min read

Ways of Working

Agile Release Planning: Plan with Value, Risk, and Real Feedback

A second reflection from Agile Estimating and Planning, focused on release planning: prioritizing by value and risk, splitting stories into useful slices, using buffers for uncertainty, and communicating plans without pretending the future is fixed.

Jun 17, 202618 min read

Ways of Working

The Design of Everyday Things: Make the Interface Explain Itself

A practical reflection from Don Norman’s The Design of Everyday Things for software and product teams: discoverability, signifiers, mapping, feedback, conceptual models, and why a clear interface should not make users guess what it wants.

Jun 17, 202612 min read