Compromise

A few days ago, an e-mail went out advertising a programming competition for a financial data analysis firm known as Morningstar. Initially, I dismissed the e-mail figuring there would be no chance of me getting first or second place especially considering the only programming languages I know with fluency are Python and calculator B.A.S.I.C.. The next day (or two days later depending on how you look at it) the e-mail made rounds again shortly after the midnight resume deadline. I stared at it for a bit before finally deciding to take the bait. After adding Google Summer of Code to my college application resume and updating the contact information, I sent it off before retiring for the night.

The next morning, my inbox was empty. I put my phone into airport mode so I could use the Wi-Fi when I needed it but not have to worry about my phone going off during classes. When I returned to my room after my last class, I had a phone call from one of the program coordinators saying they had a couple of slots left and they were glad to take me. My excitement was quickly overshadowed by the prospect of getting to the competition and being the only person in the room that unable to approach the task at hand. I sat for a bit debating on whether or not I would actually go especially since the competition was from 5pm to 8pm, kickboxing would be starting at 8pm and I had homework to do. Fifteen minutes before I had to be at the competition, I decided I would go to the competition and forgo kickboxing today.

The coordinators gave a brief overview of their company, its mission and some employment opportunities before going over the contest rules. There weren't too many competitors there, maybe fifteen at most. My mind raced coming up with back stories for each of the people in the room. The girl that asked if she could use M.A.T.L.A.B. -- obviously a data analyst that specialized in matrices and linear algebra. Oh and the guy fooling around on a terminal of the campus system as opposed to using his laptop was, of course, a cryptography expert that wrote all of his code in Assembly or even better, a hex editor. When the assignment was finally given to us, I could have just died. Not because of how difficult it was but just the opposite and how perfectly suited for the task Python was thanks to its excellent string manipulation.

I finished within the time limit and was satisfied with my code. A discussion afterward with someone I knew was a competent Java programmer made me feel better about the algorithm I used as he ran into some problems I did not. Even if I don't win anything, I'm glad I sucked up my fears and went anyway. I'm not quite sure why programmers intimidate me so much but coming in last in track never bothered me. A silly fear that's hopefully overcome. Best case scenario, I win something and I learn something. Worst case scenario, I learn something.

A bit of an aside to Mr. McCreary -- I think you would be happy to know that I probably spent more time commenting my code than actually writing it. A little over half the lines of my program are nothing but comments.