Engineering a culture
oxide.computer
oxide.computer
What Oxide have built is a great Engineering firm. Other than not tracking engineering metrics, the implementation details you listed are exactly what I try to establish in all of the engineering teams I join.
I’d love to hear what your sync & discussion meetings look like? I find in a highly cohesive team the discussions are never ending, and very fruitful, posing an interesting challenge of how to conclude them.
IMO many of the things listed are just side effects of this type of culture and the culture is 99% decided by the existing culture at founding time and hiring processes.
You can’t have a demo day without hiring intellectually curious people who like to share. You can’t pay a flat mid-tier salary with options that punish all late arrivers without just refusing to hire people that value their labor higher.
I’ve seen this mistake made at many companies. The critical piece is your hiring, retention, and performance management.
The rest of the stuff around meeting styles, knowledge exchanges, etc is all an emergent property of the team.
Engineering culture cannot be engineered. You can cultivate it by pruning out the personalities you don’t like and figuring out how to select for the ones you do like, but that’s about it. Changing the culture otherwise is pushing a boulder uphill.
Cannot be understated how difficult it is to get this balance right. Especially in small companies where you get to work with “old timers”. Push too hard and people shut down. Don’t push enough and it all unravels quicker than you would think. To give a concrete example; In a firm where openness and async collaboration is critical, how do you push someone who always DM’s to use public channels instead, without making them uncomfortable?
https://docs.google.com/document/d/1Xtofg-fMQfZoq8Y3oSAKjEgD...