More often than not we're improvising software architecture as we go. When it is not it is usually over-engineered. What if we adopted an incremental approach to architecture?

Architectural improvisations

There are problems in the software industry that have been solved a hundred-thousand times, and will be solved a hundred-thousand more. Rather than re-inventing solutions to these common problems we should be engaging in a discussion about meta-development practices instead.

Boring Complexity

This post shows an example about how object capabilities can be used in a CRUD application to defer authorization to individual models.

Using the object capability security model in C# CRUD applications

A comment on dealing with anxiety, depression and uncertainty

About social media, advertisements, and psychological trauma

The social media landscape had changed significantly since I first started using MSN. Since then the role of status updates had changed, moving ever further away from facilitating personal interaction.

How there is no longer a social dimension to social media

Please no LLMs interfere in my note taking process.

Noisy language models

The aggregate is a well understood concept within DDD practices. The addition of event sourcing to the mix might however complicate things, and the once pretty domain is now in shambles. In this post I'll cover the addition of ES, while keeping the awesomeness of DDD in place.

Creating event sourced aggregates with C#

How complex software impacts your cognitive abilities

I hypothesize that a codebase which can be navigated by logical rules provides greater accessibility than one that must be navigated through memorization. This is one of the reasons why small teams could benefit from a layered architecture.

The benefits of constraints in a layered architecture

Using aggregates in actor systems

Complex systems and cognitive strain

How code quality positively impacts the accuracy of estimates

Logging statements have no place in the domain. There are multiple better alternatives you should use instead!

How to effectively observe the runtime behaviour of your core domain

To make a system more maintainable its temporal characteristics should mimic the way humans perceive the passing of time. Coherence should bind the past and the future through the present, whereas continuity should explain the present by the past.

The importance of time and coherence in event sourced systems

This post attempts to explain event sourcing through examples showing what it is and what it is not, while highlighting some of the strengths and reasons for using it.