Commit messages are revisionist history.

But seriously, you only see their final success, not the wrong turns and simple print statement debugging along the way.

Chasing a bug that only repros on a version of macOS that can’t run the version of Xcode that I need to build the app on.

TIL…well I set out to learn about zombies and memory debugging tools in Xcode. Instead I learned that sometimes memory graph is mysteriously unavailable, and I can still get by with some custom breakpoints.

I’d like to say “TIL about NS_TYPED_EXTENSIBLE_ENUM” but really today I just discovered that it existed and don’t actually get it yet.

This social media privacy stuff isn’t new, just more interconnected. Shortly after I got engaged over a decade ago, the sidebar of gmail quickly filled with wedding planning ads. It was easy to see the correlation with my email messages.

I’m okay with markdown, but haven’t mastered using micro.blog’s iOS app to post a photo with an accessible caption. Anybody got example syntax please?

I’m seeing a strange thing on some websites…I have to tap below a link for the tap to land on the link. Could be only on iPhone X. I wonder if these websites are getting safe area inset wrong.

I annoyed a bus driver today. I feel bad about it. I really wish ALL Seattle buses had location tracking on them. My usual bus does, but I got up early.

Alternatively, if you’re pondering a conference’s lineup, what types of talks are you drawn to? People skills, intro to tech you haven’t tried, advanced details of the tech that pays your bills?

If I want to keep speaking at conferences, I should have a talk ready. If you’ve seen me speak, what aspects of my talks do you think I should retain? (recent-ish talks: Bug Hunting; Safety, Fun & Learning; An Affine Transform Playground)

I want a “Hey Siri, resume iPhone audio on the HomePod.” I was in the middle of a good iMore podcast in the car, and don’t want to go through a bunch of taps (and remembering which app I was in) before I can keep listening.

TIL: If your code crashes because an NSArray has things of the wrong type and can’t be bridged to Swift, you can still safely peek at the NSArray while stopped in the Swift file with (lldb) po misbehavingArray as NSArray

You can tell a friend orders Blue Apron by the pile of leftover garlic. Related: anybody got a favorite recipe that uses multiple heads of garlic?

Extra doses of quality time with shiny people lately. I’m grateful. They’ve been well worth the late nights.

Like working behind the scenes on a theater production, it seems like a developer’s best work is sometimes the stuff you make look so easy, or that even goes unnoticed. Bugs caught before committing, architecture that’s easy to maintain as the world changes.