Today I’ll cover the story of project number two, "just a little code" to integrate two systems. But first, let’s talk about my motivations.
About the Killer App Series
"The Killer App" is not a work of fiction, or a work of historical fiction. It is not a made-for-TV movie, "inspired by" true events but with the drama cranked up a notch or two; it is history as I recall it.
While it has been a pleasure to get this off my chest, I have no axe to grind. The players have moved on. Enough time and space now separates us that even the “bad guys”, as much as there were bad guys, would probably not recognize themselves in the writing.
Nor is this a case study, all wrapped up in a bow with a key learning takeaway.
The Killer app is ... a story.
My story, about a time in my life before I was a writer or consultant, back when Matt was an employee, and, sometimes, felt more than a little trapped by his situation. The story points out that there is more to life than process -- that often, it is the sticky blobs of flesh called humans that can make a difference. I didn’t always make the right choices. Back then I was more than a bit scared of conflict. But if a person or two can learn something from the story, and do it with a smile on their face ... I hope you’d agree with me to call that success.
Now it’s time for round two.
The Next Killer App
At the end of the killer app, our hero had transferred off the project, to go work on project number two. The transfer was no brilliant duck-and-groove out of the matrix.
The reality was that I failed a code review, so they transferred me to fix the code.
At least, I tried to fail the code review.
You see, the code came to me late in December, between Christmas and New Year's, with a bow on the end that said it "had to go into production by the end of the year."
The code itself pushed data from one system into another and provided