wjbuys.brain.to_blog

=> ruminations of a rubyist

17 January 2011

The developer's creed

While updating my CV earlier this week, I was confronted by a gaping hole in the ‘Personal Statement’ section. It always seemed like a very touchy-feely thing to put into a document that will be scanned by potential employers. And yet, the ever-helpful popup hint next to it clearly said: ”Never skip the personal statement” (in bold italics no less). Obviously, if the guys at Stack Overflow think that it’s that important, you probably should too.

So I set out to put my feelings about software development into words. After much introspection, deliberation, looking-up-of-links, fretting-over-formatting and other increasingly creative forms of procrastination, I settled upon a set of principles that are important to me. Inspired (very, very loosely) by the concept of the Credo, I came up with one of my own:

Credo in artem (I believe in craftsmanship)

I care deeply about crafting high-quality software that matters.

In my toolbox I have the flexibility and productivity of Ruby combined with the performance and stability of C# or Java. All of this is tied together neatly with a philosophy rooted in Agile principles.

I believe in the power of writing executable, business readable specifications.

I believe in the value of crafting clean, maintainable code.

I believe in the necessity of continuous improvement of process and mind.

I believe in a future of Open Source Software

It will be curious to see how these evolve in the future. After all, this would have looked radically different only a few short years ago (especially in the bits where it says “ruby”).