Kaiser Software falling down.

LA Times reports "Kaiser has aches, pains going digital: Patients' welfare is at stake in the electronic effort, experts say."

Like any big software project, it's never easy to replace an existing system, be it manual/paper system or software [mainframe] system. Either way, the problem is always with the software people: the architects and business analysts since their understand of the requirements are never complete and always behind the curve plus the programmers learn new things in the process of coding and want to do things better [and should be done so that it will be easier to maintain in the future]. Even something as small as web programming can take an inordinate more time than estimated, as we're finding out with my current work.

Copyright, 2007, DannyHSDad, All Rights Reserved.

BlueJ: programming environment

"BlueJ: Teaching Java" seems like a great way to start programming but it seems to help only the peripheral aspect of programming (not visual programming as I had anticipated).

Copyright 2007, DannyHSDad, All Rights Reserved

Software is Hard!

"Software is Hard" is a good read on how programming is a tough problem that hasn't been solved in the past several decades of computer science.

In one way, it's easy to say, "let's do it ourselves" because we programmers think we can do it better and quicker. This desire for DIY (do-it-yourself) is exasperated by how existing software is never customizable enough. Those which are (and this number is increasing as open source take off), the start up cost of learning and then adopting existing software is non-trivial.

The third party way can be easier in terms of in house effort but the cost is high and in the long term still not pay off. One good example area are the business management software like ERP (enterprise resource management) and CRM (customer relationship management) where consultants can make big money adopting the in house system to third party systems (like SAP). My experience, however, is that such tools are too inflexible to deal with custom needs of a given company and end up largely unused (or the company has to contort their existing process to fit the software and make everyone suffer).

The hard problem of software is capturing the ever changing requirements of users and implement it correctly. Unfortunately, those very requirements change due to the feedback loop process of seeing and using the implementation [and the user not explaining themselves clearly and/or not understanding the requirements themselves].

Working with teams is another issue with no easy answers. Mythical Man-Month by Brooks captures this hardness of working with others. A great team can exists and I have been part of such teams but there is never a perfect team so problems will come up at least once in a while.

Copyright 2007, DannyHSDad, All Rights Reserved.