Software Engineering
SOLID Principles Without the Strawmen
What each SOLID principle actually asks of your code, shown with realistic examples instead of Animal-extends-Dog toys.
3 min read
Tag
Software Architecture
9 articles
Software Engineering
Monorepo vs. Polyrepo: The Trade-offs That Actually Matter
Monorepos and polyrepos both work at scale — the real decision is which trade-offs your organization is already equipped to absorb.
3 min read
Software Engineering
Feature Flags Architecture: Beyond the Boolean Toggle
Release flags, experiment flags, and ops flags need different lifecycles — a flag system without a removal process always accumulates debt.
3 min read
Software Engineering
Managing Technical Debt Deliberately
Technical debt taken on deliberately with a repayment plan gets paid back; debt that accumulates silently almost never does.
3 min read
Spring Boot
Enforcing Module Boundaries in Spring Boot with Spring Modulith
How Spring Modulith turns package structure into an enforced architectural boundary, catching the coupling that code review alone tends to miss.
2 min read
Software Engineering
Naming as Design, Not Decoration
A name is a promise about behavior, cost, and side effects — bad names mislead quietly, and that cost compounds across every reader.
2 min read
Spring Boot
Decoupling with Spring Application Events and @EventListener
Using Spring's application event system to decouple side effects from core business logic, and the transactional pitfalls that come with it.
3 min read
System Design
CQRS Without the Ceremony
CQRS doesn't require event sourcing or a second database — a minimal, practical version of the pattern and when to reach for more.
2 min read
System Design
Event Sourcing Fundamentals: Storing Facts Instead of State
Why storing immutable facts instead of current state changes how you build, replay, and evolve systems, and when it isn't worth the cost.
2 min read