Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. He serves on the advisory board of a number of technology startups, and has worked as a consultant to a number of startups, companies, and venture capital firms. Case Study: Continuous deployment makes releases n.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. At the time, I was a die-heard Java zealot. and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JANUARY 12, 2009

The inimitable Paul Graham has an excellent essay called The Python Paradox in which he argues: that you could get smarter programmers to work on a Python project than you could to work on a Java project. I didnt mean by this that Java programmers are dumb. However, it made me remember that Im tired of technology arguments.

PHP 166

PHP Software Review Ruby San Francisco 166