Jeremy Hilts, Web Developer
As a developer, I’m often presented with a number of problems in need of solving. Is this code reusable? Does this object do too much? Will my use of a ternary operator here over-complicate this section of code? Is this Paul, John or George? (I kid. I can tell them apart.)
Problem solving has always been my greatest ability. I not know for the spoken language good; however, if you give me a paperclip, a piece of chewed up bubblegum (classic flavor only, not your sour apple), and a rubber band, I could make you a CMS … or CRM … or POS. Perhaps, I’ll use a little XML with a some PHP on the back-end. Maybe toss in some SQL. These abbreviations doing anything for ya?
All joking aside, I work with a qualified bunch of people; many of us the jack-of-all-trades sort. It’s difficult for us as a company to commit to a single language or infrastructure, as the tides seem to change quite frequently. We’ve been preaching the “language-agnostic web development shop” idea for a while; and I believe we do it better than a lot of the firms out there twice our size. Before I worked at Q, PHP was the hot seller on the language menu; today, it seems to be C#. Who knows what it’ll be tomorrow.
The only thing that I know for sure is: whatever it is, we’ll figure it out.
This entry was posted on Tuesday, February 17th, 2009 at 11:32 am and is filed under Design and Development. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
You must be logged in to post a comment.