I started working on Sider roadmap. It's helpful to have a good roadmap to maintain focus and work on projects. It's something I should have done it much earlier.

I have ideas about Sider 4 versions ahead. At some point, I want to put them all in writing for everyone to see, but with upcoming release I'm short on time and might not be able to finish it. If not I will complete it shortly after release.

My goal is to have full design doc online (preferably in wiki). I want for people interested in Sider to have an understanding of the platform and maybe share ideas on what can be improved.

I have only a portion of it done and it's not in the form I would to put it online yet. I'm working on improving it and will start moving it to wiki, but there's so much to do, that I'm not sure when I will put it online yet.

I came to realize importance of design documents through my recent experience. I used to think I could get away without one. No, not really. Writing design document forced me to think about different aspects of Sider and understand the whole picture much better. I had hard time focusing on my work (jumping between different things) without it and my overall design is not nearly as good as I want it to be. After I created a large portion of the document, development became much easier and more enjoyable. I started to get things done quicker and understand the whole project scope better.

My main argument against writing document was bureaucracy. I was afraid I would end up with a large, hard to read or navigate document. I didn't want to spend all this time creating something useless. Maybe I just wasn't ready for it. Anyway, when writing it I used [wikipedia:MindManager] instead of word processor. [wikipedia:Mindmap] helped to put all my ideas down in writing and quickly organize them, but I think wiki is actually more suited for reading the document with its support for free linking between different pages.