Well. I successfully burnt myself out in last week's orgy of productivity, but I seem to be recovering okay. Didn't touch Olive until late last night, when I managed to make and handful of small and one or two not-so-small improvements, but the milestone for beta 4 (the feed editing interface) is still just a stub.
Also, I promised Ash that I'd write her some docs (basically the same docs which have been promised to someone else for a ludicrous amount of time), so that needs doing. Being able to talk to her face-to-face about things finally gave me some good ideas for where I should start, so that's something. Of course, I'd like to do it in Mint, but Mint is still just a heap of potential and scraps of code, so I'll have to do it in plaintext. Editing HTML hurts too bad to even think about.
Tangential to that: should the Olive manual be a pretty HTML document with screenshots, or would it make more sense to structure it as a text document with ascii-art screens? My design-fag half says the former but the rest of me thinks that's stupid (graphical manual for a curses application).
I know that feeling all too well. I’ve amazed myself at times by materializing a few thousand lines of code out of thin air in a weekend, but I can never sustain that kind of productivity for any extended period of time, and it’s always followed by a long recovery period. Sometimes I don’t touch the code again for months on end.
As far as documentation is concerned, take a look at Markdown.
