I’ll Be Making An App For That

As a preliminary explanation, I should note that my school deploys a 1:1 laptop initiative that supplies every student with an Apple MacBook. The laptop is accompanied by a collection of software that our curriculum now partly revolves around. While I’m sure this does not faze some, in my opinion, it is quite a program for a small town in midwest Nebraska.

Earlier this year, a teacher of mine threw around the idea of playing a bit with the iPhone SDK; we would potentially spend some class time working on learning the language and eventually building Apps. It was something that interested me, but with everything I had going on at the time, I didn’t devote enough energy into seeing it through. As a result, obviously nothing came to fruition.

A semester later, Apple’s much anticipated tablet was released and with it came a new market for programming in the iPhone OS. Another technology teacher introduced us to a grant that would provide the funding necessary to get a set of iPads as well as a developer account and the tools we would need to bring them all together. Although my workload had not changed, my interest was peaked enough to give it some serious thought.

I definitely wanted to do it, but I was not convinced I would be able to devote the time necessary to such an undertaking. While I can put my projects on the backburner when time and I are not allies, it is another story entirely when playing on someone else’s dime and, consequently, expectations. While discussing my predicament with my boss, he put forward an idea that would add another level of initiative to the entire thing. Our technology firm has a standing web design department (primarily for local businesses), but he presented the possibility of adding a development layer to our small firm. While we would likely branch out to other areas eventually, we both agreed that SDK work would likely be a good place to begin and would work well with my participation in the grant.

To fast forward a little, I decided to participate in the grant (which will, for the most part, begin next year) as well as shift part of my focus at work from technician to developer. I am still in the very early stages of it all. While I have played with the SDK in the past and know the basic syntax, I still have a lot to learn in the way of the actual language. I am researching a few books that I would like to order to help in this quest of knowledge. Soon I will start going through a course offered online through iTunes U by Stanford Engineering Everywhere which is essentially presented as an introduction to iPhone programming. This will likely extend from the rest of the school year into much of the summer. I will be taking a break in June due to various commitments I already have made (a leadership conference, college visits, etc.) but ideally I would like to be ready to start semi-serious development before my senior year begins.

As for what I will be doing for the project during the next school year, it fully depends on how fast I progress. As I said, I would like to spend the majority of it refining my skills and doing semi-serious development. Educational tools for school and to keep up with my responsibilities to the grant will be my initial area of focus. For work, I plan on creating a mobile interface for the help desk ticketing system we use as a way to teach myself the basics. Plans may change, but I am excited for what I have planned thus far.

My process needs to be documented so I will apologize in advance in case this blog becomes monopolized by the project. Perhaps it will be an incentive for my lazy butt to write about other things as well. As for the quote:

“A programmer is a person who passes as an exacting expert on the basis of being able to turn out, after innumerable punching, an infinite series of incomprehensive answers calculated with micrometric precisions from vague assumptions based on debatable figures taken from inconclusive documents and carried out on instruments of problematical accuracy by persons of dubious reliability and questionable mentality for the avowed purpose of annoying and confounding a hopelessly defenseless department that was unfortunate enough to ask for the information in the first place.”

IEEE Grid