Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Ive attempted to embed the relevant slides below. Startup Lessons Learned - the Conference (April 23.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. Take a look and let me know what you think.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

AUGUST 8, 2009

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. But what about Commodity? With product debt, your users pay the interest.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

NOVEMBER 29, 2008

For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Take a look and let me know what you think.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

DECEMBER 8, 2008

Theoretically, i can visualize the Continuous Integration as RAD ( Rapid action development) along with iterative method, which we used to study in Software Engineering's Process model. March 26, 2010 8:42 AM ankur aggarwal said. the link given in this blog "CI" is very impressive.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136