[00:09] <valorie> mmmm, it's just like writing citations, IMO
[00:09] <valorie> do it first
[00:10] <valorie> you know what a piece of code is supposed to do, so write the test and then write the code
[00:10] <arraybolt3[m]> Either way it takes eternity.
[00:10] <arraybolt3[m]> I dunno, maybe I'm just writing my tests wrong.
[00:10] <valorie> citations: you find the info - write the citation, log it, then write your outcome 
[00:11] <valorie> the more often you do it, the easier it gets
[00:11] <valorie> gsoc students: "I thought you weren't a coder!"
[00:11] <valorie> I'm not, but some principles are universal
[00:12] <valorie> well, I code well in English
[00:12] <valorie> and "unit tests" for an article would be writing a clear objective
=== arraybolt3_ is now known as arraybolt3
[17:53] <tsimonq2> o/
[17:54] <tsimonq2> santa_: ping, no idea if you're here since Matrix is weird with names :)
[18:09] <RikMills> appears not yet