Two kinds of complexity: essential and accidental.

Most teams treat them as the same. The work is choosing which kind you're holding.

Dependencies are a loan against future maintenance.

You owe back what they owe upstream — every breaking change, every deprecation, every CVE. Read the lockfile like a contract. The interesting question isn't can I add this; it's am I willing to maintain this if the maintainer disappears tomorrow.

Most "we should automate this" is actually "we should stop doing this."

Automation makes a wasteful process cheaper. It does not make the process worthwhile.

The one painting in a museum I keep coming back to.

I couldn't tell you why. The not knowing is part of why.

I started writing thank-you notes by hand again.

It's not about the note. It's about the half-hour I sit with the person before I write.

I stopped sending the snarky reply, even in private.

The snark accumulates somewhere. Better not to manufacture it.

The friend who texted "no need to reply" and meant it.

I read it again two weeks later when I could. The not needing to reply was the gift.

Watching shows isn't rest. It's lower-grade work for a stranger's attention.

The body is still. The eyes track. Cortisol responds to the dramatic beats. Real rest leaves me with energy at the end. The screen leaves me with fewer hours and less of myself — and a quiet itch to watch one more, the way bad work always wants more of itself.

Most "the codebase is messy" is actually "we don't share a mental model."

You can rewrite a clean codebase into mess in two weeks. You can keep a tangled one tidy if everyone reads it the same way.

I told my team I'd say no to anything that wasn't on the quarter's three priorities.

The hard part wasn't saying no to others. It was saying no to my own ideas — the side projects I started in week two, the calls I felt obliged to take, the help I offered before checking what it would cost. The team's discipline was easier than my own.