Whenever we discuss a paper in my distributed systems class, I randomly split people into six groups and they spread out around the building to talk, while I walk from group to group. The groups are different every time. But so far, every time, I'm able to find five groups, while the sixth group goes off somewhere and I can't find or communicate with them until they eventually wander back to the classroom five minutes late.

I feel this is rather appropriate for a distributed systems course.

Did you know that I have a really cool color theme called Witch Hazel for VSCode @code & others?

🧙‍♀️ https://witchhazel.thea.codes/

@cdonnellySRE Stare not into the void lest you become known as the void domain expert.

(Overheard from a wiser person than me.)

One of the hardest and most valuable things you can do as a company is the following:

1. Have a fully up to date org chart
2. Have a diagram that is not the org chart that accurately reflects how work flows through the company
3. Have an up to date and accurate diagram and explanation of what the company does and how it does it (architecture, revenue funnels, business value streams, code-bases)

Scaling decision making is *impossible* without a shared context to build alignment off of.