3.1 If it ain’t broke, break it3.1.1 Facing code rigidity3.1.2 Move fast, break things3.1.3 Respecting boundaries3.1.4 Isolating common functionality3.1.5 Example web page3.1.6 Leave no debt behind3.2 Write it from scratch3.2.1 Erase and rewrite3.3 Fix it, even if it ain’t broke3.3.1 Race toward the future3.3.2 Cleanliness is next to codeliness3.4 Do repeat yourself3.4.1 Reuse or copy?3.5 Invent it here3.6 Don’t use inheritance3.7 Don’t use classes3.7.1 Enum is yum!3.7.2 Structs rock!3.8 Write bad code3.8.1 Don’t use If/Else3.8.2 Use goto3.9 Don’t write code comments3.9.1 Choose great names3.9.2 Leverage functionsSummary