Way back at the beginning of my professional programming career I worked for a small software house that wrote graphics software. Although it had a desktop publisher and line-art based graphics package in its suite it didnâ€™t have a bitmap editor and so they decided to outsource that to another local company.
A Different User Base
The company they chose to outsource to had a very high-end bitmap editing product and so the deal â€“ to produce a cut-down version â€“ suited both parties. In principle they would take their high-end product, strip out the features aimed at the more sophisticated market (professional photographers) and throw in a few others that the lower end of the market would find beneficial instead. For example their current product only supported 24-bit video cards, which were pretty unusual in the early to mid â€˜90s due to their high price, and so supporting 8-bit palleted images was new to them. Due to the large images their high-end product could handle using its own virtual memory system they also demanded a large, fast hard disk too.
Even though I was only a year or two into my career at that point I was asked to look after the project and so I would get the first drop of each version as they delivered it so that I could evaluate their progress and also keep an eye on quality. The very first drop I got contained various issues that in retrospect did not bode well for the project, which ultimately fell through, although that was not until much later. (Naturally I didnâ€™t have the experience I have now that would probably cause me to pull the alarm chord much sooner.)
Hard Disk Disco
One of the features that they partially supported but we wanted to make a little more prominent was the ability to see what the RGB value of the pixel under the cursor was â€“ often referred to now as a colour dropper or eye dropper. When I first used the feature on my 486DX PC I noticed that it was a somewhat laggy; this surprised me as I had implemented algorithms like Floyd-Steinberg dithering so knew a fair bit about image manipulation and what algorithms were expensive and this definitely wasnâ€™t one! As an aside I had also noticed that the hard disk light on my PC was pretty busy too which made no sense but was probably worth mentioning to them as an aside.
After feeding back to them about this and various other things Iâ€™d noticed they made some suggestions that their virtual memory system was probably overly aggressive as the product was designed for more beefier hardware. That kind of made sense and I waited for the next drop.
On the next drop they had apparently made various changes to their virtual memory system which helped it cope much better with smaller images so they didnâ€™t page unnecessarily but I still found the feature laggy, and as I played with it some more I noticed that the hard disk light was definitely flashing lots when I moved the mouse although it didnâ€™t stop flashing entirely when I stopped moving it. For our QA department who only had somewhat smaller 386SX machines it was almost even more noticeable.
DBWIN â€“ Airing Dirty Laundry
At our company all the developers ran the debug version of Windows 3.1. enhanced mode with a second mono monitor to display messages from the Windows APIs to point out bugs in our software, but it was also very interesting to see what errors other software generated too . You probably wonâ€™t be surprised to discover that the bitmap editor generated a lot of warnings. For example Windows complained about the amount of extra (custom) data it was storing against a window handle (hundreds of bytes) which I later discovered was caused by them constantly copying image attribute data back-and-forth as individual values instead of allocating a single struct with the data and copying that single pointer around.
Unearthing The Truth
Anyway, back to the performance problem. Part of the deal enabled our company to gain access to the bitmap editor source code which they gave to us earlier than originally planned so that I could help them by debugging some of their gnarlier crashes . Naturally the first issue I looked into was the colour dropper and I quickly discovered the root cause of the dreadful performance â€“ they were reading the applicationâ€™s .ini file every time  the mouse moved! They also had a timer which simulated a WM_MOUSEMOVE message for other reasons which was why it still flashed the hard disk light even when the mouse wasnâ€™t actually moving.
When I spoke to them about it they explained that once upon a time they ran into a Targa video card where the driver returned the RGB values as BGR when calling GetPixel(). Hence what they were doing was checking the .ini file to see if there was an application setting there to tell them to swap the GetPixel() result. Naturally I asked them why they didnâ€™t just read this setting once at application start-up and cache the value given that the user canâ€™t swap the video card whilst the machine (let alone the application) was running. Their response was simply a shrug, which wasnâ€™t surprising by that time as it was becoming ever more apparent that the quality of the code was making it hard to implement the features we wanted and our QA team was turning up other issues which the mostly one-man team was never going to cope with in a reasonable time frame.
I donâ€™t think itâ€™s hard to see how this feature ended up this way. It wasnâ€™t a prominent part of their high-end product and given the kit their users ran on and the kind of images they were dealing with it probably never even registered with all the other swapping going on. While Iâ€™d like to think it was just an oversight and one should never optimise until they have measured and prioritised there were too many other signs in the codebase that suggested they were relying heavily on the hardware to compensate for poor design choices. The other is that with pretty much only one full-time developer  the pressure was surely on to focus on new features first and quality was further down the list.
The project was eventually canned and with the company I was working for struggling too due to the huge growth of Microsoft Publisher and CorelDraw I only just missed the chop myself. Sadly neither company is around today despite quality playing a major part in the company I worked for and it being significantly better than many of the competing products.
 One of the first pieces of open source software I ever published (on CiX) was a Mono Display Adapter Library.
 One involved taking Windows â€œout at the kneesâ€ â€“ not even CodeView or BoundsChecker would trap it â€“ the machine would just restart. Using SoftICE I eventually found the cause â€“ calling EndDialog() instead of DestroyWindow() to close a modeless dialog.
 Although Windows cached the contents of the .ini file it still needed to stat() the file on every read access to see if it had changed and disk caching wasnâ€™t exactly stellar back then .
 See this tweet of mine about how I used to grep my hard disk under Windows 3.1 :o).
 I ended up moonlighting for them in my spare time by writing them a scanner driver for one of their clients while they concentrated on getting the cut-down bitmap editor done for my company.