Culture is how people actually do the work — not how the company talks about it.

This is a subtitle for your new post

Culture is how you code, and how you build software, not the pizza, the ping pong table or the posters on the wall.


1. Culture is what people do when no one’s watching

  • Do devs write tests or skip them to hit deadlines?
  • Are code reviews thoughtful or rubber-stamped?
  • Do teammates help each other or stay in their silos?


That’s culture. It’s not the team lunch. It’s what really happens on a random Tuesday afternoon.


2. Culture shows up in habits and norms

  • Do people ship small PRs often, or sit on giant branches for weeks?
  • Are bugs logged and fixed fast, or quietly ignored?
  • Is refactoring encouraged or punished?


3. Values only matter when they cost something

A company might say they value “quality,” but:

  • If managers push for shipping fast and punish delays,
  • If teams never invest in tests or tech debt cleanup...


TL;DR:

Culture isn’t what’s written or promised — it’s what’s practiced.
It’s the real, everyday choices people make to get the work done.