Joe "The Software Engineer" was watching a revolution unfold on TV. President Mubarak finally agreed to resign after 30 years of fun...err...power.
Joe decided it was time for software engineers to put their foot down too and cause a revolution.
"Code Monkeys", "Commodity skills", "Grunt Work" - He had heard enough of those terms and it was time to show the powers that be as to who called the shots.
Within the next 24 hours, a "Software Revolution" group had been organized on Facebook and software engineers from all around the globe joined him in support. "Very exciting", he thought.
Their plan - To stop coding till they were given their due respect. They were the rock stars and wanted to be treated like one. They needed celebrity status, VIP seating in meetings and unbridled access to all "classified" company information. Of course, better monitors, better offices and an ability to work on what they want and when they wanted would be nice too.
Day 1
All software companies grind to a halt. Rows and rows of blinking monitors await their masters to fill them up with data and tables and code. Keyboards await their first click of the day. All software engineers gather outside their offices and in the laws of their sprawling complexes and start chattering excitedly.
Day 2
Customer escalations are up. Customer support managers cannot handle the incoming calls and some executives field customer calls to make them happy. They have never worked so hard before. Phew! When they reach home, the only thing they can do is find the nearest bed and sleep as if there is no tomorrow.
Day 3
Some enterprising executives roll up their sleeves and decide to get dirty with some code. They fix some easy fixes and check-in the code. Their triumph is short lived when the VP of QA declares that all their automated tests are failing. What ? How ? Impossible ! . The software engineers in the meanwhile are still lazing around and gloating at their desperate executives.
Day 4
Executives dread going to real work. They never felt this way before! Meanwhile, software engineers start experiencing withdrawal symptoms. Their conversations now see trickle of words like "null pointer exception", "caching" and "hash table". They quickly check themselves and think about the revolution. "Discipline is key", they remind themselves.
Day 5
The executives join the managers to fix bugs but their sleek Macbook Air's are not loaded with all the tools needed by the engineers. They will have to trade for a heavy Dell. They quickly abort their attempts and justify it by saying something like "benefit" v/s "cost" trade-off.
Day 6
Software engineers now find themselves talking to each other more about bugs and less about the revolution. Their withdrawal symptoms are taking a toll on them. "Only if they could write some code" , some start thinking.
Day 7
One of the companies has an idea. "Software engineers love their code", they think. So, the company starts scrolling customer bugs and lines of code across giant screens in their offices and campuses. They are overwhelmed by the sight of their very own "for loops" and "if conditions" displayed on giant screens. Their code never looked so beautiful! Some of the customer bugs are so easy that they want to rush to their desks and fix it immediately!
Day 8
The executives realize that the trick is working. They setup more giant screens and display even more code. Some engineers can't take it anymore. They rush to their cubes and start fixing the bugs. Coding has never been so exciting!
Day 9
A mass exodus of software engineers from the revolution camp. More and more engineers are back at work.
Day 10
Everyone is back to work and back in their cubicles. Looking at those endless lines of bright code against the dark screen brings tears to their eyes. They wouldn't miss it for any revolution.
(Meanwhile, seen in conference rooms across the world - Managers and executives are popping champagne bottles and toasting to yet another management success ... a crushed revolution. A dart-ridden picture of Joe hangs on the walls.)