Startup Lessons Learned

MARCH 25, 2010

It usually looks like this: the can-do attitude and high-bandwidth communication that characterized the first few iterations have produced magic. It usually looks like this: the can-do attitude and high-bandwidth communication that characterized the first few iterations have produced magic. Take a look and let me know what you think.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

MARCH 4, 2009

Thanks to those of you who were willing to fill out the survey, I learned my net promoter score (about 25) as well as some clear other segmentation insights: about 80% of you are founders of or work at a startup, you read many of the same other blogs, and many of you would like to engage with Lessons Learned in formats and venues beyond this blog.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

A Smart Bear: Startups and Marketing for Geeks

OCTOBER 24, 2011

My co-hosts were Bob Walsh and Patrick Foley , hosts of the well-known Startup Success Podcast. Because then you’d miss out on: Whether it’s better experience to build a complete, tiny startup or to do more in-depth customer development for a meatier problem. So I have a question for you, Jason.

Cofounder 208

Cofounder Technical Review Software Review Differentiation 208

Startup Lessons Learned

FEBRUARY 16, 2009

Then we could render the whole site with much less latency, bandwidth usage, and server cost. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? It would be a lot more efficient to send down a compressed packet with the entire sites data and presentation in an optimized format.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68