He’s writing a list as part of his imaginary shower argument with his boss and coworkers as to why they are all inferior and he’s perfect and why all the problems they are facing are easily attributed to his list of 50 points of things he feels he does that they are failing to live up to.
At least that’s my take away.
Mind that this instinct was born from prior experience with my own imaginary shower arguments.
Put differently, something you consistently find when you postmortem incidents where people have lost their SA is that they thought at the time they had full SA. They only notice they've lost it when things are clearly going downhill.
So it's important to regularly re-ground yourself with reality even if you think you don't need it. That's a critical component of maintaining SA.
That gets swept under the rug far too often.
This list makes it clear that communication (of designs, of status, of workarounds, etc) is vital for the professional software engineer.
And it's showing. There is so much emphasis on communication, people started equating quantity to quality. "Just talk more, that's what great communication is about" wouldn't be an observation too far from the truth.
Far too little is invested into researching what makes quality communication. It's just the same old rational arguments against rational arguments, day in, day out. For a field entirely about managing and sharing information, be it to machines or to people, that's pathetic.
If people are so certain it is better and believe it is important, let them stake money on it and do research. Until then, the cat is both dead and alive.
Clear lines of communication
Culture of communication
Strong vision and storytelling
Open discussions and inclusive of disagreements
Managing "up"
etc
Communication is hard.
There are certainly some valuable concepts - but the presentation is fairly incoherent (including the video of the talk he gives) and not particularly helpful.
Many of these items are utterly unrelated: Some are fairly specific to gaming (profiling/memory layout/timing) some are basic professional expectations (I can schedule my time well). In neither case is there real advice for people who actually struggle with some of these areas.
My item number 51 would be... "I can articulate my point in a more compelling manner than an incoherent collection of 50 things I don't like"