Antman writes software

This article was originally published on A Democratic Economy where are I write about an alternative way of doing business likely to result in a new economic paradigm and a better world.

Coupling is not intrinsically bad.

The Two Generals Problem is a mathematical theorem proving that no messaging protocol can reliably ensure that two parties share the same state.

As far as I can tell, there are six immutable fundamental problems faced by all commercial software.

Essential complexity is where software engineers are uniquely able to deliver business value, whereas accidental complexity is what some engineers think looks good on their resumes.

As applications scale, infrequent problems become significant.

How often have you seen this happen: The business is anxious that the product team is not kicking enough goals.

Much of the existing literature regarding team culture assumes a co-located team.

Application Performance Index (Apdex) is a standardised method for calculating the perceived satisfaction of a user accessing your service.

Recently I wrote an article about applying Functional Programming to Domain-Driven Design.

Domain-Driven Design (DDD) simplifies the development and maintenance of complex software applications.

In JavaScript, Array.prototype.map, Array.prototype.forEach, and Array.prototype.reduce are used heavily in functional-style programming.

The benefits of a Microservices Architecture are well known; they reduce coupling, allow independent deployments, and increase the rate of change in our applications, making product managers love us, finance teams applaud us, and CEOs offer us big bonuses.

It's a story as old as time, boy meets girl, girl falls in love with incomprehensible eldritch horror — oh wait no, sorry wrong story, this one is about TECH DEBT!

In some languages such as Java, methods or functions can provide type information about the Exceptions or Errors they may throw.

This article assumes you are familiar with the never type, exhaustive checks, and the concept of failing fast.

Those of us who use Trunk Based Development as the foundation of our approach to Continuous Delivery or continuous Deployment are familiar with the use of Feature Toggles to prevent work in progress changes becoming prematurely available to customers while

By removing the constraint of atomicity for a transaction, we can break up a long lived transaction T into several transactions: \(T_{1},T_{2},T_{3},T_{n}\) In order to maintain consistency, we must also provide compensatory transactions for failure cases:

Singletons are commonly used in Object Oriented Programming when we want to enforce that there is only ever a single instance of a class.

If you've used frameworks like Rails, Django, or even Hasura, you are probably familiar with the concept of "up" migrations and "down" migrations.