Recent Feature Articles

Feb 2009

Sponsor Thanks, ASSorted Out-of-placeness, & More

by in Feature Articles on

And now, a quick break from our sponsors. If there are any companies that you think would make a good sponsor, let me know. Otherwise, if you haven't done so already, please show your support by taking a look at what our sponsors have to offer.

 

Software Verification   Software Verification - software engineering tools for memory leak detection, code coverage, performance profiling, thread lock contention analysis and thread deadlock detection, flow tracing and application replay on the Windows Vista, 2003, XP, 2000 and NT platforms.
Mosso   Mosso - massively scalable hosting for .NET (2,3,3.5) PHP, Ruby, etc., with unlimited sites & mailboxes, simple online provisioning, and an enterprise clustered platform that's supported by real people.
SlickEdit   SlickEdit - makers of that very-impressive code editor and some pretty neat Eclipse and VisualStudio.NET tools and add-ins, some of which (Gadgets) are free. Check out this short video highlighting just one of SlickEdit's Visual Studio integration features.
SoftLayer   SoftLayer - serious hosting provider with datacenters in three cities (Dallas, Seattle, DC) that has plans designed to scale from a single, dedicated server to your own virtual data center (complete with racks and all)
WTF   The Non-WTF Job Board - Powered by HiddenNetwork, it features some great job opportunities like:

The Docile Monster

by in Feature Articles on

credit: gwen @ flickr Although The University billed itself as “a leader on the forefront of Information Technology,” it was neither a leader nor anywhere near the forefront. At least, not any more. Its “next generation” hardware – graciously donated by a company known as Big Green – had slowly devolved to “last generation.” And then to “several generations old.” And then, finally, to ancestral. By that point, many students’ laptops rivaled that of the once great, Big Green hardware.

Fortunately, The Professor had excellent connections at Big Green. And Big Green, not exactly a non-profit organization saw the potential in educating students on their platforms. So after much negotiation, Big Green finally agreed to provide The University – free of charge – with some rather expensive and quite interesting hardware. The media dutifully published the relevant press releases and the students began dreaming of virtual environments, sandboxes, compiler farms, databases and everything else that nerds would want.


Beneath Dave

by in Feature Articles on

When John Smith started his job as the IT Manager/Network Admin/Webmaster for a small, sixty-employee subsidiary, he thought that he had found a pretty sweet gig. Everybody from his boss on down seemed reasonable, plus he got a laptop and a nice 19" LCD monitor. And best of all, the vending machine gave out drinks for $0.25.

Overall, things went along pretty smoothly and, once he got to understand how everything was connected at the company, he brought up some very good suggestions on how to improve things further. Including his idea for an VPN to secure transactions between his and the parent company. But instead of a round of applause, John got a nervous "Well, your VPN idea sounds pretty solid, but.....you're going to need to run that past Dave first."

Who's Dave?


The Manual Migration

by in Feature Articles on

The time had come for the national telecom we'll call Communicommco to shed its legacy systems and move into the future. In fact, calling them "legacy systems" is perhaps too charitable – these things were freaking dynasty systems. The dusty green screen terminals and ancient interface were being replaced with a cutting-edge the-future-has-arrived VB6 frontend. There was just one problem: the existing data had to be migrated in somehow.

Having just graduated college, Joe B. had a lot of free time on his hands. He had a job lined up, but that was six months away, and he was still too wet behind the ears to sell his services as a contractor. After seeing a lot of late-night commercials that made data entry sound pretty lucrative, he decided to try to get a position on Communicommco's migration project.


The Son of ITAPPMONROBOT

by in Feature Articles on

It’s always been my goal that the stories shared here on The Daily WTF provide a “certain” kind of inspiration. Perhaps the kind of inspiration leads towards better code instead of the disasters featured here. Or maybe the inspiration to gently nudge that “certain” programmer into a career of, say, accounting. Or even just pure inspiration which reminds us that, while sometimes boring, our jobs aren’t completely meaningless.

That said, it’s been a bit surprising to see that one particular article – ITAPPMONROBOT – has provided the inspiration for other IT professionals to build to their own "robot". Not once (see: Open Sesame), but now twice. Felix explains...


Consultants of the Crystal Citadel

by in Feature Articles on

Photo Credit: 'Thristian' @ FlickrIt was the mid-1990's and business was booming at the company that Terry worked at. It was booming so much that the existing process of entering an order — faxing in an order form torn out of an outdated-as-soon-as-it-was-printed catalog — was delaying things enough that it was costing the company some serious dough in missed sales. Needing a way to re-engineer the process without hiring an army of support staff, management decided on an innovative plan that would enable customers to place orders electronically without needing to contact customer service.

With resources being tight (even the help desk was fielding order inquiries), management decided to farm out the work to an outside IT firm. Now, important work like this wasn't going to be farmed out to the boss's nephew who was a whiz at programming in Word and Excel. Instead they were going with a big name, "we named our building after ourselves" company. Yes it would be expensive, but the money that could be saved by receiving orders this new way would allow the program to more than pay for itself in short order.


Non-Compliant By Design

by in Feature Articles on

The IT Support Department at Stephen S.'s company was divided into two distinct castes: helpdesk admins and system admins. And the differences between these two groups were many.

The helpdesk admins had rotating shifts and were there 24/7 (and each was on call 24/7), while the system admins had a solid 9-5 and a rotating on-call admin. The helpdesk admins staff was always on duty, while the system admins would frequently attend catered vendor meetings, leaving the helpdesk admins crew to fight over the remaining scraps. There was a considerable difference in pay scale. The helpdesk admins were the low men on the totem pole, while the company bent over backwards to keep the system admins happy, stopping just shy of providing palanquin transportation to and from work (instead, they had a 50/50 mileage split).

The Wee Hours


Does Not Compute: Crunchies, Virtual Returns, & More

by in Feature Articles on

It’s easy to take for granted a lot of the words that have entered our high-tech lexicon. Many of the words – from Amazon to the Web – have real-world meanings that, oftentimes, are very far removed from “our” meanings. Here are a few stories from readers that serve as a fun reminder to all this.

Crunchies (from Romjin)
Recently, one of our customers called in with some problems he was having with his computer.


Seasonal Slowness

by in Feature Articles on

Photo Credit: 'peterallen' @ FlickrFlash back to the early 1990s when David S. was working for a large health care provider, maintaining an application that passed data files between two servers across a leased line.

Normally, data transfers went off without a hitch - the applications responsible for shuffling data between the servers were well written and while the hardware on either end wasn't exactly bleeding or even cutting edge, it was mature enough that all of the kinks were worked out.  For David, day to day maintenance was a piece of cake.


Damn the River

by in Feature Articles on

Hitchcock River had gotten so badly polluted that going for a dip in it would get you one of two things: superpowers or some kind of nasty flesh-eating bacterial infection. And as awesome as it'd be to have X-Ray vision, it was just not worth the risk.

Decades ago, Ed B. was working for an underfunded state research team with an insanely-frugal mad scientist at the helm. They were working together to study the sludge that flowed through Hitchcock River, and had a semi-friendly rivalry with a well-funded lab in a neighboring city ("Shelbyville"). Ed didn't mind the cheap boss or shoddy equipment, though, because the equipment they used had such cool names. Honestly, one of the devices they used was called a "gas chromatograph mass selective detector." Awesome.

Measuring Flux Capacitance


The Secret DTS Package

by in Feature Articles on

"I don't know, Gerald, this doesn't look right."

"What do you mean?"


Re-enlisting the Data General

by in Feature Articles on

Photo Credit: 'glass window' @ FlickrFlash back to the early 90's when Remy P. was working as a system administrator for a major oil and gas company. Getting his hands dirty on a mix of Windows, VaxVMS, Alpha, and Solaris servers, Cisco routers, and even an old Xenix box that everybody prays never crashes, things were never dull, and today was certainly no exception.

Scratching his head the whole way down the freight elevator, Remy and two strapping lads from building services were to fetch the old, retired Data General server that once ran the old legacy accounting database before being replaced by a Dec Alpha and Oracle database from the server graveyard in one of the dimly lit storage rooms. Once in place and he would then play Doctor Frankenstein with it so that it may fulfill one request - print out all of the financial records that could be restored from tape backup for none other than the almighty Internal Revenue Service.


The Expert System

by in Feature Articles on

As a highly paid consultant, Bruce didn't make a whole lot of friends with the "locals." Whenever his New York City-based systems-integration firm placed him at a client site, the in-house developers tended to resent him for one of two reasons: They'd either believe that he didn't bring nearly enough innovation to justify his company's three-figure hourly bill rate ("We could have thought of that, too"), or they'd feel that he was far too much of an outsider to provide any valuable contributions to their team ("We already know what's best").

Victor was no exception. Almost immediately, it was obvious that Victor had come to the conclusion that bringing in any outside consultants would just delay things further.