Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

NOVEMBER 13, 2008

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Instead, five whys kept leading to problems caused by an improperly trained new employee, and wed make a small adjustment. and so forth.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 29, 2008

On the one hand, it gives you insight into what kind of employee the candidate might be. Some questions have a natural escalation path (like working through the standard operations on a linked-list) and others require some more creativity. Case Study: Continuous deployment makes releases n. I use the circle question, too.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

NOVEMBER 17, 2008

Have you met that prickly operations guy who seems to love servers more than people (but would never let them fail on his watch)? It has to balance competing goals of establishing clear ownership, while avoiding talented employees getting stuck. Case Study: Continuous deployment makes releases n.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Case Study: Continuous deployment makes releases n.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 13, 2010

Lessons Learned by Eric Ries Monday, September 13, 2010 The Superbowl ad test I am a firm believer in the danger of vanity metrics , numbers that give the illusion of progress but often mask the true relationship between cause and effect. Vanity metrics are generally bigger. Vanity metrics. The solution? Is that really news?

San Francisco 154

San Francisco Metrics Lean PR 154

Startup Lessons Learned

MARCH 20, 2009

They started building BASIC interpreters, but evolved into the worlds largest operating systems monopoly. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

JANUARY 12, 2009

But I think debates about which language, which operating system, even which editor (emacs, vim, Visual Studio) can go on forever. There is a stark difference between both types of employees. Case Study: Continuous deployment makes releases n. However, it made me remember that Im tired of technology arguments.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

It took hundreds of years for newspapers to learn to behave as worthy holders of this public trust and cover the news without fear or favour, and create a firewall between news and views and the ad-sales side of the operation. And when you have employees who really believe they are deserving of such, you are building a bad product.

Community 158

Community Management Lean Software Review 158