Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Eric, Is this post about Architecture? Good luck, engineering manager.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 8, 2009

And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.)

Software Review 87

Software Review Design Software San Francisco 87

Hearpreneur

FEBRUARY 8, 2023

3- Finance Club Photo Credit: Jonathan Tian I am enrolled with the Finance Club on LinkedIn to enhance my business operation beyond boundaries. These are just two of the many reasons why I think you should consider being a member of an architectural professional group. The group also provides counseling for couples and families.

Community 96

Community Architecture Entrepreneur Networking 96

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. Its likely that the new release will contain new bugs.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

JUNE 15, 2009

One large source of waste in development is “double-checking.&# For example, imagine a team operating in a traditional waterfall development system, without continuous deployment, test-driven development, or continuous integration. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Seeing Both Sides

AUGUST 3, 2012

Technical founders Tom Leighton and Danny Lewin built the original prototype at their lab at MIT starting in late 1996 before raising capital, so in a sense Akamai’s Minimum Viable Product (MVP) was a prototype with the basic architecture and traffic mapping in place that validated algorithms for the founders and investors alike.

Distribution 49

Distribution Lean Massachusetts Cofounder 49

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. and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. what happens if we have a pipelined architecture?

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Support multiple sharding schemes. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

NOVEMBER 13, 2008

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. For my first time, it was scalability problems and our operations team. Now, everyone is learning together - about your product, process, and team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

adam.heroku.com

MAY 18, 2012

Founders and early employees tend to be very self-directed so the need for management is nearly non-existent. The team should own the vision and direction for the part of your product that it works on. A close mapping between your software architecture and your team architecture will be a big help here.

Developer 92

Developer Database Architecture API 92

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

DC 90

DC Washington San Francisco SBIR 90

techcrunch.com

OCTOBER 23, 2010

This is the first post in what’s going to be a series of blogs on how to go from nothing – no connections, no team, no money and no knowledge of how the startup industry really works – to operating a growing business. I’m taking a 52 week course in how to start up, run, operate, and achieve self employment. and Google.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

Steve Blank

OCTOBER 26, 2020

Joe Felter , Raj Shah and I designed a class to examine the new military systems, operational concepts and doctrines that will emerge from 21st century technologies – Space, Cyber, AI & Machine Learning and Autonomy. Now the problem is, in the diagram below on the left, this is what our DOD architecture looks like today.

Artificial Inteligence 396

Artificial Inteligence Fractional CTO Technology CTO 396