Articles from TnL
I believe a compelling view of the universe is the need for competition and cooperation as the only building blocks upon which we can grow. My quip of, "all growth comes from conflict, but not all conflict leads to growth" is true, and I think Competitive Cooperation is an explanation of why, and how to look for the right kinds of conflict.
There are a lot of different software engineers out there, with different values. One of those values is sometimes "speed" measured only in the initial task work, and expressed in stupid statements like the famous "move fast and break things." The attitude of creating something working and then polishing it later is a problem. It misses the point.
I have incepted a pattern at a few big tech companies that my friends worked at after they did some side stuff with me. It makes your life testing against a database way easier. You'll never look back once you've got it going.
In computing performance, direct instructions are fastest, but are difficult to program. In code, indirect seems elegant, but just ruins cognitive ability. The balance should lean towards directness. Indirection may not be bad, but it's only good in small quantities.
Good fences make good neighbors. This is the most important concept in cooperation and coordination of work. Ostensibly I'm talking about software engineering, but it's also true of everything in life. Everything.