TODO.md

• Talk about technical debt
• Grab material back from Savant codex
• Figure out where to put "reproducibility"
• Replace * with subheaders for all the checklist items?
• Writing project plans in programming
  • Influence of basecamp
  • Influence of Karen the boss lady
• How to teach (especially programming)
  • Teaching is different from documentation
    • Based off of Yocto training experience
  • Simplification doesn't require "babying" terminology
    • Not even for programming
      • "Filing cabinet"
        • Mention Cornell explicitly
        • The baby terminology took on all the complexity
        • And provides none of the benefit
        • SMBC voltage armidillos
    • Use the real terminology
      • You have to be willing to explain it
      • Maybe use a different term once to introduce
      • But then get them talking like a pro as soon as possible
  • Don't just do example projects
    • Might as well have people just start in at work then
    • Choose homework projects well
  • Actually teach theory
    • Concepts that are obvious to you aren't obvious to others
    • e.g. Yocto (call back) explain what Yocto's goals are
      • Yocto commands can then be explained relative to its goals
      • The example projects can then be chosen relative to its goals
• Go revise each section
  • Consider making it less of a check-list
  • Consider doubling down on check-list-ism
• Discuss Foundation Team
• Discuss hiring dev-ops professionals
• Discuss On-Call
• Revise in blog post on Napoleon
  • Better examples
  • Potentially add additional questions for lede paragraphs.
  • Include the part of blog post that shows Wikipedia's real lede about Napoleon.
  • Revise more.