20 Things in 20 Weeks
Recently I’ve been realising more and more how much time I spend doing things that aren’t productive. Watching TV, playing video games, etc. While some down time is important, I’ve got all these ideas rattling around my head that I’d love to work on, but I keep putting off until some ever-distant ‘later’. So I’ve decided that for the next few months I’d like to be (more) productive, and I’m setting myself a challenge. I plan on implementing 20 Things in 20 Weeks. Some of these ideas are tiny apps, or blog posts, or scripts, and will only take a few hours to complete. Others are rather large and may take a few weeks of solid work.
There are a few reasons behind doing this. I’d like to actually have something to show for my downtime - I’ve had a bunch of these ideas for a long time now and have never gotten around to doing them. I want to keep learning - and the best way to learn is to write code and make mistakes. My software design skills (and UI design, for that matter) are somewhat lacking - the more mistakes I make, the more things I know not to do in the future. And I simply want to challenge myself.
I intend to complete all of this around my other obligations - working full time, obviously, and spending time with my partner, friends and family - so it may be a bit of a stretch, but I’m curious to see what I can achieve if I put my mind to it. At the very least, I’ll have something to show for my time at the end of it.
I’ve written a few loose ‘rules’ around what a Thing is, whether it counts towards the 20, how to keep track of myself, etc:
- A Thing is an idea for an app, a control, a library, something that is interesting, useful, helpful or simply helps me learn something new.
- A Thing doesn’t have to be unique (for example a Stopwatch app is not unique in the slightest) but I have to learn, use or produce something new each time.
- I might get part way through and decide something is “too much” to get done in the time frame, or I might simply not want to do it anymore - I can swap that idea out for something else, or ditch it completely.
- If I can extract something out of any partially completed work into a useful control or a library for something then that counts as a Thing.
- There is no rule that I must only work on one Thing at a time, or on the Things in any specific order.
- I don’t have to produce a Thing every week, or only produce one Thing in any given week.
- Things produced in earlier weeks can be used to help build things in later weeks.
- I must detail at the end of each week what I have done - this should be in the form of a blog post, where I can go into detail, or just provide an overview, depending on how interesting the Thing(s) was/were.
- If I make a Thing worthy of its own blog post, I should write a post for that as well as the weekly one. The blog post about the Thing is considered part of that Thing.
- Some of the Things listed below are blog posts - this is OK. The ‘post about a Thing’ described in the prior point is a retrospective post, rather than a pro-active post whose intent is to be a Thing.
I’ve written up a quick list of ideas of Things I can do over this time. This list will change - I will update it as I go with links to posts, links to finished products, strike-throughs as I drop things and additions as I think of new Things.
Common Android libraries base/sample project that people can copy (including ActionBarSherlock, HoloEverywhere, Guava, etc), with examples, plus rename script (for renaming all the namespaces and the app name etc) - potentially implemented as an Android Studio template?…
Stopwatch app with Start/Stop timer and Countdown functionality
Road Rules Comparison website/app for saying “I’m from New Zealand, what are the road rules in Canada that are different?” and displaying differences
Diary app/website, completely private, for recording what you did that day, including the ability to check in places (privately), what you learned, add pictures, etc, and a “What happened to me on this day last year/last month/last week” function
Text based Twitter client (Yatta - Yet another text-based Twitter app) designed specifically for not consuming much data - no pictures, manual refresh only, no link auto-expansion (Twitter might do this for you?…) etc
A Pinterest-style Android list view, implemented properly so you just attach a ListAdapter and you’re away (Attempted - Blog - Etsy have built a far superior one though, so I doubt I’ll ever touch this again)
LeapMotion Windows controller to maximise/minimise/move windows left/right
App that shows current/max/min speed - should be ideal for using RxJava for streaming location data?
‘Cartoonify’ app that takes a photo + converts it to a cartoon
What’s Shaking, NZ? for iOS (partly written already)
Figure out how to fix the Twitter plugin on the side of this website. (‘Fixed’ it by deleting it - updated the theme at the same time, woo!)
CV/Resume app, with my work history, links to profiles, Twitter stream, G+ stream, etc
Basic RSS reader, maybe?…
Basic flash cards app - math, chemistry, physics, etc.
Social running app, like geocaching you’ve gotta find specific locations and check-in there for points, get more points the more people check in to your submitted favourite running spots
Time localisation differences for Samsung (and other?…) devices examples + blog post
Wedding website for my friends Michael and Rebecca(Oops, they got married!)
Open source Android app licenses page example - Settings app page comes from a file and that file is created during build - what about one-person apps where your build process is File -> Export? (Blog post, Github)
A social network specifically for sharing cat pictures, because cats are awesome.