Since code swarm is open sourced I’ve used it to visualize the CMS application I’m working on at my company (SourceMedia). The video depicts over one year of commits history to subversion. Different colors represent different file types: red – source code, blue – jars, orange – images and green – configuration files.
I can’t say I’ve learned much from it, yet it’s an interesting first step that tries to convey the work done during a development of real world apps.
I’ve been programming for the past fifteen years. I still feel like I don’t know shit. Maybe that’s why I love it, it’s feels endless, every time I learn something it’s like opening a door to a new room that has another five doors in it. I guess it’s true about a lot of things, and that some people can find this infinite quest discouraging, but I feel it’s the fuel that keeps me motivated every morning going to work.
Hell, I’m not saying write your own language like Fog Creek people did, I’m just saying let’s all spend a little more time programming, understanding the fundamentals and try connecting them to the tools we use, and problems we have to solve, and less time writing posts in forums of some popular framework we “must” use.
I hate writing, I suck at writing, I will procrastinate writing stuff as much as I can (and even way beyond that). I’m even writing this post instead of writing some paper for school (something about conflict management if you really want to know).
So why start a blog probably nobody will read and add to the endless noise ?
Well, you might call it mid-year resolution, but I decided to confront my writing daemons as Jeff Atwood suggests and maybe in the process suck less at writing, and today I’ve got additional support after reading Steve Yegge’s (my new favorite blogger) post about why you should start a blog.
Working in the software industry for quite some time (and still loving it), I find most programming blogs, books, forums, references and most form of documentation totally lacking one major aspect: explaining why make certain choices, talking about trade offs, and giving good end to end examples that don’t revolve around: cars, music instruments or pets. So I thought it’ll be a good place for a mind dump about programming decisions I face every day. As Yegge says, writing about something help clarifying it to yourself, and maybe other people can help clarify it even further.