Many stories aim to share a saga of how code builds are successfully integrated with each other. This is not one of those stories.
What Martin wanted was to fulfill his internship requirement for his degree and possibly earn a little spending money for his efforts. He got both of these and the experience of meeting "The Monster."
You'd think that rounding should be simple, but why is it causing Ryan so much trouble? You can thank his managers for that.
Adam's employer was able to reclaim the company URL from a cyber squatter. Now it should be easy to make sure its site resolves to the new name, right?
In a DevDisasters reversal, Dave's meticulous attention to detail that points out the numerous issues in code that made it to a production system was enough to earn him a role at the company.
Long hours finally took their toll on Adam's health, so Gerry picked up the slack in his own peculiar way -- introducing some slick do-it-all function.
Code audits seemed unnecessary to everyone except the auditor. Good thing the auditor finally had one sympathetic ear -- "Andrew" -- to hear him out.
If you think Bert is all talk when it comes to his decade of C# experience, you're wrong. He delivers…15 times.
If there's one life lesson to be learned here, it's that just because a manager knows how to write code, it doesn't mean that they should be allowed to write code.
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.