Speaking At November OCJUG Meeting

Posted in: Cloud Computing

Just a reminder that I will be speaking at the November meeting of the Orange Country Java Users Group (OCJUG) this Thursday (the 10th).

This presentation will be a variation of the presentation I did at JavaOne at the start of October on Amazon’s Elastic Beanstalk tool for creating PaaS environments for Java web applications.

Please refer to the OCJUG website (www.ocjug.org) for exact timing and location.

Is LinkedIn ready to recognize O.C.?

Posted in: Quotable Quotes

Bill Crane, the vice president of engineering at LinkedIn, says local members of the social networking site may haveorange-prize Orange County as a geographic designation for members’ profiles within two weeks.

http://jan.freedomblogging.com/2009/09/16/linkedin-working-on-oc-geographic-designation/22015/

O.C. the Rodney Dangerfield of LinkedIn?

Posted in: Social Networking

… LinkedIn, the business-oriented social networking site, groups Orange County not just with Los Angeles but Riverside, San Bernardino and Ventura counties, under the umbrella of “Greater Los Angeles.”

A group of Orange County business people recently hollered, “Enough!” … 2,500 have joined the We Are Orange County group on LinkedIn to persuade LinkedIn to use Orange County as a member geographic designation.

Read more in this OC Register Article.

Enough is Enough

Posted in: Software Development Best Practices, Software Development Team Leadership

I am personally interested in processes (or removing processes), practices and tools that allow software teams to deliver on time and with high quality on a consistent basis. Now that sounds pretty benign and uninspired. It sounds like a common goal that everyone in the software industry would share. Am I naive to think that it is more than reasonable to expect bug-free software? I know many people think that at a mathematical level, debugging many of today’s complex systems is simply unrealistic. But didn’t humans design the compilers and the IDEs and everything else related to software? Don’t we by definition control the monster? Are we really so smart as to have invented something that is beyond our own abilities and comprehension already? Is this the start of the rise of the machines? I choose to think not.

I do believe that bug-free software is the goal of every software project, even if it isn’t explicitly stated. The problem is the commitment to achieving that goal. Quality is often intangible, at least on the high end (low quality is often very tangible). And intangible things are easy to ignore or sacrifice. Quality often comes at the end of a software project and when deadlines are tight, it is the first to be discounted.

Here is the story of what finally inspired me to start this blog.

I was sitting at San Francisco airport, waiting to fly home. I live in southern California, so it is a short flight and American Airlines only uses little regional jets for the SFO to Orange County route. The flight was not full and the plane is small to start with. So passenger loading was done pretty quick and we were set for an on time take off. But we didn’t take off. We just sat there and sat there. Finally the stewardess announced over the intercom that the delay was because they had introduced a new automated system that week to do some of the paperwork required to be given a green light for take off. And that they were having some trouble getting it to work so they were going back to the manual system so we could get underway.

The most disturbing part of this was the exact words used by the stewardess during the announcement. She said “we are using a new computerized automated system and as with all new software there are some bugs and glitches”. I found that statement to be very profound.

My assumption is that an airline stewardess represents a typical layman user of software – in other words she has no specialized knowledge of how to write software or what it is like to work in a software team. She represents a typical user that only sees software from the end-user perspective. And from her perspective software usually has bugs. Usually has bugs. Can that be true? Over all of the software written and all the smart people that write it, does software still usually have bugs? At least anecdotally in my experience that does appear to be the case.

So I say to that, ENOUGH IS ENOUGH.

Software is now part of a lot of people’s every day lives. It is responsible for many tasks that if completed incorrectly could cost human lives. It is also responsible for many tasks that if completed incorrectly have a financial impact on companies and individuals. There is also a social impact from poor quality software. What was the cost in terms of lost time for the people sitting on that plane with me? What is 20 minutes worth? Time is the only non-renewable resource, so 20 minutes is actually priceless, its value is immeasurable.

Every time you relax your definition of quality you are failing as a software engineer. You are contributing to the continued and currently deserved poor perception that people have of the software industry. And ironically, you are also immediately failing the customer who is probably the one pushing you to do the relaxing. It is a basic, fundamental principle of software development that a relentless pursuit of delivering quality software is actually the shortest and quickest path to delivering a project.