4 ms·
If your personal project is small and self-contained enough that you write it once and then you're done, then sure. My projects tend to be much larger, and be
by gwd 4y ago
If your personal project is small and self-contained enough that you write it once and then you're done, then sure. My projects tend to be much larger, and be works-in-progress. As annoying as it is, taking the time to plod along and do proper testing has saved me time and time again. If you only have a few hours a week to work on a project, the last thing you want to do is spend 8 hours (AKA 3 weeks) figuring out why something isn't working.
- moffkalast 4y agoReally depends on the size yeah. If you're working on some 20k+ code megaproject then it makes perfect sense, but for the average small side project I feel like the code and approaches change so quickly that you'd just spend half your time rewriting and fixing broken tests for no real gain.
- gwd 4y agoHmm, well my "small recent" project, that I got to my own personal MVP standards, is already at 2.6k lines of code; and my long-term project is at 9.4k lines of code -- not counting the little side libraries where I put more generic code I thought might be useful elsewhere. So, I guess you're not too far off.
- CRConrad 4y agoI got the impression that by "some 20k+ code megaproject" the GP meant 20k+ files, not LOC. But I could of course be wrong.