Avid international public speaker. Resigned & begrudging generalist developer. Mental health advocate & grappling with my own experience daily. Opinionated blowhard. Not secretly a goat.
Typically I say "one-zero" if I'm "pronouncing" binary as binary, instead of translating binary into a number for the purposes of working with that number. This in the same vein as hex, where you recite each number/letter in turn, since English doesn't have premade words to turn "1A" into "a-teen".
October 30, 2025 at 1:20 PM
Typically I say "one-zero" if I'm "pronouncing" binary as binary, instead of translating binary into a number for the purposes of working with that number. This in the same vein as hex, where you recite each number/letter in turn, since English doesn't have premade words to turn "1A" into "a-teen".
The fact that we frequently prefer interactions and experiences that feel cognitively easy is also a reliable illusion. We experience this in our learning all the time.
This is also why I'm skeptical of any idea that developer experience should only be about making things FEEL easy
October 24, 2025 at 3:22 PM
The fact that we frequently prefer interactions and experiences that feel cognitively easy is also a reliable illusion. We experience this in our learning all the time.
This is also why I'm skeptical of any idea that developer experience should only be about making things FEEL easy
Engineers like challenges, but we tend to be selective about what we consider a valid challenge. "I need to build this despite shit code /politics / lack of resources..." The mindset switch is that all these things are not inhibitors to solving the problem, they are part of the problem definition.
October 8, 2025 at 8:53 PM
Engineers like challenges, but we tend to be selective about what we consider a valid challenge. "I need to build this despite shit code /politics / lack of resources..." The mindset switch is that all these things are not inhibitors to solving the problem, they are part of the problem definition.