Andrew found this code on the product pages of a fairly popular automotive e-commerce website. It's called whenever an 'attribute' of a product (size, color, etc.) is selected or changed by the user.
The main focus of this code is to update a concatenation of the values of all currently selected attributes which are stored in a hidden form input field. Once it has done that, it hands off to another function to make an AJAX request with this concatenated value as a parameter.
Trevor found an unusual bug. Every customer had a GUID, but for some reason, their JSON API failed if there were ever more that 75 results.
He checked the web layer, only to find that it didn’t actually build the JSON- it just returned a string. The string itself came from their Oracle database. That’s where this procedure came from:
Have you ever done something that seemed like a good idea at the time? Then looked back upon it much later and had second and third thoughts about the wisdom of what you had done?
A long time ago, Jack worked for a company that had built a goods-declarations system for freight-forwarders so that they could get the blessing of the government to import/export their goods.
When one of Felix G’s newest design customers decided that they were officially unhappy with their current web-agency, another company's loss was his gain.
His first assignment was a simple one - remove the code that displayed the website’s creator credits (something like 'developed by xyz') from an external website.
Most programmers are familiar with a notion of technical debt. Sometimes all it takes to make or break a project is a single bad decision, questionable design solution, or even a plain old bug that doesn't get fixed early on. The hacks and workarounds keep piling up, slowly turning the project into an unmaintainable mess.
In this regard, David was already off to a head start. He has recently been assigned to maintain a meeting tracking system with – to put it lightly - a bit of history. A year before, the marketing department of his company received the first version from a subcontractor and promptly implemented it – only to find out that the data gathered were a little off. According to the reports, every single meeting lasted exactly 24 hours – from midnight to midnight.
Business was booming during the formative years of SuperbServices, Inc. It was a blessing and a curse; like any startup, there was more work to do than people to do it. Telling the sales team to be less successful wasn’t an option, so the tech team had to adapt.
The CEO of SuperbServices tasked Roland with a major initiative that would save the company, or at least their sanity. “We need to automate all of this processing work, so we can focus on service delivery!”, the CEO said. “Our value proposition is our services, and everything else is busy work. We need to automate that, and that’s where you come in. I need you to engage the Robot Guys to work on automating everything: operations approvals, purchasing, money transfers, client emails, everything!”
Arty works on a team maintaining a legacy application that can best be described as a birds nest of code. It is a massive collection of global variables and a few tens of thousands of routines that would independently modify the data. Decapsulation was the overriding design pattern of choice. Of course, changing the value of some variable invariably has all sorts of unpredictable side affects. Naturally, this lead management to be fearful of making any changes, no matter how urgent, for fear of what would inevitably happen.
Fortunately, management recognized the need to replace it. The directive was given. A new application would be built. The replacement would be designed in such a way as to keep data and the routines that needed to access it somehow tied together. The state of a variable would only be changed as an end-result of some business action.
Growth is challenging for any company, and the smaller a team is the more carefully they have to vet candidates to ensure a good fit. Carlos understood this, but had never seen it practiced as extensively as when he applied for a systems management position at Initech. The scrutiny applied to their candidates suggested a company obsessed with finding the perfect fit, and Carlos couldn't imagine the quality of the incredible team they must have already. Between the recruitment agency and Initech itself, he'd had three interviews and completed four online tests, including every developer's favorite: a personality quiz. Shaking hands with Carlos after the most recent interview, Initech's senior developer and his would-be boss promised he'd get a call that day or the next with the company's decision. Days went by before his phone rang, Initech's chipper HR person on the line.
"Hi Carlos! I was hoping you had a few minutes to answer a few questions."