Everyone likes the efficacy of the bite-sized quips and trivia, but the main problem with them is that they tend to become domain specific, and border on non-se

Everyone likes the efficacy of the bite-sized quips and trivia, but the main problem with them is that they tend to become domain specific, and border on non-sensical when you shift domains. From my standpoint, the best that can be done to further the engineering side of software is to educate on a paradigm basis, and to avoid misleading case-by-case tips. Read, teach, or create definitive guides to coding styles, architecture strategies, and the benefits and drawbacks of making data more or less structured or "smarter" (more code-like). Demonstrate not just ideal use-cases, but imperfect ones, since real world code usually ends up with a lot of imperfect solutions. It should be fun to explore all these different techniques. As it is, they're spread out in bits and pieces, and the really comprehensive works tend to be found with "getting-started" tutorials and CS literature.