Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. Take the example of a design team prepping mock-ups for their development team. Give the dev team your very first sketches and let them get started.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

DECEMBER 7, 2008

Its common to find a hacker at the heart of almost any successful technology company. When a startup encounters difficult technical problems, this is the guy you want solving them. As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. Sure, it seems efficient.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

JULY 13, 2009

For example, heres him discussing our collective blindness to queues: To understand the economic cost of queues, product developers must be able to answer two questions. Today, only 2 percent of product developers measure queues. Second, what is the cost of these queues? First, how big are our queues?

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

OCTOBER 20, 2008

I now believe that the "pick two" concept is fundamentally flawed, and that lean startups can achieve all three simultaneously: quickly bring high-quality software to market at low cost. Thats why we need continuous integration and test-driven development. May your team, one day soon, refactor with pride.

Software Review 164

Software Review Engineer Management Technical Review 164