Continuous Deployment Engineer SEM Web 
Startup Lessons Learned
SEPTEMBER 7, 2008
Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Its a nice complement on the product engineering side to his customer development methodology. .
Startup Lessons Learned
SEPTEMBER 22, 2008
I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." In this model, you take some fraction of the lifetime value of each customer and plow that back into paid acquisition through SEM, banner ads, PR, affiliates, etc.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 15, 2008
See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. Since that time we've seen a massive change from product engineering to financial engineering. Expo SF (May.
Startup Lessons Learned
SEPTEMBER 2, 2008
Labels: agile , continuous deployment 1 comments: timothyfitz said. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n. Expo SF (May. Conference streaming, sponsors, discounted tickets.
Startup Lessons Learned
NOVEMBER 7, 2008
Dont worry about selecting particularly good keywords, if youre new to SEM. Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. SEM only gets at one segment of users, and for a brand new product, you presumably need some skill at marketing in general and adsense in particular to get any useful info.
Startup Lessons Learned
SEPTEMBER 10, 2008
This is still an essential practice, especially on the web. There was a time when "web content" was considered "not code" and therefore not routinely source controlled. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. Do you make daily builds?
Startup Lessons Learned
SEPTEMBER 30, 2008
So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. Was it an important or irrelevant fact that most of our web code was procedural and not object-oriented? I mean, have you seen other people? Heres my take.
Expert insights. Personalized for you.
131 
Let's personalize your content