Startup Lessons Learned

JUNE 17, 2010

But according to the theory, this should have been covered by the various specs and documentation we were rigorous about producing. Instead, we spent time making sure the exact behavior of the tools were well documented – by engineers, naturally. Case Study: Continuous deployment makes releases n.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

JULY 3, 2009

The Lean Startup fbFund Edition View more documents from Eric Ries. davemcclure : amazing concepts on Continuous Development => "Cluster Immune System" @EricRies #LeanStartup @fbFund [link] dalelarson : Because most features take longer to argue and prioritize than to build. Case Study: Continuous deployment makes releases n.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

AUGUST 8, 2009

We owe a lot to this seminal document. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Re-reading, I was struck by how much of it we now take for granted.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

OCTOBER 20, 2008

Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors. Case Study: Continuous deployment makes releases n. Second was not changing the requirements without full sign-off.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

FEBRUARY 7, 2013

Struggling to explain the successes and failures of those companies, I discussed principles like continuous deployment, customer development, and a hyper-accelerated form of agile. My personal background was as an engineer and my companies had been Web-based startups, so that is what I wrote about.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

AUGUST 16, 2010

Designed for large businesses, the channels let a company share several types of documents, brand the channel with their own design elements, and then include display advertising, contest promotions, blog aggregation, social media integration and metrics reporting. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

AUGUST 8, 2012

And, as has been documented many times, people tend to work with people like them. In fact, this is a well-documented and universal psychological feeling. You might also look at tactics that you’ve refined in an innovative way--say, a new take on A/B testing or continuous deployment. *

Lean 164

Lean Houston Continuous Deployment Technical Review 164

Startup Lessons Learned

NOVEMBER 5, 2008

Education Guideline Book (1st Edition) Sep 2006 View SlideShare document or Upload your own. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. If not, you might want to take a look.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

NOVEMBER 13, 2008

Each five whys email is a teaching document. We had made so many improvements to our tools and processes for deployment, that it was pretty hard to take the site down. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

MARCH 27, 2009

In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

OCTOBER 16, 2013

As Shutterstock has grown, there are a few key elements to our continued development speed: Small, autonomous teams: The more a team can do on their own, the faster they can go. Continuous deployment: A key component of speed is to keep pushing out work.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

APRIL 18, 2013

In fact, this is a well-documented and universal psychological feeling. Or describe tactics that you’ve refined in an innovative way--say, a new take on A/B testing or continuous deployment. * If you don''t think you''re qualified to speak at a conference like this, you''re probably wrong! Seriously. *

Lean 167

Lean San Francisco Startup Continuous Deployment 167

Feld Thoughts

JANUARY 16, 2013

Or pre-Gmail having a “board meeting folder” in Outlook so I could quickly find the upcoming board meeting documents. PowerPoints, PDFs, Word documents, text files, Excel spreadsheets, Prezi docs, videos, email outlines – the list goes on. No death by endless Powerpoint, no reading a document I’ve already read.

Continuous Deployment 166

Continuous Deployment Distribution Lean Email 166

Startup Lessons Learned

DECEMBER 6, 2008

The advantages of cross-functional teams are well documented, and for a thorough treatment I recommend the theory in the second half of Agile Software Development with Scrum. Case Study: Continuous deployment makes releases n. I want to focus here on one particular strength: the ability to operate semi-autonomously.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

APRIL 7, 2010

I’ve previously documented that early-on in IMVU’s life, we made the mistake of building an IM add-on product instead of a standalone network. I’ve previously documented that early-on in IMVU’s life, we made the mistake of building an IM add-on product instead of a standalone network. Let me illustrate.

San Francisco 154

San Francisco Lean Metrics Design 154

SoCal CTO

JANUARY 5, 2011

500 Hats , January 10, 2010 Developing new startup ideas - Chris Dixon , March 14, 2010 Batch Processing Millions and Millions of Images - Code as Craft , July 9, 2010 jQuery Plugin: Give Your Characters a NobleCount - The Product Guy , March 23, 2010 How do the sample Series Seed financing documents differ from typical Series A financing documents?

Silicon Valley 378

Silicon Valley Startup Term Sheet Venture Capital 378

Startup Lessons Learned

JANUARY 12, 2009

And I think a bad choice, a bad library, a horrible API, lack of documentation etc. You forgot to mention how awesome the documentation on php.net is. Case Study: Continuous deployment makes releases n. If I am forced to make choices, I will stop using the bad choice, unless I am forced to use it. Interesting post.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

I offered an educated opinion about the travesty called "profit based pricing" that the former "community manager" actually fabricated documents as the basis to forum ban me and threatened to permanently ban me as a means to censor the information I sought to share. Case Study: Continuous deployment makes releases n.

Community 158

Community Management Lean Software Review 158