I bought the book Dreaming in Code by Scott Rosenberg not long after it was published, and it's been sitting on my shelf, unread, ever since. I've read a lot of books on computer history - in fact, most all of them covering the period from the 1970s to the 1990s. After I arrived here in 1997 I've been close to many of the historic events that comprise a whole new series of books. This one, though, I should read for two reasons:
One, it's about the pitfalls and mistakes that can bring down a large software project. Some of the reviews said it can hit too close to home, but also make you feel better, as some of the top minds in the industry are not immune to the same mistakes.
Two, I have actually dreamed in code, which is the story I want to tell.
It was late in the early phase of a big project and I was responsible for building a multi-source enterprise data model for the entire hospital. The tools at my disposal were a SQL database, bulk data copies, stored procedures, and data transforms using a view/copy mechanism I developed for the physician directory years earlier - which was to be adapted one of three major portions of the enterprise architecture, the other two being physical locations and services provided.
The main problem was data flow.
I struggled for weeks with various data models, trying to fit them together, integrating the different source systems, keep the updates moving reliably from staging to production, catching errors before they do, and making the whole thing easy for one person to oversee.
Everything I tried either caused conflicting changes to overwrite each other, or entire data copies to fail. Each of the three main subsystems: physician, location, service, was an entire application data model in and of itself, and they were interlinked in increasingly complex ways. The end result, if it worked, would be amazing. Whether you're looking for a service, a doctor, or the nearest location for either, all the connections would be there.
If it worked.
(to be continued)
Sunday, May 10, 2009
Wednesday, April 29, 2009
Old School Coding
ComputerWorld has an article on things programmers did in the old days and probably won't miss.
Spaghetti code, GOTO, and the FORTRAN idioms, I remember them well. Punch cards were a bit before my time. The one thing I don't miss is programming entirely in emacs and vi. Modern IDEs with code completion and visual modeling (and now semantic resource management) are a huge time saver. First code completion blew my mind, it was like the documentation automatically opened to exactly the right page as I typed. My taped-together copy of K&R C could go on the shelf. Now with visual modeling, I can rearrange my program structure to my heart's content before writing a single line of code. Don't even get me started on refactoring. It was impossible. Of course, with UNIX I didn't have to worry about the 8+3 file name limit, although I did write some TSR (terminate-stay-resident) programs in x86 assembly. I remember writing the UNIX "more" command for DOS with my own twist on error handling. Instead of "File not found" it would print, "So the bartender says, that's no file that's my wife!" What can I say, I was a rambunctious young scamp. I thought my home-built overclocked 286 with co-processor (I couldn't settle for just integer math, could I?) was total cyberpunk. It had a giant hard drive that sounded like a jet engine taking off when I booted. Even so, it was mostly a dumb terminal for the University supercomputers. The Convex C-220 had an awesome debugger. I managed to avoid Windows almost entirely until the late 90s when I moved to Silicon Valley.
Slow computers? I remember a scientist in the early 90s complaining about fast computers. In the old days, he'd say, he could load his data, run the program, and go off for a nice lunch. When he got back he'd have his results. Now, he'd complain, a data reduction that took 2 hours now completes in 20 minutes, hardly time to do anything! Also something about VMS being God's own operating system, while younglings like myself thought UNIX was God's own operating system.
Ah, memories...
Spaghetti code, GOTO, and the FORTRAN idioms, I remember them well. Punch cards were a bit before my time. The one thing I don't miss is programming entirely in emacs and vi. Modern IDEs with code completion and visual modeling (and now semantic resource management) are a huge time saver. First code completion blew my mind, it was like the documentation automatically opened to exactly the right page as I typed. My taped-together copy of K&R C could go on the shelf. Now with visual modeling, I can rearrange my program structure to my heart's content before writing a single line of code. Don't even get me started on refactoring. It was impossible. Of course, with UNIX I didn't have to worry about the 8+3 file name limit, although I did write some TSR (terminate-stay-resident) programs in x86 assembly. I remember writing the UNIX "more" command for DOS with my own twist on error handling. Instead of "File not found" it would print, "So the bartender says, that's no file that's my wife!" What can I say, I was a rambunctious young scamp. I thought my home-built overclocked 286 with co-processor (I couldn't settle for just integer math, could I?) was total cyberpunk. It had a giant hard drive that sounded like a jet engine taking off when I booted. Even so, it was mostly a dumb terminal for the University supercomputers. The Convex C-220 had an awesome debugger. I managed to avoid Windows almost entirely until the late 90s when I moved to Silicon Valley.
Slow computers? I remember a scientist in the early 90s complaining about fast computers. In the old days, he'd say, he could load his data, run the program, and go off for a nice lunch. When he got back he'd have his results. Now, he'd complain, a data reduction that took 2 hours now completes in 20 minutes, hardly time to do anything! Also something about VMS being God's own operating system, while younglings like myself thought UNIX was God's own operating system.
Ah, memories...
Tuesday, April 28, 2009
Enterprise 2.0
The new buzzword - Enterprise 2.0, refers to private, internal social networks, for example when employees don't use Twitter, they use a twitter-like application kept safely behind the firewalls with all the access and security control applied for any internal communication. Google's find-an-expert is an early example of this. Twitter-like applications for internal communication may or may not be useful, but some kind of internal IM definitely is.
ReadWriteWeb has more.
ReadWriteWeb has more.
More Healthcare IT Articles
Some recent articles on Healthcare IT and the EMR...
Improving EMR Usability: Part 1, Part 2, Part 3.
What Usability Is and How to Recognize It
The Dubious Promise of Digital Medicine (Business Week)
The Data Model That Nearly Killed Me
Improving EMR Usability: Part 1, Part 2, Part 3.
What Usability Is and How to Recognize It
The Dubious Promise of Digital Medicine (Business Week)
The Data Model That Nearly Killed Me
Thursday, April 16, 2009
Mylyn
Trying out Mylyn and Tasktop and I love it. Everyone on my project is required to use Mylyn now, and Tasktop, we're doing the free trial to integrate bugzilla, OPAS (our corp help desk system), calendars (for releases and help desk tickets), and cvs. This incorporates a lot of the ideas I've been toying with around the semantic desktop project. Now when I go back to that bug I worked on a month ago, I see exactly the files involved (say 5 files in 3 different projects among hundreds), supporting documentation, even web resources. Regardless of the source system, it's all URIs. Exactly right.
Wednesday, March 25, 2009
The Memory Box
I do lots of stuff online, and lots offline. I have documents on my desktop and web pages I open. Where is that google app engine account I got when it was beta and haven't touched since? It's in my browser history, still. Dated documents, bookmarks, emails, user history. All the related material is there, but how to find it? How to organize it? How to crawl the different things I've done on my laptop any one of which I may wish to recall at some later date? That programming library I installed last month? Where is the API, tutorial, and article I found on some google search at the time? It's all in my little electronic box of memories. I need a web of remembering.
semanticdesktop.org
semanticdesktop.org
Tuesday, March 10, 2009
Identity Blog
Somewhere along my Googlings I came across the subject of digital identity, which I found days later in a long-forgotten browser tab. Save it! It looks like good reading for later.
Kim Cameron's Identity Blog
The page I had bookmarked, THE LAWS OF IDENTITY, I landed there looking at what people are saying about the term Enterprise 2.0, which far as I can tell is attempting to utilize Web 2.0 social features - blogs, chat, Ergos-Bacon numbers, etc - into a private Intranet setting. The real question is: how do employees use it day-to-day to help them in their jobs? We need a usability study similar to what Jeff Hawkins did when designing the Palm Pilot. The case for usability is easy to make, and lo-fi prototyping can be invaluable in getting a product started in the right direction.
Kim Cameron's Identity Blog
The page I had bookmarked, THE LAWS OF IDENTITY, I landed there looking at what people are saying about the term Enterprise 2.0, which far as I can tell is attempting to utilize Web 2.0 social features - blogs, chat, Ergos-Bacon numbers, etc - into a private Intranet setting. The real question is: how do employees use it day-to-day to help them in their jobs? We need a usability study similar to what Jeff Hawkins did when designing the Palm Pilot. The case for usability is easy to make, and lo-fi prototyping can be invaluable in getting a product started in the right direction.
Subscribe to:
Posts (Atom)