shadchnev

Never forget that success if always a collective effort, so invest your time and energy in relationships with others.

This is a classic 'follow your dream' that attracts classic 'man, face the reality' comments. However, there is no need to oppose one and the other.

I work for a company that was founded 6 years ago and grew to 130 people and 55 million pounds (85 million dollars) in yearly revenues by now. The company never took investment, was started without significant savings by one founder and is still expanding rapidly. We build innovative products, regularly receive awards and make acquisitions. Our profit margins are great. We're more successful than most other companies.

Yet, this company wasn't started as a usual startup. The business started by driving traffic to online shops using google ads. Doing this is actually hard work and it's very unsexy, techcrunch won't write about it and your friends won't say wow. But the company grew from one person to a small team, then to a larger team, the rest is history. Now that we're very profitable we can afford to innovate. Many projects that we started flopped but some survived and are either profitable or growing quickly. I have little doubt that the future of this company is very bright.

Starting a startup is like playing a lottery. Not only you have to invest some of your time and money into it, you also have to be lucky. Actually, you have to be very lucky. The line between success and failure when you have no cash reserves is extremely thin. You are free to take the risk but you should accept that most probably you'll fail.

A better way to innovate is to earn some money before you actually innovate. Our company did it by working in affiliate business, your way may be different. Our company didn't innovate when we could not afford to lose. However, once we could afford it, we opened a sizeable division responsible for innovations and it's paying off. As I've said, most projects fail but fortunately we can afford it. We learn and move on.

There's a difference between doing something and achieving a result. If you want to be a part of a startup, start one, it's free and easy, I've done it a couple of times. If you want to build a business and make money, find a way to pay for your mistakes and bad luck when it happens.

Go out and figure out how to make some money, not millions but a little bit in the least risky way. Affiliate traffic like our founder did? Maybe buying and selling stuff on ebay? Maybe something else. Just build an unsexy old-fashioned business that will generate money and then you'll be in a position to innovate, follow your dreams and all that stuff.

This worked for our founder and I'm pretty sure it's a much shorter path to success than learning to code at night or building the next twitter on weekends. If you want the result, ruthlessly minimize the risk even if it means building a less sexy business first. I guess this won't be a very popular advice though.

That's http://www.getinvisiblehand.com :)

I'll be there!

Imperial College. In addition to a very strong Computing department (see other reviews, league tables or just believe me, I've got MSc Advanced Computing from there), it's situated in London, where many exciting IT companies are based. I would never have met so many great hackers/founders etc. if I chose not to study in London.

Yes, you're right, there is no way of knowing that we suggest the best bargain and not the most profitable affiliate link. However, we promise we are not doing this because we believe that the way to success is by providing the best service for the user, so irrespective of the commission, you'll always get the biggest price difference we have.

We do use affiliate IDs but we don't ever redirect without user's explicit permission (user has to click a button). Is it really evil? why?

thanks!

You're absolutely right. I set up a mail client to download mails weeks ago and it was downloading them 1 at a time (seems like a server limitation), so it wasn't a problem until today, when it downloaded first unread messages ever. I didn't suspect it because it's been operating for weeks in the background and didn't cause any problems.

Thanks for help!

I hate it but I still try to force myself to do it. It really, really helps to find bugs if refactoring or a new feature breaks something, so it's a necessary evil. I call it evil because unit-tests themselves have to be written and debugged, which takes time. I believe I should just practice more, so that I could write them incredibly quickly, then they won't suck.

Congratulations!