Software the Hard way

Unless you’ve been living under a rock, you’re well aware of AI agents like Claude Code and Codex revolutionizing software development.

As an engineering leader, I’ve seen the following pattern play out multiple times, across multiple companies Executives complain about engineering velocity not being high enough.

Someone on Reddit once asked for “unethical career advice” for software developers.

XKCD #1425 I was reading a book on a lazy Sunday afternoon when I learnt something that completely changed the way I looked at one of the iconic movies from my childhood – Toy Story.

It sounds surreal to even say it out loud, but I’ve been living in America for the majority of my life, ever since I was a teenager.

As the CTO for an early-stage startup, I had put together a version-1 of the Principles and Best Practices for our engineering team.

One of the watershed moments of my life was as a 20 year old intern attending a workplace presentation about personal finance.

Suppose you’re working on a software system and need to implement user-logins using a userID and password.

Many years ago, a younger and more naive version of myself decided to try bootstrapping a startup together with my co-founder, while still juggling our full-time jobs.

As someone who loves discussing Software Craftsmanship and best practices, Test Driven Development (TDD) is a bit of a sore spot for me.

All around us, we are surrounded by crappy software.

Founder: Hey Joe!

I recently came across a story that is just as amusing as it is shocking: One of my clients is responsible for several of the world’s top 100 pension funds.

You and your friend are walking by a magic store and find a trick coin.

Over the past years, I’ve worked in multiple teams adopting very different strategies when it comes to feature flags.

Here’s a common pattern that I see play out very often in software teams: There is a need to change the existing system behavior to accomplish new functionality.

One of the most common debates I see, is on the right level of abstraction to use when coding.

I’ve been programming in Java for over half a decade, and thought I had mastered all aspects of overloading and overriding.

A dichotomy I often see in many different teams and projects, is the dilemma between “failing fast” and “failing gracefully.”

I can’t keep track of the number of articles I’ve read about hiring in the past few years.

No, there hasn’t been any new vulnerability found in SSH, nor am I denying the usefulness of SSH as a building block in the dev toolchain.

The following is a post which I found on the Blind app.

The conventional view of Software Testing The hardware and software worlds may seem poles apart, and in many ways, they indeed are.

I have a confession to make.

As a computer engineer who has spent half a decade working with caches at Intel and Sun, I’ve learnt a thing or two about cache-coherency.

When you run into a problem, a bug in your code, how do you try to fix it?

When building Caucus, my first personal project, I had a couple of core goals and philosophies that I used to guide all my decisions.

There was a time when I had never seen nor touched an IDE.