My software stack

A week or so ago I stumbled across this blog, which went almost instantly into my RSS feed, due not only to the name of a post which cracks me up (yes, I know my humor is off ;P) but also to the posts I found really interesting.

And then I came along this post which got me thinking about what software I ended up using towards the end of my bachelors. Or the software I have learned of since, but wish I’d known about earlier. I began to write a comment to her post, but realized that it would be too long, so I write here instead. All credit to Hazel though, since without her post I wouldn’t have been inspired to write this one.

My list, as compared to Hazels, will not be as well-rounded, it won’t necessarily fit every student the way her list do. Also, the software I list will only be guaranteed to work in GNU/Linux, as that is what I used in the final semesters, and have continued to use since.

First of all, a text editor. It doesn’t really matter which, just evaluate a bunch until you find one you feel comfortable with. Once you have found “the one” become intimate with it. Become a frakking Jedi-master at wielding it. I’m still a padawan-level user of Vim, but I’m getting there.

I say the same about web browsers, mail clients and instant messaging clients. Find a good one, learn as much as you can about it, and use it effectively. Firefox, Thunderbird and Pidgin are my preferred tools.

A bug-tracker, although often web based creating a need for a web server, can often provide more “good stuff” than just tracking bugs. Stuff like statistics, or, if you think outside the box you’d be able to track things other than bugs, which I guess it was issue-trackers does. Some of these also include a wiki-system, which makes establishing a project-specific knowledge-base kindof easy. In the one university project where we used such a system (and where I realized its potential) we used Trac.

A blogging-system with an RSS-feed capable of being filtered on tags or categories could be used to distribute status updates to other members of a group. That I’m using WordPress should be fairly obvious to all.

Use a version control system wherever and whenever possible. With the next two suggestions on the list, “wherever” will be a lot more commonplace than one might first believe, even for non-programmers. At the university we had access to SVN-servers, and also tried Mercurial, a distributed vcs. Mercurial stuck with me ever since.

From generic suggestions, let’s go specific.

I could encourage you to check out markup languages such as reStructuredText or Markdown, to find one which suits you best and to run with it. And since I’ve now written the terms you’d need to Google, you could do that, but I’ll simply recommend LaTeX. The reason for markup languages in general, and LaTeX specifically is that you can then store your information in one plaintext format (which makes it easy to manage in version control) and can then transform it to a slew of other formats as needed.

Most of the time we needed to hand in PDFs. LaTeX excels in that and manages all the typesetting stuff and (obvious) formatting. Which leaves you with more time to focus on the content. One could also either extend LaTeX with Beamer, to create presentations, or simply generate a PDF and run Impress!ve.

For diagrams, graphs and flowcharts or representations of state-machines, Graphviz would be my recommended way to go. Again using plaintext to control the content, again with the benefits of version control. Inkscape saves files in the SVG format (again, plaintext) which might be usable (especially since it can also save files as both PS and PDF)

If you need graphical representations of statistical data or other plots, matplotlib could be the way to go.

I personally don’t like managing things, or management-related stuff, but lately I have been haunted by the feeling that if I used management tools, even if I would only be managing myself and my pet projects, I could be more organized and efficient. So I have started looking at TaskJuggler. It is similar to Microsoft Project, with the largest difference being that… you guessed it, you code the project plan ;D. Plaintext yet again. And then you compile the plan and TaskJuggler attempts to verify that no resources have been double-booked.

Considering each piece in this list on their own, it might seem like a waste of time to exchange one software with another. I do find each of these softwares impressive in and on their own, but it is when they are put together, when all their strengths are combined, that you tend to get the most out of it.

The all plaintext approach I have tried, both in groupwork at the university, and later on my own, work rather well. That so many of the softwares on the list can be used to communicate and transfer information between parties is also intentional as without communication the chance of a successful project outcome diminish rapidly.

The last (bonus?) item on the list would be to recommend learning, at least superficially, a programming language which you could hack together small scripts with. Something which you could use to “glue” together the other parts. I adore Python, and many of the softwares listed above have python-bindings ready to use. Perl, Ruby and others, which elude me right now, would undoubtedly work equally well or better, but as with the text editor, pick a language you feel comfortable with, and rock on.

Thoughts? Questions?

Update: Fixed broken link

Tags: , , , , , , , , , , , , , , , , , , ,

4 Responses to “My software stack”

  1. Hazel says:

    First of all, I just want to thank you for visiting my blog, I hope you enjoyed it.

    I completely agree with you that for group projects having a central way of tracking changes and bugs is vital, whether that is a page on a wiki or something more sophisticated. On my last group project, we also used Trac. On that project, we set up a central Subversion repository but for personal projects, I tend to set up the repository on a flash drive so I can always access it, even without internet.

    The list you’ve given here is really expansive, and I really appreciate the depth you’ve gone into for each suggestion. Thanks again for this post, and good luck.

  2. Patrik says:

    Well it evens out as I thank you for sharing your insights in your blog ^^
    The one project where we used Trac we also used Mercurial, I can’t for the life of me remember how well (or not) the Trac/Mercurial integration worked, but I remember that one at least should have been able to browse the current revision of the repository right there in Trac. Such things are cool ^^
    About housing the repository on a flash drive, are you using SVN for that, and if so how does that work, as I was under the impression that the SVN needs to run a service or something to be able to do its magic?
    Thank you, I’m glad you liked the post :) I wish you good luck as well.

  3. archie says:

    I do prefer Emacs over vim, but let’s not start a flamewar over that. :)

    However, I’m curios, what RSS reader do you use? I’m using Google’s reader, but lately I’m not convinced that it is the best one for usability. Especially in terms of getting a good overview of the posts.

    /archie

  4. Patrik says:

    Nah, no flamewars, unless it is with hesa ;)
    And as I wrote, as long as one is comfortable with the tool, who cares what tool it is?
    For RSS I just use plain old Thunderbird, I haven’t looked at the web-based alternatives, and of the desktop applications… neither one of RSSOwl or Liferea or some CLI-based one made me any happy. And Thunderbird… is perhaps not an optimal solution, but it gets the job done.
    Hope you found something worthwhile at mah blag so you are inclined to come back ;D