Startup Lessons Learned

NOVEMBER 17, 2008

Playing with new technologies. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. Seeing whats possible.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

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

NOVEMBER 29, 2008

Some questions have a natural escalation path (like working through the standard operations on a linked-list) and others require some more creativity. Any of these answers can work, and depending on what they choose, it usually makes sense to keep probing along these lines: which operations are the most expensive? Any advice?

San Francisco 146

San Francisco Lean Agile Java 146

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

JULY 29, 2009

Lean vs. debt In the world of physical goods, the leaner a supply chain is, the less debt is required to operate it. To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment. One last thought.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. Halling said.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

OCTOBER 20, 2008

Because there are no tests for new features (or operational alerts for the production code), the code that supports those new features could go bad at any moment. Today, the transformations are often from migrating all those rudimentary legacy systems into a technological windtunnel described by Ray Kurzweil in The Singularity is Near.

Software Review 164

Software Review Engineer Management Technical Review 164

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. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

Campaign 84

Campaign San Francisco Lean Agile 84

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 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 19, 2008

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. FYI the surveymonkey link isnt operational. Case Study: Continuous deployment makes releases n.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

MARCH 20, 2009

They started building BASIC interpreters, but evolved into the worlds largest operating systems monopoly. I think the OReilly audience is particularly important, as so many entrepreneurs got their start in technology (as I did) from their worn-down copy of Programming Perl. Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Continuous Deployment DC 68