On Labeling

I've noticed a theme that has come up a lot recently across multiple conversations with people that I've had at work. When the topic arises it mainly seems to be associated with the discussion of values. Most of the time it's just a thread in a bigger conversation, however this time it became a main theme while I was talking with a fellow co-worker and friend in slack and I thought that it would be fun to capture it.

Here's a redacted version of the conversation:

Erik Lopez

[7:36 AM]

did you like the book “the art of readable code”?

Blake Dietz

[8:09]

I did like the art of readable code. I use concepts that I learned from it almost every day.

Erik Lopez

[8:38 AM]

I am reading the wiki page on it

[8:38]

and it seems really rad!

Erik Lopez

[8:47 AM]

in some sense, the nuggets of coding wisdom on that wiki page seem self-evident to a degree but it is nice to see it concretely written

Blake Dietz

[9:08]

in some sense, the nuggets of coding wisdom on that wiki page seem self-evident to a degree but it is nice to see it concretely written

Yes, but it can be important to discuss those things and to label them. When assigning a term to ideas the very act of doing that can be valuable within an organization. It's a way to compactly communicate > values.

Erik Lopez

[9:08 AM]

TRUTH

[9:11]

I really love what you said here: (edited)

[9:11]

Yes, but it can be important to discuss those things and to label them. When assigning a term to ideas the very act of doing that can be valuable within an organization. It’s a way to compactly communicate > values.

[9:11]

I think that alone sometimes gets overlooked and people assume that these things are just understood

Blake Dietz

Blake Dietz is a software engineer that lives in Boise, Idaho. He enjoys mountain biking in the Boise foothills and tinkering on side projects in his spare time.

Read More