Hacker News new | past | comments | ask | show | jobs | submit login

Good read, but what the article only mentions at the end is that the first step for all of these strategies is:

"Work really, really hard."

Writing a book, creating a whole icon set, or creating GitHub are all much harder and more time-consuming than doing client work.

So I think the biggest barrier to earning money while you sleep is probably the amount of work involved, not the lack of ideas.




So, earn money in your sleep by working really hard and not sleeping for a long time. Kind of like it taking 10 years to become an overnight success.


So true...I've been publishing apps on the iOS app store for the last 3 years and get an hour of sleep during development. But once the app is live and earning money, I can rest easy and sleep 8-9 hours a night. Over a span of 5 years, it basically averages out to about 5-6 hours of sleep a night, which seems normal.


Not really. If your day job is designing icon sets, then pumping out one more on the side isn't really all that hard. Especially if your day job is designing a client site that happens to need a whole bunch of icons for a client who doesn't consider things like generated IP to be worth protecting.

There are lots of examples of this sort of thing that make it pretty straightforward to take something that you're doing anyway and spin it off as a product that brings in revenue. If fact, the product that pays my rent (S3stat) was exactly that: something we needed in house that turned out to be something other people would pay for.

So yeah, it's probably not anywhere near as much work as you expect. And like people are telling you elsewhere, once it's built, it stays built, and the money keeps rolling in.


Are you kidding? The last think I want to do after I do my day job is more of my day job. I think lots of people feel this way and that's why they find the article valuable, the realization that their extra time can be parlayed into future earning. But yeah, it will take time and work, sometime time and work some of us just can't bring ourselves to do, no matter the future value.


The difference between the two is that work for a client can typically only be sold once. Work like creating an icon set or writing a book can be sold infinitely and require virtually no post-support. Additionally, those streams of income can continue while you're working on more client work if that's your thing.


Not necessarily, for some client work I've reduced my price in exchange for full ownership (or rather, co-ownership) of the product I've developed. That way I can do with it what I want.


Except you can also scale your consulting business by hiring or tying up with other devs. This means you can still earn while others are working for you!


I recommend you to read this article: http://blog.asmartbear.com/consulting-company-accounting.htm...

While I don't agree with everything he says, there's a large amount of truth in that post.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: