Please enter at least 3 characters 0 results for your search

How *deeply* broken can software get?

How *deeply* broken can software get?

I tend to "spend" a lot of keystrokes on various aspects of technical debt and/or poor engineering practices. The list seems endless: component coupling, shallow modeling, leaky boundaries, inconsistent conventions, not-sufficiently-expressive design, incapacitated development agility, unnecessary layers of indirection,…

Read More

Once an anti-pattern: Anemic Domain Model

Once an anti-pattern: Anemic Domain Model

TL;DR Many of the most commonly used patterns & "conceptual industry standards" in software development have their roots in Object-Oriented design. However, it's time to realize that OO is not the only viable way this day, so…

Read More

The most undervalued of all patterns

The most undervalued of all patterns

We 'like' to put blame on factors that (in our opinion) lie beyond our control - stone-carved deadlines, outdated legacy, unimaginative Product Owners who always dump tech debt-related work items into abyss of Nice-To-Have. Some call it 'victimship' & it's…

Read More

State pattern, tech debt fertilizer

State pattern, tech debt fertilizer

A short post about unreasonable usage of State pattern - something I keep seeing every so often in code (regardless of language / platform). What's a State pattern? State pattern is a way to encapsulate state (& behaviour that depends upon…

Read More

Stuff I've found on the web: exception handling policy lib - Polly

I have a weak spot for the policy design pattern since ol' good C++ times: I think it has all started when I've read one of Sutter's / Alexandrescu's books with some great examples of policies injected via template parameters. This…

Read More