Rebuilt a race calculator for this year's Gravel Worlds. Accounting for stopped time at checkpoints was a humbling experience; the 80-ish lines of procedural code to calculate ETAs took me about 4 hours to write.

Pretty happy to write it with a test-driven workflow; there aren't that many opportunities in "real world" coding for the "known input = expected output" algorithm implementation that this afforded. I don't know if there's a bigger gap between the enjoyment I get writing some categories of code with TDD, and the frustration I get testing other codebases

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!