That's funny, cause I practice something I'll start calling "cost-free unit testing".
Step 1: If you're thinking about how a code api should act, sketch it out inside a test.
Step 2: If you're about to jump into a repl and poke at your code, open a unit test instead.
Now you've simply replaced other activites at no net cost to you. My core takeaway is that everyone tests their code somehow. You're best off if you can automate that process. Don't obsess over it (I almost never test my html/views), but try to find opportunity.
Step 1: If you're thinking about how a code api should act, sketch it out inside a test.
Step 2: If you're about to jump into a repl and poke at your code, open a unit test instead.
Now you've simply replaced other activites at no net cost to you. My core takeaway is that everyone tests their code somehow. You're best off if you can automate that process. Don't obsess over it (I almost never test my html/views), but try to find opportunity.