Rewriting bedtime stories, one fairy tale at a time! During my childhood, I enjoyed stories that triggered my creativity and imagination. Naturally, I loved all kinds of cartoons, but there was something that bothered me deeply in them. It was the way most cartoons depicted “good” and “bad” in a crude pile-up of cliches.

The good, the bad and the obvious

Watching old cartoons as an adult is going to shed light upon aspects you have probably never noticed before. To name a few, the adult innuendos, easter eggs, and stereotypes. One thing you never had trouble differentiating was the main character (the good) and the enemy (the bad). When the latter wasn’t also a main character, he or she would always be depicted as an ugly, inexplicably evil person who tried to bring chaos and whose agenda made little to no sense (the obvious selection of traits, used in every old cartoon). Until this day, I’m team Tom, Coyote and Sylvester. They were lucky enough to be main characters also, so at least they escaped the mean face stereotypes. They have been through hell and back numerous times, faced every unfair situation there can be while their “good” counterparts smirked full of pride and arrogance. If anything, the plot twist of our entire childhood was that sometimes, the roles of “good” and “bad” were in fact the exact opposite of the obvious that was shown.

The protagonist of the story

Meet the Big Bad Wolf, an average Joe who got into a big misunderstanding with Little Red Riding Hood and went viral. After that, he settled down and got a job as a Quality Assurance Engineer. He worked hard day after day to become better and prove his worth, as his fellow developer co-workers shunned him for the “little he did”.

The co-workers

Three little developers. Each one, was assigned to build a part of a big project that their company was preparing to introduce to the public. It was something majestic, a groundbreaking, innovative website. A social networking website! Hallelujah! Each one of the three devs saw this project as an opportunity to get a better position, get a shine upon them and perhaps a sweet raise too.

The big bad project

So everyone at the office was busy working on the big project, while the deadline was coming closer and closer. The Wolf patiently waited for the three little devs to send him their parts, as they were working on the last 3 parts to conclude the project. Ten days before the project’s deadline, the first little dev sent his part to the tester Wolf. The dev was confident that there were no issues, but he was only a junior dev still and did a rookie mistake. The Wolf huffed and puffed and blew the dev’s progress away. The registration form he had created did absolutely nothing when the Wolf clicked the button that would submit it. So the little dev went back to work to fix this. Six days before the project’s deadline, the first little dev had finally fixed the issue and the Wolf was very pleased at the result, which he approved. The second little dev, then, sent his part to the Wolf. He had implemented the slider of images that users would upload and view their pictures in their profiles. The Wolf huffed and puffed and blew the dev’s progress away. He uploaded a series of images. Big, small, wide, panoramic, animated. He found out that the images would not look good if they were smaller in size and the quality standards were not met. So the second little dev went back to work to fix this. Three days before the project’s deadline, the second little dev had fixed the issue, but when the Wolf retested it, other issues had emerged. So another day was gone in the process before all the issues were fixed. One day before the project’s deadline, the third little dev sent his part to the Wolf. He had implemented the rest of the user profile, including the second little dev’s image slider, a status update bar and an interface that would house the user’s updates and personalizations. The dev was a senior so he was very confident about his work. Considering that there was now less than a day left, the third little dev, along with everyone else in the company, pushed the Wolf to approve it without stressing too much about it since the third little dev insisted he had thoroughly tested it himself and everything worked as expected. The Wolf only had an hour to test it and find any issues, but that would bypass the project’s deadline and set its release at risk. Stakeholders would not be happy with that. Before the Wolf huffed and puffed, co-workers dragged him to have a beer with them and celebrate the new project. He never approved the third little dev’s part. Everyone’s work was merged into one big project and it was released on time. Everyone was cheerful, until they realized that the registration form, the very first step that people would need to fill in to join the website, was once again not working. There was mayhem at the office and everyone first pointed the finger to the first little dev who was responsible for that part, who in his turn pointed the finger towards the Wolf who had tested this feature before and had approved it. The Wolf knew the situation was bad, but he was confident for his part, so he quietly sat in his chair and started investigating what had gone wrong. The Wolf huffed and puffed and blew every doubt against him away. It was after the third little dev had submitted his part, that the registration form did not work properly again. Had he had the time to test the project before its release, disaster would have been averted. The three little devs and the Wolf all learned their lesson. One should do no more and no less than his job properly. Eventually, the three little devs and the Wolf got past their differences and had their make-up beers after they had all been fired.

Leave a Reply

We are a software house!

A place that we gather all together to build, test and ship software for high demanding clients.

Our headquarters

Ipirou 16
Drama, 66100

T: +30 2521 105247
E: [email protected]