With all my love to Mr. Levels[1], I'm personally glad the author decided to approach this as their little "Tiny projects" rather than "Follow me as I build six startups in six months". I feel it nicely sets expectations to what I can get out of checking out each project and thinking "well, it's just a tiny project after all, why can't I have made something like this ever month too?". The 12 startups idea was also inspiring to me but I disliked how the term so frequently leads people to (IMO) somewhat pointless analysis of "Is this even a real startup?" around each individual project.
Six Months of Tiny Projects
81–90 of 151 posts
Re: Six Months of Tiny Projects
#82I don't understand why the other comments are being so negative, this is awesome . There's a Jony Ive quote along the lines of "when you build something, you get the actual thing, but even more valuable is how you've grown and changed from building that thing. Best of luck on your future projects, great on you to make awesome stuff and grow as a person!
It's good that he built some side projects and seems like he learned a lot. And the process and write ups are entertaining, but I understand some of the negativity. He comes off as peak tech bro, instead of talking about how he's making the projects for fun or for learning everything is about monetizing or getting views on (admittedly!) poor quality hackathon projects. Dialing down some of the tech bro and the focus on making "products" and I believe the negativity would go away. It doesn't help that his idea process seems to be "what can I make that is like something else, but significantly worse" :). I think it's a great achievement in rapid development, however
Re: Six Months of Tiny Projects
#83> Today, people have created over 1400 stores, selling everything from t-shirts, to human beings. Selling human beings!!! really?
If you're interested, my mother in law is for sale. Very cheap but she comes with a no return policy.
Re: Six Months of Tiny Projects
#84This is a good exercise in estimating workload.
While the article says one week is insufficient to make something meaningful, I've found personally that you can write useful software even in a single day, as long as your feature scope is finely targeted. Actual real life needs of real people are also more interesting to write software for.
Re: Six Months of Tiny Projects
#85> I'm anxious for the month I can't find any new social platforms.
I doubt that'll be an issue for some time, there are so many startups out there either trying to be the next big one or specifically to address the needs of a niche set of users.
Once the project hits a certain level of public awareness new social projects will be contacting the author to ask to be included, there will be no "looking for them" involved (though perhaps some due diligence checking to make sure the platform isn't in some way a project they'd rather not be associated with).
Re: Six Months of Tiny Projects
#86I don't understand why the other comments are being so negative, this is awesome . There's a Jony Ive quote along the lines of "when you build something, you get the actual thing, but even more valuable is how you've grown and changed from building that thing. Best of luck on your future projects, great on you to make awesome stuff and grow as a person!
It's good that he built some side projects and seems like he learned a lot. And the process and write ups are entertaining, but I understand some of the negativity. He comes off as peak tech bro, instead of talking about how he's making the projects for fun or for learning everything is about monetizing or getting views on (admittedly!) poor quality hackathon projects. Dialing down some of the tech bro and the focus…
What is your definition of “tech bro”? The post comes off to me as someone who is humble, introspective, interested in technology, interested in testing out new ideas, and interested in getting better. Not sure what’s “tech bro” about any of that, but maybe that means I’m a tech bro, bro! /joke
Re: Six Months of Tiny Projects
#87This is such a great way to keep the sword sharpened. I am really excited to see and quite inspiring that the author even embarked on this mission.
Re: Six Months of Tiny Projects
#88>> 1-2 months is a more reasonable tiny project timeframe. It gives you enough time to build something with substance, and test the idea thoroughly.
This is a similar timeframe that Basecamp uses for internal initiatives. I've been pushing for us to switch from 2-week sprints to something closer to 6-week features. If you're building on existing product or a brand new one 1-2 weeks is just not enough time for meaningful progress.
Re: Six Months of Tiny Projects
#89I find this inspiring and think I might do this myself. I have a huge list that makes me anxious to work on, but doing so publicly might force me to do some of them.
Re: Six Months of Tiny Projects
#90snormal is really good