Code Monkeyism

Programming is hard by Stephan Schmidt

October 26, 2007

Graeme - the Grails bug buster

While testing Reposita with the Grails repository, I was amazed about Graeme who is the Grails project lead and recently became the CTO of G2One.

Scanning the Grails subversion commits and searching for bug fixes, Graeme seems to be a very very active bug buster. One in four commits is a bug fix. Perhaps this directly contributes to the Grails success story. I hope he keeps up fixing bugs, now that he’s CTO.

See for yourself:

Graeme and Bugs

If you liked this post, subscribe to my free full RSS feed.
Filed under: Grails, Groovy and Grails, Reposita

You can share this post!
Do you want to tell others about this article? Use the social bookmark icons to submit this artice to the service of your choice. Thanks.

Get free updates by email

If you did like this article you can get free updates with your RSS reader, you can follow me on Twitter or get free update to new posts by email. Enter your email:

 
About the author: Stephan has been working as a head of development and CTO. He has experiences in different technologies since 20 years including Java, Rails and Python. Stephans main field of interest is maintainablity and productivity in software development. Want to know more? All views are only his own.

Comments

Marc Palmer

Stephan - you’re right Graeme’s da man when it comes to code, he is the lead dev after all. But what about the sterling contribution made by people who raise huge amounts of jira issues eh? :)

Graeme’s using radeox to generate some Grails docs I think… I feel some synergy coming on!

October 31st, 2007
stephan

Marc - best to have users and testers to find bugs. Without them, people won’t be able to fix them. I’ve added to the Grails JIRA too.

Radeox seems to be everywhere :-)

October 31st, 2007

Leave a Reply