TBH, most emails should be a work session.

The hardest part of being in technology is changing people's minds.

Stubborn is not a strong enough word.

Dependencies due to our company's team structure make them required unfortunately. I wish we were truly value stream aligned.

After several years of training teams and working with my own teams I am convinced that, for any product larger than a POC, writing tests first is faster than writing no tests.

My team says "thank goodness we have those tests" at least once a day. Every day their belief in TDD, CI/CD, feature flags, and mobbing gets reinforced.

Ah, well then you might get away with it. I would also nominate inflow/outflow. Flow is associated with a lot of good Lean principles.

You are not your customer. Do not replace their needs with your intuition.

"Excuse me, have you seen my son?"

I wish Junkyard Wars was still a thing on TV.

Not going to be as punchy and marketing friendly.

Who is your target audience? Developers, designers, managers, or leadership?

Forced updates are the devils work.

I like it.

RDBMS's really are a great way to persist data and fit many scenarios. But CSV and JSON files are also quite good.

Use the simplest possible thing that could work, not the thing with a bunch of bells and whistles just because it has them.

I'm bored, sad, and lonely, the only obvious thing to do is switch all of my debian systems from bookworm to trixie.

The truth is, once you learn one programming language, others are a lot easier to learn. Also, the more depth of knowledge you have about the one language the easier it will be to learn others. Never feel bad for what you know, no matter how small it seems.

You can't make a story too small as long as you keep it vertical.