Show more

Today's a good day to read that book you already own instead of buying another one.

Every day's a good day for that.

I own a lot of Audible titles. Like, a lot. Dang.

Tagging is so much better than directory arrangements in so many contexts.

I honestly enjoy writing Standard Operating Procedure (SOP) docs.

I take The Checklist Manifesto to heart (

The smaller the platform or service that you build, the less you have to document.

Really loving my current client assignment. This feels like the strongest embrace of (lowercase A) agile principles that I've experienced across my career.

Seeing interfaces in code with a leading I (for Interface) makes me sad.

The whole point of interfaces is that consuming code doesn't need to know if something is a specific class or just implements an interface.

Let's see if I can cut down on caffeine this month.

Imaging a programming language type system that distinguished between floats with different precision, e.g. 0.1 couldn't be mixed with 0.100 without explicit conversion. Maybe some older languages do that?

It's wild how many large companies with entire UI design teams can make interfaces that are less efficient for users than individual, independent contractors were writing in the 90's.

How do you put your game face on for your stand-up?

Learning a lot about CQL (Clinical Quality Language) on the job this year:

Thinking about WebRTC as a vehicle for maintaining serverless backups between one's own devices.

I think every Computer Science degree program should start with a mandatory class covering Algorithms to Live By:

A refactoring metaphor:

"It's time to do the dishes, even those pans that have to be scrubbed, because we've been ordering takeout every day."

What does "ordering takeout" look like on your project/team and what are your internal metrics around it?

I don't like it when official docs for a programming language/framework/module/etc. point to a Medium article. (Looking at you, React.) Please inline that for posterity/to limit the harm of paywalls.

Thinking about how much "tech debt" can be better understood as "leveraged tech."

It's created with the assumption that future returns will exceed the inevitable costs.

This may sound essentially the same as consumer debt but businesspeople could (ostensibly) hold a greater appreciation for how leverage could destroy the business much more readily than debt.

Presenting an introductory talk on today. Wish me luck!

Show more

A Mastodon instance running on Thoughtworks infrastructure for its employees to interact with the Fediverse.