SoCal CTO

FEBRUARY 13, 2013

Once you build it, they will now ask you about the key metrics that they need proven in order to see if you really are a good investment. Even with these, you will have paper-tested your MVP, but the reality is that customers will not be able to assess the value to them until they actually use it. Review the code being built.

Technical Cofounder 338

Technical Cofounder Technical Review CTO Hire Fractional CTO 338

Startup Lessons Learned

OCTOBER 20, 2008

As I evolved my thinking, I started to frame the problem this way: How can we devise a product development process that allows the business leaders to take responsibility for the outcome by making conscious trade-offs? When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

APRIL 26, 2009

The idea of leverage is simple: for every ounce of effort your product development team puts into your product, find ways to magnify that effort by getting many other people to invest along with you. It allowed me to assess the market demand for that offline product before I had the final product baked. Expo SF (May.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

OCTOBER 16, 2013

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. The result was a new process of four-week iterative cycles all about throttling new code.

Lean 167

Lean Startup Software Engineering Agile 167

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. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation.

San Francisco 146

San Francisco Lean Agile Java 146

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

During a lull in her practice she got a serendipitous opportunity to shift gears completely and ended up leading software product development teams. Indeed, most of the innovations we've made at Smart Bear in the art of code review have already been duplicated by both commercial and open-source competitors.

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

Startup Lessons Learned

DECEMBER 7, 2008

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. I am basically a one-man shop.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

blog.expensify.com

APRIL 24, 2012

How about reviewing some of the incredible work being done by the likes of Mark Rendle, Ben Vanderveen, Alex Robson, Jon Skeet, Chris Patterson, Glen Block, Rob Eisenberg or Steve Sanderson? I run a.NET development team and before this gig I spent 4 years running a web app written in.Net. March 26, 2011 at 1:15 am.

Java 107

Java PHP Software Review Coder 107