> Don't fight the tools: libraries, language, platform, etc. That means you'll always be stuck doing things using existing paradigms. Which is fine if you're o

> Don't fight the tools: libraries, language, platform, etc. That means you'll always be stuck doing things using existing paradigms. Which is fine if you're only developing an application, but not fine if you want to effect more fundamental change. > Never start coding (making a solution) unless you fully understand the problem Sometimes, I cannot understand the problem until I've started coding. > Tech debt is like fast food. Yes, in the sense that where I work, many people have it every day :-( > go for this priority: Security > Reliability > Usability etc. I don't buy that gradation. > Don’t use dependencies Contradicts a bunch of other points IMHO. > Any function that’s not pure should be a class. No. Verbs are not nouns. But - if he means functions with static variables, then maybe. > Software is more fun when it’s made together. Build a sustainable community. Very difficult in my experience. In a commercial setting, the company controls your software, and it's a totalitarian 'community', if at all. With your pet projects, it's often difficult to attract users to participate more actively.