freenode/lisp - IRC Chatlog
Search
22:43:04
fiddlerwoaroof
flip214: maybe I should contact him directly, I'd like to pull things like author/title/etc.
22:43:39
fiddlerwoaroof
The last time I tried, I also ran into issues with PDF spec versions, I think
7:10:20
lukego
I was a good boy and write some unit tests but I'm already deleting them all because they are not worth the effort to maintain.
8:07:43
splittist
lukego: If I'm writing to a spec, or in the last throws of writing (or, at least, working out) a spec, then I find unit(?) tests to be useful. But if I'm 'exploring the design space' (i.e. coding without knowing what I'm doing) then I do find them a boat anchor rather than a sanity check.
8:12:16
lukego
splittist: I think that in this case I wrote some really basic unit tests as scaffolding to get some low-level routines working for the first time. but now I don't need it much because I've written other code that exercises these routines pretty thoroughly and I can just run that to get test coverage.
8:13:12
lukego
so it seems like my test suite will just try to exercise lots of relevant code paths and then I'll need to have enough "design by contract" style instrumentation to be able to catch and debug errors when/where they occur
8:16:25
lukego
(my case might also be special in that these are routines for importing data in a specific file format and it only takes three and a half seconds to import all such data that actually exists... so I don't really need to be prepared for inputs that aren't included in the test suite)