The Natural Laws of Paper Deadlines

  1. Yes, no one will read your code. But it’s worth taking the care to design your system, from architecture to logging, properly. Shortcuts compound.
  2. Keep a journal. You will encounter the same problems twice.
  3. Write down your methods, especially after you submit the paper. Who knows, it may get accepted, and you may have to run more experiments.
  4. Collect every statistic you can think of. If you don’t, you’ll have to rerun everything on deadline day.

This is a working list.

 
0
Kudos
 
0
Kudos

Now read this

Fix: Including modules on singleton objects in Ruby

Two weeks ago I posted this. The idea behind adding methods to a single object still hold, but I made a rather egregious error. I am pulling a row out of the database, (abstracted by ActiveRecord) and then extending that Ruby object with... Continue →