Honestly? Mainly, reviewing it and debugging it in my mind. It works - you should try it! It makes you a smarter and a better developer as well. The try-refresh-repeat cycle is for amateurs.<p>But that comes with the way I write my code - modular, i.e. broken into small, readable and reusable units. Well, if I&#x27;m doing a something that requires shaving off any redundant CPU cycle, that&#x27;s another story, but as we know, premature optimization is the root of all evil. You won&#x27;t see anywhere in my code long functions&#x2F;methods,  endlessly nested IF-THENs, and similar junk - writing simple, unfancy, DRY code drops the need for unit tests to almost zero. Using long, but meaningful identifiers drop the need for inline documentation.<p>I mean, I don&#x27;t have to repeat things that have been known for ages - just buy some old books, it&#x27;s all in there!<p>There are way too many coders today and very few engineers!