There once was an invoicing system that, when it worked, it worked very well, indeed. But when it was broken, it was horrid.
Not just once, but repeated in various lucrative apps -- a humongous chunk of code that should've been reduced to a mere line.
To accommodate an influx of year-end work, Guillaume's employer does what many stores do -- hire on temporary help. However, when you're desperate, beggars can't always be choosers.
It’s crunch time for Ben and his team. After a long journey, their project to uplift their biggest client’s application code is nearly at an end. Hopefully they didn’t miss anything ...
Andrew does integration for a living. As a result, weird client data comes with the territory, but one client's data in particular stands out as being truly unique.
With the rate of turnover for developers of Ventozoom's flagship application, some part of the system must be cursed. After Robert joined the team, and seeing how his predecessor handled dictionaries, he can understand.
Simple problems are often solved by simple solutions. Other times, simple problems are solved with an end user running a Web site from Visual Studio on their machine.
After Wayne's employer decided to bring some outsourced code back in house, he discovered that developers in Kerbleckistan were doing some serious innovating in the science of passing parameters.
A critical auditing app was as down as the floor of the Grand Canyon. And each day it was down was a six-figure fine.
What's proper etiquette for handling code snafus when working for -- literally -- a mom-and-pop company?
It's a situation a coder should never have to face: perpetuating bad coding practices from years ago, or just fixing the darn thing!
Would going above and beyond when fixing terrible code have serious consequences?
Why user requests shouldn't always be granted.
That dinosaur of an office appliance -- the fax machine -- plays an unexpected role in Jason's Web site registration puzzle.
When fewer SQL Server columns does not mean better performance.