Something Old:

• Early Hooniversity notes (back when it was taught by ~rabsef-bicrym, ~risruc-habteb, and ~somlus-savlev)
  

  
  

Something New:

• Nvidia's DIGITS supercomputer (watch out tinybox!)
  

  
  

Something Borrowed:

• Sean Goedecke, “Mistakes engineers make in large established codebases” (h/t Hacker News)
  

  
  

  • Large codebases are worth working in because they usually pay your salary
    

    
    

  • By far the most important thing is consistency
    

    
    

  • Never start a feature without first researching prior art in the codebase
    

    
    

  • If you don’t follow existing patterns, you better have a very good reason for it
    

    
    

  • Understand the production footprint of the codebase
    

    
    

  • Don’t expect to be able to test every case - instead, rely on monitoring
    

    
    

  • Remove code any chance you get, but be very careful about it
    

    
    

  • Make it as easy as possible for domain experts to catch your mistakes
    

    
    

Something Blue:

• Aurora Borealis forecast tool (You know, just in case…)