1. Find some known-good code you trust and measure coverage. 2. Find a few missing coverage lines. 3. Write tests. 4. Find bugs!
miniblog.
Related Posts
I find myself just taking photos of documents for submitting forms, rather than scanning.
Scanning still feels more 'official' (a PDF instead of a JPG) but the sheer convenience of using a phone wins every time. I've rarely seen organisations complain about photos.
Compiler error messages is such a deep topic. Even in rustc, a mature compiler that invests effort in diagnostic quality, I find interesting issues every few months.
(The majority have been fixed pretty quickly, so it's really rewarding to file issues.)
I'm trying mini projects to exercise my new programming language and find gaps.
So far I've done fizzbuzz, JSON parsing, and a crude scheme interpreter.
Any ideas for additional projects? They need to be well scoped because I keep finding e.g. stdlib crashes.