re: Coding practices your future self will love you for VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Here's another one: document your code. As in write a technical documentation of your code. It doesn't necessarily mean the document should be tech...
 

The one I'd add is (for my purposes) to the same end: docs, ideally, should be written in the same cadence as the code - update code, update doc, update code, update doc.
This is insanely turbulent for me.

Instead, I've adopted something between TDD and plain through-as-crap testing.

I can run the specs and flip through the its and get a complete understanding of what the code should (and should not) do, and how to make it do it.
Doc-by-test is much easier for me because I don't have to switch gears to keep it moving.

The "honest" benefits of testing are just byproducts lol.

code of conduct - report abuse