Archives

I've understood the cloud for a while now. Understanding it and building on it are different rooms, and I'm finally walking into the second one.

I assumed learning to build was a technical problem. Step zero turned out to be a mindset I have to unlearn my way into.

Every beginner's first AWS moment is 'access denied.' Here's IAM, the thing saying no, explained the way it finally made sense to me.

Networking was the corner of AWS I quietly skipped. Here's VPC, subnets, gateways and the rest, explained the way I finally understood them.

Writing about things I don't fully understand yet, on purpose.

Most POCs prove the wrong thing beautifully. A good one de-risks the single assumption the whole deal rests on.

Once I knew what the core services were, the next puzzle was how they pass work to each other. API Gateway, SQS, SNS and EventBridge, in plain words.

Every cloud conversation eventually hits the same fork: fix what's there, or build new. The answer almost never starts with technology.

EC2, S3, Lambda, IAM, the alphabet soup that runs the internet. Here's how a few of the ones that confused me finally clicked into place.

For years I could talk about the cloud without really understanding it. Here's how AI helped me finally build a mental model of AWS.

AI didn't make me a better listener. It gave me the room to be one.

The point of a prototype isn't to impress anyone. It's to make an abstract argument concrete enough to disagree with.

A small defense of watching cartoons as an adult.

The most useful person in the room is often the one who can translate.

A customer asked a question my sales answer couldn't cover. That was the day my job quietly changed.

The best deals I closed started with me talking less.

Why I finally started writing things down in public.