August, 2008

Information Overload

Information overload is a topic which has seen enough blog and article time to provide a generous amount of information overload on its own!  As an example, I searched Google for the term “information overload” and it returned the first 10 of approximately 2,160,000 “hits” (…but who’s counting?   :-)   No wonder we need data warehouses!  I figure that is probably a bit more information than this modest man can (or wants) to handle - yet of course as I scanned that first page of “hits” I had to check out a couple of them.

One of the hits that I followed in particular caught my attention and prompted me to both chuckle to myself and to think about my own habits.  A blog response from Noam Chomsky  really started me thinking — in response to a question about tips for handling information overflow he replied:  “I wish I could answer sensibly. I just can’t. You should see the room in which I’m working. Piles of books, clippings, manuscripts, notes,… All sorts of lost treasures buried in them.“  Sound familiar?

His response really brought home to me that my habits of saving information, whether it be printed material, sound clips, email or internet links encourages my sometimes overwhelming “buried” feeling - information overload is alive and well in my life, as well as “…all sorts of lost treasures…”!

Now, to get to the real point of this post — as a developer I believe that it is in my clients best interest to support them in providing the information they need to forward their businesses -  whatever that is.  It is very easy for me to provide them with too much information (…some say there can never be enough) in the form of reports, graphs and miscellaneous on-line “views” of their data.  However, I believe that it is a “key” responsibility of mine to constantly be aware of the tendency toward “information overload”.

User Reluctance to Application Changes

Some things just never seem to change, and user reluctance to application changes is one of those situations which it seems, is always present - regardless of the form of change.  Sometimes I’ve found that even changes which had been requested by users, and that they kept looking forward to, once made, the changes are received with grumbling and every excuse possible being used to avoid incorporating the changes into their routine.

The question is, what do you do about it?  What does it take to bring the user around so that rather than condemning the changes, they embrace them with enthusiasm?  The answer is actually quite simple, although time consuming — it’s one-on-one training.  My experience with providing “training” applications which the user can access on their own to learn new application features has been highly ineffective since the users do not spend the time needed.  A “classroom” kind of setting also has been ineffective for my clients since often it is key people in the company that need to use the application, and they have a business to run!  (…read this as they’re TOO busy for training!)

However, the 1-on-1 approach has proven effective consistently since it provides the capability to work with the reluctant user with “real” information, in their setting (…always do 1-on-1 at their desktop!),  and your presence allows for instant answers to questions and concerns as they come up in the session.

This kind of training can also provide valuable feedback for further development of the application — for one thing, it allows for experiencing “real issues” for users “IF” such issues exist.  Certainly as developers we hope that there will be no “real issues” with our pride and joy of application, but I’m sure we all have experienced them.  Seeing exactly how the application performs for a user is important - many a “little issue” that I’ve seen when working with a user 1-on-1 has led to better the next iteration of the application.

Independent Development Business

My work day started today with the usual quick scan through the multitude of emails that I receive daily.  I have always found this activity a gentle way to start my day (which generally begins somewhere between 5:30 and 6:30 AM).  I’ve also found that at times my attention is directed to particularly poignant articles relating to some facet of my business as an independent software developer.  This mornings find is just such an article.

My find?  “The myth of being successfully solo in business” is a brief article that caught my eye and started me thinking about just how dependent an “independent” software developer is.  Let me explain a bit without (hopefully) you not reading the linked article.

The article explores what is described as “…the myth of the successful solopreneur…”, and explores also how “…we can’t do it ourselves”.  Now, THAT is something I’ve realized over and over again through my years as an independent software developer!  However, my memory gets pretty short with certain learning I’ve noticed, and especially when faced with this myth!

The impossibility of doing all the things yourself that are provided for you when you are an employee seems to escape many of us self-employed, and often we think we’re some kind of super human who CAN do it!  I’ve personally had one of those reminders recently as the result of my wife’s broken ankle back in mid May.  Since the time of her injury, ALL of the household responsibilities AND the income producing responsibilities have been on my shoulders. 

Fortunately, I don’t have an office out of the home that I have to go to - but I do have the occasional visit required to my local customers.  All of these activities have at times been very much overwhelming — and certainly indicative that I “can’t do it” solo.  Through this period I have met with exceptional understanding from my clients and considerable help with meals prepared by friends and shared with us.

While what I refer to above might seem more personal than business related, I call it to your attention in light of the referenced article, and as another indication that being an independent software developer still requires others.  Professionally I’m a part of the Northeast Dataflex Consortium, a dedicated group of professional developers who support each other in many ways.  Those of us who are independent software developers are also dependent upon our vendors, customers AND indeed all of those around us in some way.

Girls, Technology and Career Paths

Once again I have found myself drawn to an article dealing with “girls”, technology and careers.  The article in question, “Girl Power! Summer camp grooms tomorrow’s techies” introduces us to a summer high tech camp for girls 11-14 years old.  It seems that these girls are experiencing opportunities to see technology in action in what is referred to as a “girl-friendly” atmosphere.  The hope of the program being that this program will “…make technology relevant — even cool — for this at-risk age and gender group…by exposing them to women in technology-related careers”. 

As I look back at my experiences in this industry I see but a handful of women who have chosen to make software development their career, and even fewer seem to be involved with other IT functions.  To my way of thinking, we are missing out!  I don’t think we need hard headed “know it all’s” of any gender, but I strongly believe that we do need the perspectives that only a women brings to a project, and the lack of women involved in technology restricts us.

While I have heard many a snide remark made regarding some of the female perspectives that those daring enough to voice did in fact voice, I have often wondered about how many of the impractical, almost “toys” that have come and gone in the corporate world would never have gotten off the ground had there been respected female perspectives listened to.

I hope the program referenced meets with successes way beyond their stated goals.  The statistics presented in the article about women and their technology careers tells us something is missing - and indeed it is - the female talent.