Startup Lessons Learned

DECEMBER 7, 2008

And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Even with the highest standards imaginable, theres no way to hire just genius hackers. Hire a CTO or VP Engineering. Worst of all, your teammates are constantly wanting to have meetings.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

JANUARY 12, 2009

Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. But by the time I was building my first websites for commercial use , PHP had taken over. Which makes them exactly the kind of programmers companies should want to hire.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 2, 2008

Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Labels: agile , continuous deployment 1 comments: timothyfitz said. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Steve Blank

JULY 30, 2009

He’s Only in Field Service When I was at Zilog, the Z8000 peripheral chips included the new “ Serial Communications Controller &# ( SCC ). .&# Most startups tend to think they are selling into an Existing market – a market exists and your company has a faster and better product.

Silicon Valley 133

Silicon Valley RSS California Customer Development 133

Startup Lessons Learned

JULY 28, 2010

the version that would facilitate the investment of real money) was planned for late-2009. “Everybody felt the burden of supporting all those transactions every day,&# says Pascal-Louis Perez, kaChing’s CTO. “It took a ton of our time, and just wasn’t contributing to our long term vision.&# The result?

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 2, 2008

This simple feedback loop has proven its worth to me time and again. Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. February 14, 2009 11:12 PM Eric said. May 15, 2009 1:17 AM neocoder said.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

MAY 7, 2009

Lessons Learned by Eric Ries Thursday, May 7, 2009 Fear is the mind-killer Fear is an emotion that slows teams down. For people we hired from larger companies especially, this was challenging. When a new engineer started at IMVU, I had a simple rule: they had to ship code to production on their first day. Great post.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

SEPTEMBER 13, 2008

Thank yo u January 3, 2009 4:07 PM BillSeitz said. May 8, 2009 2:27 PM Eric said. May 8, 2009 2:39 PM VictusFate said. There is much work that I need to do (the only developer so far) before we have something customers can use. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 12, 2008

You might get a bunch of inbound emails from other press and partners, and all of these things can contribute to a feeling that you’re on your way to getting tons of traffic. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. It strokes your ego.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 10, 2008

Labels: Test-driven development 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 14, 2008

is something like "yes, I personally answer the customer support emails." For example, my experience with teenagers is that they are very reluctant to call or email asking for support, even when they have a severe problem. September 25, 2009 5:23 PM jchunter said. They just dont need another authority figure in their life.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 5, 2008

October 13, 2008 9:44 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Want to learn more about me?

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 15, 2008

This gets me into trouble, because it conjures up for some the idea that product development is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. March 26, 2009 6:15 PM Will said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: continuous deployment 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 1, 2008

Labels: Test-driven development 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 8, 2008

So one of the first things we did was to hire an Oracle expert and get to work. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. 1 comments: flixsterwidgettest said. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 18, 2008

If you have a minute, post your answers in a comment, or email me. April 22, 2009 1:26 PM Paul May said. Paul | twitter: @paulmay May 3, 2009 1:48 PM Trace Cohen said. First time here so this question doesnt apply as I havnt read any other posts of yours (yet!). May 4, 2009 6:36 PM acheekymonkey said. How annoying!)

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 6, 2008

April 13, 2009 12:40 PM Gaborsaid. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you? BTW, its FF 3.07 if someone stumbles here. Want to learn more about me?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 10, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Want to learn more about me?

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

Startup Lessons Learned

SEPTEMBER 10, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Want to learn more about me?

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

SEPTEMBER 16, 2008

thanks for the mention:) September 17, 2008 11:56 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 2, 2008

For readers concerned about the chasm, I recommend reading Seth Godin's thoughts on "Being remarkable" and finding a unique edge/twist for your products and marketing (edgecraft). Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Try About the author.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 18, 2008

April 27, 2009 10:55 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Try About the author.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 29, 2008

Lessons Learned by Eric Ries Monday, September 29, 2008 Q&A with an actual reader One of my favorite things about having a blog is the feedback I get in comments and by email. Question 1: When youre adding features to a product used by an existing user base, do you still do split testing to determine usage patterns?

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 22, 2008

As a lot of work seems to progress using email, Google Docs is a natural progression, while allowing our team to upload items and progression without meeting face to face or sending off a number of repetitive emails. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Want to learn more about me?

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 28, 2008

Drop me an email (startuplessonslearned-eric@sneakemail.com) if youre interested and Ill see what I can do. of course, the most convincing narrative usually belongs to the hippo: [link] and when you remove objectivity from your startup, you are going to have a hard time sustaining successful decision making. wow, dead on.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

SoCal CTO

DECEMBER 1, 2010

aka: An Open Letter to the Next Big Social Network) - 500 Hats , November 1, 2010 I've held off writing this post for a long time, because I couldn't quite get my head around all the issues. We had several emails back and forth where he provided basic details on the concept. Call it facts for hire. Hiring The Right Candidate.

Technical Review 175

Technical Review Technology Product CTO Hire 175

techcrunch.com

OCTOBER 23, 2010

Tweet View Comments Guest Author Sep 20, 2009 This guest post was written by Meebo CEO Seth Sternberg. But six months in, you’re gonna cry when you see someone else put out that same product you’re pitching me right now. Like I said, forget everything else and just get your product out the door. I don’t know any developers.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84