Design
Open / Closed Principle
How to design software so adding behavior doesn’t mean reopening everything that already works.
Field notes from software engineering
Built systems.
Broken systems.
Better systems.
Notes on software, architecture, infrastructure, and the practical lessons that tend to arrive after the diagrams are finished.
Featured / SOLID
Single Responsibility Principle
Only one reason to change.
June 28, 2025 · 14 minute read
// keep responsibilities explicit
public class ReportService
{
private readonly IReportGenerator _generator;
private readonly IReportStore _store;
public Report Create(string id) { ... }
}
public class ReportService
{
private readonly IReportGenerator _generator;
private readonly IReportStore _store;
public Report Create(string id) { ... }
}
Databases
SQL Server Performance Notes
Things learned from real plans, real bottlenecks, and real production workloads.
Systems
Linux Archive
Old command-line notes preserved with context instead of rewritten as if they were new.
Architecture
Lessons that survived production
Patterns, trade-offs, and decisions that looked different after scale and time got involved.
Archive / 2008 → today