Startup Lessons Learned

JANUARY 19, 2009

I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. For example, lets say you dont have an operations team, and so youre still getting paged late at night when servers crash. Is it time to make your first operations hire? That depends.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. these devices all need human instruction to enable correct and desired operation. Case Study: Continuous deployment makes releases n.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Good luck, engineering manager. It was painful for a lot of people.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

FEBRUARY 7, 2013

Scott Summitt iteratively leveraging the emerging technologies of digital fabrication and 3d-scanning to change people's lives. PayPal, under the leadership of David Marcus and Bill Scott, re-defining and re-engineering itself by embracing Lean Startup to improve the product experience. Lean Startup has gone mainstream.

Lean 167

Lean Entrepreneur San Francisco Agile 167

Startup Lessons Learned

NOVEMBER 11, 2008

Its an academic treatise that tries to answer a seemingly straightforward question: after World War II, why did Silicon Valley become the undisputed leader of the technology world, while Bostons Route 128 corridor did not. Worldwide developments based on this research led to modern radio communication, television, and the electronics age.

Silicon Valley 68

Silicon Valley San Francisco Lean Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. Still, a startup product development team is a service organization. Labels: hiring , product development 5comments: TedHoward said. Any advice?

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

NOVEMBER 19, 2008

This wasnt an education product - it was a pretty surprising group to find using it. What all these teachers had in common were two things: they were technology early adopters that were willing to take a chance on a new software product, and they all had similar problems organizing their classes and students.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. Case Study: Continuous deployment makes releases n. This is what the BSD license was invented for, for example.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

NOVEMBER 17, 2008

For example, should we invest a week of engineering time into making our website more failure-proof (which were pretty sure will pay off right away) or into experimenting with a new technology (that might pay off in months, years, or never)? Case Study: Continuous deployment makes releases n.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

FEBRUARY 22, 2010

I’ve seen many times what happens when a single department get’s holed-up in its own space, like the terrifying “ operations cave.&# I’ve seen many times what happens when a single department get’s holed-up in its own space, like the terrifying “ operations cave.&#

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

MARCH 20, 2009

They started building BASIC interpreters, but evolved into the worlds largest operating systems monopoly. Each of these companies were fortunate to have enough time, resources, and patience to endure the multiple iterations it took to find a successful product and market. Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

JANUARY 12, 2009

However, it made me remember that Im tired of technology arguments. But I think debates about which language, which operating system, even which editor (emacs, vim, Visual Studio) can go on forever. Case Study: Continuous deployment makes releases n. January 16, 2009 2:02 PM Chrissaid. Nice article.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

NOVEMBER 5, 2008

What I found particularly interesting, looking back, is that the McCain campaign had superior technology, voter lists, and numbers on their side. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Campaign 84

Campaign San Francisco Lean Agile 84