I wouldn't say that this project of mine is "big" in the canonical sense, and it is only meagerly "profitable" by a loose interpretation of the word; but this has been a huge side project from my personal point of view. Essentially, I started this when I was teaching high school full-time and needed a better website for my calculus class. The "big" impact of this project is that it opened a door to a new career for me: I'm now a full-time software engineer and thus measure its profits on the order of my current salary, which is hugely significant to me.
the current task: refactoring my code to incorporate new things I've learned, namely: TDD and knockoutjs + json API. After 2 years of self learning python, I'm looking to transition from teaching into development and am hoping to use this project to showcase what I've learned!
My first big web application has absolutely no unit tests. None. Why? Well, when I first learned to code I was taking the Udacity cs253 course, in which there was no instruction on unittesting in Python, so several of my projects shortly thereafter contained no unittesting. I was actually quite proud of these projects until my brother asked if I had any tests ... "what is a test?" ... his face was priceless.
Thanks - I had not even considered the bit on finding a company I'd like to work for and start contributing to their open source stuff... makes perfect sense.
Also "Rule of thumb, you are never ready. Just go for it" is basically the best advice I've heard for essentially any new task; it's nice to have that reinforced.
Actually both of these approaches make sense to me - I had read something on HN in the past asserting that deadlines dramatically increased the productivity of a particular startup compared to feature goals (as in: "We're launching version 2 on Jan 1. with whatever we can get done before then" vs. "we're going to incorporate XYZ in version 2, and we'll launch it when we do")- so up to this point I've been considering June as a hard deadline. "I need to get as much as I can get done by June" as opposed to "I need to go and collect XYZ skills". Probably the correct approach is being aware of XYZ skills and collect those first, but always having a looming job-jump deadline. Thanks to both of you for your advice!
I wouldn't say that this project of mine is "big" in the canonical sense, and it is only meagerly "profitable" by a loose interpretation of the word; but this has been a huge side project from my personal point of view. Essentially, I started this when I was teaching high school full-time and needed a better website for my calculus class. The "big" impact of this project is that it opened a door to a new career for me: I'm now a full-time software engineer and thus measure its profits on the order of my current salary, which is hugely significant to me.