one of the best lines to ever appear in print IMHO
Also, the Margin Call speech is perfect
"There are 3 ways to make a living in this business: be first; be smarter; or cheat. Now, I don't cheat. And although I like to think we have some pretty smart people in this building, it sure is a hell of a lot easier to just be first"
1/ Perhaps the most important factor in deciding whether to build custom software or use a 3rd party provider is the cost of the "tech debt" on your company's balance sheet.
2/ Most people don't think about it this way, but when you build custom software, you are effectively buying a rapidly depreciating asset that's going to have to constantly be repaired.
3/ At the margin, it's almost always better to use a 3rd party software that's not quite as customized as you like b/c what you lose in personalization is more than compensated for by moving the tech debt onto someone else's balance sheet.
1/ I remember going to an unconference/hackathon in Vietnam and there was this moment where I realized all these 18-22-year-old Vietnamese students were smarter, hungrier, and harder working than almost anyone I knew in college.
2/ I like to think I was never particularly entitled, but to the extent that I was, meeting those people really woke me up.
It also showed me how many advantages I had to build on.
3/ It's really hard to overstate how important the "ovarian lottery" is and the extent to which that "luck" impacts your life trajectory.
Been going back through the Boyd/Guerilla/Blitzkrieg stuff lately and it's so obvious to me that the way in which companies function is going to be completely remodeled in that vein.
So obviously the future.
FEW UNDERSTAND THIS
I think the shift will happen as companies go more distributed, naturally lends itself to a guerilla structure with "multiple unsupported centers of gravity" as Boyd called them.
I think all of the hard tech is there, it's just a matter of re-engineering what is leftover of Taylorism.
The Toyota Production System/Theory of Constraints probably the most promising angle right now
1/ I have experimented with many different approaches over the last nine years to how to work with distributed teams.
Here's my current "best practices" approach:
2/ *General Guidelines*
a) Take spatial context seriously: If we’re discussing a specific task, we discuss it in the comment section below the task itself. If we’re talking about a specific document, we discuss it in the comments attached to the document.
3/ b) Poor communication creates more work. Getting in sync with your team and communicating to help your team stay in sync with you is not something annoying you have to do in addition to your job, it is a core and central part of your job.
If you could make a reading list that everyone who worked with you would be required to read, what 1-3 books would be on that reading list and why?
My list:
Getting Things Done
Work The System
Systems Bible/Seeing Like a State/Antifragile
Getting Things Done by David Allen - because you need to be able to trust someone to do something once they have said they will do it to make meaningful progress
Work the System - Because I believe you need to agree on a "systems first" framework for how work is done to be long-term effective.