I’m an operations guy by trade. Over most of my career, that’s basically been the role I’ve played. Even with the aspirations to develop software, in truth, I’ve only flirted with that idea. Sure, I write scripts here or there to get jobs done, or to make my life easier as an operations guy, but I’ve yet to release something with that bears the resemblance of a ‘created with code’ product. For me, this is about to change.
The problem I’ve faced over and over again is the ability to start. Though many of my ideas have merit, they mean nothing without execution. As many programming languages, SDKs, Libraries, Frameworks, and development tools there are, I’ll never make the decision on which one I should choose. I’m convinced now that I should just fvckin’ choose one, and go as far as I can with that particular technology until I’ve reached a hurdle that can’t be leaped.
Realizing this, and having been recently inspired by Jennifer Dewalt’s 180 Websites in 180 Days , and John Resig’s Write Code Everyday , I’ve decided to come up with my own coding challenge. The only way I’ll make it is by challenging myself to do it. I’ll document my progress here, and if anyone wants to keep up, feel free.
I like John’s rules, so I’ll tailor his rules to fit my challenge:
The challenge starts TODAY. Play time is over. 180 Day Coding Challenge, Begin!