rmtutty

You're describing me until about age 30.

1. You need to realize that if something was easy or obvious, it would already exist. The only things worth doing are things that appear impossible.

2. Don't try to keep it all in your head at once. Get good at making a plan or a list of steps, following them (almost blindly), and correcting course every few steps. Taking a big problem apart and bringing small steps to completion keeps things interesting.

3. Make sure you're doing something you're personally interested in. Not everyone is cut out to dig ditches for the man.

Site's not available?

You don't need to read the article. The title is the least whitewashed portion, it just gets more ridiculous from there.

I bought an Asus Zenbook Prime about a year ago. Been running Ubuntu 12.04, then 13.04, now 13.10 on it with basically no issues. Multi-monitor, bluetooth devices, wireless keyboard/mouse, the whole thing.

Stop being a fuckhe.....oh, nvm.

The derp is strong with this one.

What do you want from a CTO? As a serial CTO/lead dev/architect-y guy, I can tell you that the title can be extremely varied in interest and actual duties.

Are you looking for someone to select the tools and the way those tools work together to meet your goals? Then they might not want to see an already built product.

Are you looking for someone to help you scale the application as engagement (hopefully) goes through the roof? You may be looking for more of a devops person.

Are you looking for someone to set up the developer culture, the process and hire/mentor an internal team? A good lead developer can handle these issues.

Are you looking for someone to which to hand ALL of these issues, to just handle them? Then, you are actually looking for a CTO. This person will be more expensive than the others, and will likely drive additional expenses through hiring those others as well. So consider your MVT (minimum viable team) as well as MVP, and go looking for the people you really need.

Best of luck!