I never realized how sloppy my use of observability terminology was until I read the OpenTelemetry documentation.

I’ve been thinking about the estimation books sitting on my shelf. Why haven’t I read them? For some reason they don’t seem as critical as other reads. Estimation may be taking a back seat to improved iterative process.

I generated a visual while trying to reconcile the iDesign and Clean Architecture architectural patterns. The visual helped cement some important ideas, but I never published it. Here I’ll revisit the visual and review how my ideas have changed.

This series clarifies the Open-Closed Principle with examples. This post recaps what we’ve learned

This series clarifies the Open-Closed Principle with examples. This post describes some approaches that may look like the OCP, but don’t deliver the expected value.

This series clarifies the Open-Closed Principle (OCP) with examples. This post applies the OCP to the system level with architecture patterns like ports and adapters.

This series clarifies the Open-Closed Principle with examples. This post will demonstrate the OCP through interchangable and composable dependencies.

This series clarifies the Open-Closed Principle with examples. This post will demonstrate how the OCP can be achieved through flexible behaviors like callbacks.

This series clarifies the Open-Closed Principle with examples. This post will demonstrate how the OCP can be achieved through flexible data.

The Open-Closed Principle, one of the SOLID principles, is crucial to reusable code and insulated problem domains. This series will clarify the principle with examples.