Remove 2005 Remove CTO Hire Remove Founder Remove Open Source
article thumbnail

HOW TO: Hire the Perfect CTO

mashable.com

Hiring the wrong person for key company positions can cost a business thousands — or tens of thousands — of dollars and man hours. This is especially true when it comes to tech companies hiring the wrong chief technology officer. Leadership Abilities Are A Must It’s natural to want a tech savvy and competent CTO.

article thumbnail

Lessons Learned: Great open source scalability tools from Danga

Startup Lessons Learned

Lessons Learned by Eric Ries Friday, September 5, 2008 Great open source scalability tools from Danga If you are trying to build a scalable LAMP service, its always best to start with the original and still quite relevant presentation, from Brad Fitzpatrick when he was at LiveJournal. You can find the 2005 version here.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

From Nothing To Something. How To Get There.

techcrunch.com

One of the things I do as a founder of a later stage startup is to meet with early stage entrepreneurs to help them get their companies going. Nine times out of ten, the meeting ends with them asking me for introductions to VCs. Inevitably, the excuses begin: I need to hire people to build the product. and Google. No legal muck.

article thumbnail

CEO Friday: Why we don’t hire.NET programmers

blog.expensify.com

Update: The end is near, Expensify is hiring a.NET programmer! As you might know, we’re hiring the best programmers in the world. If you are a startup looking to hire really excellent people, take notice of.NET on a resume, and ask why it’s there. Expensify Blog. Expense Reports That Don't Suck.

Java 107
article thumbnail

Lessons Learned: Why PHP won

Startup Lessons Learned

When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. At IMVU, when wed hire a new engineer, we could get them to ship code to production on their first day, even if they had never programmed in PHP before. As always, Paul is right.

PHP 166