4 ms·

I quite often leave my code broken so that next time I open the solution I know exactly where I left off. I will often leave a comment there or throw("get X to

• jtheory 13y ago
  I do this as well -- once I have the complete solution to something in my head, I quickly go through the various parts of the codebase that will be affected and drop pseudo-code or even just rapid notes in each place -- which will intentionally break the compilation, so that I can use the compiler errors as a fast & direct way to pick up the threads again if I'm interrupted. For non-compiled code I'll add a dozen line breaks and a note in all-caps to make it jump out in a diff.
  • gbog 13y ago
    Great but using tests is better, because written correctly you will keep them and they will check forever that the thing is working