So, I don't have time to work on TaskSmash, but I think it has a lot of potential. Months ago I wrote a blog post offering accounts on it, and despite not linking to it since, there are more than 100 tasks posted every day. People really love it and email me about it all the time.
The PHP code is a bit of a mess. I was a really bad coder when I wrote it, so it's basically just one big disaster of a php file. It's all functional, just not organized or documented. So you'd probably want to clean that up. The big feature that needs to be implemented (that would seriously only take a day) would be to have recurring tasks. There's an API for it that I never made public, and someone is making an android app for it right now.
If this sounds like something you'd like to put time into, you can have 49% of it for $1. I'm keeping 51% not because I actually want to control it, but because I want to be able to look out for the best interest of the users on it, since they trusted me when they signed up. If you decide that you want to sell all the email addresses to a marketer, I need to be able to override that.
You can keep it free, you can make a premium version and charge for it, or you can try to charge a small amount for the existing functionality to NEW users (I'd like existing users to get it free for life). I don't care whether we make money on it or just keep it free. If you make money, you have to give me 51%, if you don't make money, that's fine, too.
I can keep TaskSmash running forever as-is, and obviously don't need help with that. So if you do take it on, I will expect you to actually work on it, both making it better and getting more people using it. Your 49% will vest monthly with a one year cliff. In other words, if you say you're going to take it over and give up within the first year, I get the project back. Not trying to screw you, just trying to make sure that the person who takes it over actually cares about working on it (not full time, just as a hobby is fine).
Let me know if you're interested.
It's surprisingly rare for me to get emails with suggestions for posts, but since posting last week about my startup, I've gotten several requests for a post about programming. Good idea-I should have thought of this before.
Now is a particularly good time to talk about programming, because now is a particularly good time to start a tech business. Every two weeks I go to Startup Poker, where I play poker with a bunch of startup employees and owners. We don't talk about startups all that much, but when we do, a recurring theme is this: there has never been an easier time to start a startup.
The process of starting up a tech company has almost become standardized: two founders join together with an idea, they start building it, take funding, and change the idea along the way as necessary. Amongst the two founders, there are only two configurations that you'll see: either both are "technical" or one is "technical". Technical meaning that they can program and will actually build the product.
Update: the original title was "Reason Why You Shouldn't Hack on Open Source Projects", but commenters pointed out that this title would fit better.
People admire open source contributors, just like they admire entrepreneurs and artists. That's awesome, they'll tell you. Improve the world, I love that. Go for it! (It's easy for them to say.)
But as with anything that becomes more prestigious, people recommending it to you will ignore your opportunity costs, and you may try to do it for the wrong reasons. You shouldn't become an artist so you can be famous, but because there's art inside of you that will kill you if you don't let it out. You shouldn't found a startup to make money, but because it's your life's work. And you shouldn't hack on open source projects because someone told you that your GitHub profile is your new resume, but because you want to code socially. I won't focus on why open source is good in this post, but rather warn you about some common, bad reasons to hack on open source projects.