Everything at Henry's company revolved around contracts with vendors. The IT department had relied on the aptly named Contract Manager -- the sole remaining Visual Basic 6 client-server application -- to support that business for the past 12 years.
The office where Peter L. works was abuzz with excitement one morning a few months ago when the familiar, bland corporate art was missing from the wall opposite the elevators.
When Brett was hired on as a senior analyst, he wasn't surprised to learn that the older platforms were built around Visual Basic 6 (VB6), which was no longer supported by Microsoft.
Dueling developers create an unappetizing code stew.
Usually, when a multi-megabyte e-mail lands in Jerry's inbox, it means that someone tried to be fancy by including some silly photos or graphic images in intra-office correspondence.
A major validation error in the code resulted in a 60 percent failure rate for an expense form.
Henry was the TAXCALC king. But his coding skills were positively peasant-like.
Was "Calvin code" genius or tomfoolery?
For years, nobody cared that the legacy image-syncing application consumed as much bandwidth and processing time as it did.
Power user Alice strikes; can the code save our programming hero?
For MegaCorp's end-of-quarter presentation, the VP of marketing arranged a demo for a feature that he had contracted an outside consultant to add to the new version of the company's customer-facing online application.
Someone named Robbie had created a posting asking for assistance in resolving a problem with a simple Visual Basic .NET console application. It was used to retrieve and process product registrations and credit card transactions via the Internet for a piece of niche shareware.
When the big merger was announced, the IT staff of both corporations was a little bit nervous, and with good reason: The day after the announcement, many redundant positions were eliminated.
Everybody in the IT department was quite happy -- even a little surprised -- with how well the outsourced project to replace the legacy billing system was progressing.
Bob had sent out a single VB.NET function with an accompanying class definition. Its sole purpose in life was to see if at least one of the terms, passed as an array of strings, existed in the second parameter, a document body. Jed was positive that somewhere, a Reverse Polish Notation calculator was crying.