We've all been there: the dreaded "Your disk is almost full" notification on macOS. This week, I hit the wall. A 52GB folder of mobile backups, photos, and videos was choking my internal SSD.

But as an engineer, the thought of manually dragging-and-dropping thousands of files—or worse, manually deleting duplicates—felt like a recipe for disaster. One wrong click and a decade of memories could be gone.

Here is how I solved it using a "Safety-First" framework and a custom Python deduplication engine.

Read This​

Not every post needs to be a framework.

Some posts are better as reminders.

This is one of those.

A few things I keep relearning, and apparently keep needing to relearn.

Read This​

I think many teams would become healthier if leaders wrote more honest memos.

Not longer memos. Not more polished memos.

Just more real ones.

So this post is in that spirit.

Below are 5 memos I wish more leaders wrote, or at least communicated this clearly.

Read This​

Most people notice career growth only when something visible happens.

Promotion. Big title. Big company. Comp jump.

But a lot of career trajectory gets shaped much earlier and much more quietly.

By decisions that do not look dramatic at the time.

That is why I think career decisions compound quietly.

And because they compound, small repeated choices matter more than people think.

Read This​

Executive presence is one of those phrases that sounds useful and annoying at the same time.

Useful because it matters. Annoying because many people turn it into performance art.

I think the cleaner way to see it is this:

executive presence is not about sounding important, it is about creating confidence under pressure

That is very different.

Read This​

Being smart is useful.

Building a room where only your intelligence matters is not.

A lot of leaders do this without realizing it.

They become the fastest thinker, quickest responder, final answer provider, and unofficial escalation endpoint for everything.

From outside, it looks impressive.

From inside, it creates dependency.

And dependency does not scale.

Read This​

A lot of people think senior leadership means having better answers.

Not exactly.

Many times it just means you have to decide before the answer becomes obvious.

That is the real difficulty.

Not decision making with full clarity. Decision making with partial information, limited time, strong opinions, and visible consequences.

That is why I think one of the most important leadership skills is this:

being able to move with imperfect information without becoming reckless.

Read This​

Some leadership books are clean.

This one is not.

That is exactly why The Hard Thing About Hard Things works.

It does not pretend leadership is all clarity, confidence, and vision slides.

It talks about the messy part:

• uncertainty
• pressure
• bad options
• layoffs
• underperformance
• morale damage
• trying to act calm when you are not calm

That is real leadership. Not the LinkedIn version of it.

Read This​

A lot of engineering problems are not really architecture problems.

They look like architecture problems. They sound like architecture problems. They even get discussed in architecture meetings.

But many times the real issue is this:

team boundaries are wrong

That is why Team Topologies is such a useful book.

It helps you see something many engineering leaders learn the hard way:

bad org design creates bad software behavior.

Read This​

Some leaders enter a room and make everyone sharper.

Some leaders enter a room and make everyone quieter.

That is the simplest summary of Multipliers.

The book is basically asking:

Are you making people think better? Or are you making them wait for your answer?

This sounds simple. But in engineering leadership it is a huge difference.