>More Random Cramps

>Happy PI Day:

PI Day is March 14th. How many digits can you calculate it!

Soccer (Football) Seaon:

Well, it’s started again. Amazingly enough, I was actually looking forward to the start of the season. I was burned out from refereeing by the end of December, but started getting ansy again during February. So far, three games under the belt. Two centers, and line. Yellow card count so far, three (2 for dissent, 1 for Unsporting Behavior). Players come up with some of the most amazing excuses on how it couldn’t possibly have been him/her that just pushed their opposing player to the turf. I’m especially amused when I’m about 5 feet away from them when they do it.

Software Craftsmanship:

The Manifesto for Software Craftsmanship is now available for signing. I’m glad to see several members of the Eclipse development community have signed it. However, it’s only a very small percentage. InfoQ has a good roundup of blog/quotes from the group that crafted the Manifesto, it’s worth a read.

Code Contributions, Patches, and Clean Code:

One of those random discussion topics that pops up on #eclipse-dev brought up the topic of white-space and formatting of patches received from the community. I have tended to see developers complain that the formatting was changed, or that the patch contained more than just addressing the particular bug. First I’ll say, if the patch works, addresses the bug, and doesn’t change existing functionality, then I’m not going to sweat the details. However, in order for me to verify that it does not change existing functionality, it has to come with a Unit Test.

It’s still amazes me the amount of code that is checked in by eclipse developers with out unit tests for the code. Unit tests are a proven verification/development methodology that really should be common practice by now. One of the HUGE advantageous of Unit Tests is that they allow you to evolve your code and clean it WITHOUT breaking existing code. Worrying about whitespace is the least of our concerns when it comes to patches. If the patch fixes and CLEANS up the code to make it easier to read, then more power to the contributor for taking the time to fix up some ugly code.

To help your comfort level with accepting patches…make sure you have unit tests that cover at least 80% of your code. Unit tests are your safety net, don’t walk the high-wire with out it.

Twitter me this, Twitter me that:

I’m on twitter. Follow along with what I call a life and what I call a “reality”. Yes, I use a handle when twittering. The full title is King Argyle the Darner of Socks. Why that handle, that’s another blog entry for the future. By the way, Christopher Walken’s twitters are priceless.

This entry was posted in agile, eclipse, testing, xml. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s