Software Theory

One of the more common reactions I hear when engineers first encounter a message broker in a service-to-service communication context is that it feels like overengineering.

Distributed systems earn their bad reputation for debugging mostly because of how they’re designed, not because distribution is inherently opaque.

There’s a line of thinking in software engineering that treats bugs as interruptions — things that pull you away from the “real work” of shipping features.

A year into working at Nubank — where the backend runs almost entirely on Clojure — I’ve had enough time to form a real opinion rather than a first impression.

We’ve all been in the situation where the LIKE operator in SQL isn’t good enough for the needs of the task at hand.

Throughout my career I’ve noticed many books and courses that promise to teach you everything you need to know about a programming language or software methodology in 24 hours, 7 days, or a month.

Implementing Aspect-Oriented Programming (AOP) in .NET Core 2 was an eye-opener.