Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

FEBRUARY 22, 2009

See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. May 16, 2009 1:52 PM Todd Green said.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 15, 2008

For example, by making this button green, did more people click on it? That green button was part of a customer flow, a series of actions you want customers to complete for some business reason. Code To make split-testing pervasive, it has to be incredibly easy. One last note on reporting. Great post Eric!

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JANUARY 30, 2009

Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Fail faster.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

AUGUST 24, 2009

And thanks to the radical transparency enabled by the internet, the quality of these proposals is actually constantly rising, to the point that it’s almost impossible to judge the quality of the final product – because all the proposals look polished and professional, even the terrible ones. Is that a lot? Is that good?

San Francisco 113

San Francisco Lean Technical Review Distribution 113