Startup Lessons Learned

FEBRUARY 10, 2009

Luckily, Chad Austin has recently weighed in with an excellent piece called 10 Pitfalls of Dirty Code. IMVU was started with a particular philosophy: We dont know what customers will like, so lets rapidly build a lot of different stuff and throw away what doesnt work. But it worked. We made it. So can you.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

www.quora.com

JANUARY 16, 2011

are just emerging for business people (customer development, business model generation,). He correctly identifies the three disciplines that have to be represented in a balanced and collaborative manner: developer, designer, distributer. Levy , Emily Gonzales , Satoshi Suzuki , Joshua M.

Technical Review 51

Technical Review Startup CTO Hire Cofounder 51