Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Thats more than just drawing architecture diagrams, though. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JUNE 17, 2010

The team hired only the best and the brightest. They are leaders, visionaries, founders and managers having tremendous success. They either had to hire a developer onto the art team itself (unthinkable) or learn those development skills themselves (which was, to be fair, really hard).

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

JULY 29, 2009

For example, at a previous virtual world company , we spent years developing an architecture to cope with millions of simultaneous users. The downside was that we had to combine dozens of projects whose internal architectures, coding styles, and general quality varied widely. Sometimes quick and dirty actually incurs less debt.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 8, 2008

So one of the first things we did was to hire an Oracle expert and get to work. You dont need to invent a new architecture, and you dont need to even build your architecture up-front. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Were in a new wave of platform evolution.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Steve Blank

FEBRUARY 22, 2016

The show follows the journeys of founders who share what it takes to build a startup – from restaurants to rocket scientists, to online gifts to online groceries and more. Additionally, he is the co-founder of ConnectYard , a social analytics platform for e-learning platforms. We did do a lot of … customer discovery.

Cofounder 120

Cofounder DC Entrepreneur Silicon Valley 120

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. Customer Development is itself an example of SBCE. We owe a lot to this seminal document.

Software Review 87

Software Review Design Software San Francisco 87

Steve Blank

NOVEMBER 9, 2009

This required convincing software vendors to move their applications to our unique machine architecture. Not a trivial job considering our computer was one of the first parallel architectures, and our compiler required specific knowledge of our vector architecture to get the most out of it.

Silicon Valley 327

Silicon Valley Software Review RSS Technical Review 327

Startup Lessons Learned

OCTOBER 20, 2008

Eric, Is this post about Architecture? I define Architecture (capital A) as "the advocacy for human values in a process" (not little a architecture, over-arching structural approach, just design-in-the-large). The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

APRIL 26, 2009

Other companies accomplish this by hiring a large staff of content production experts - and get a very good result. Plus, we saw some of the intrinsic limitations of supporting such a large staff: slower cycle times, higher cost basis, and - most importantly - the ability to serve only a limited number of customer segments.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

JUNE 15, 2009

Both sides start to think of their point of view in moralistic terms: “those guys don’t see the economic value of fast action, they only care about their precious architecture diagrams&# or “those guys are sloppy and have no professional pride.&# No departments The Five Whys for Startups (for Harvard Business R.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

DECEMBER 28, 2009

Switching these customers directly to continuous deployment sounds harder than it really is. A typical "new feature" release is, in my experience, about 80% changes to underlying APIs or architecture. Switching these customers directly to continuous deployment sounds harder than it really is.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

NOVEMBER 29, 2008

Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. This second objective plays no small part in allowing you to hire the best. Hiring decisions are among the most difficult, and the most critical.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Just change it.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

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. Customer data is normally partitioned according to customer id.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JULY 13, 2009

But it goes beyond that, including techniques for improving the economics of product development. Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet. No departments The Five Whys for Startups (for Harvard Business R.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? What is customer development? No departments The Five Whys for Startups (for Harvard Business R.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 16, 2009

Lets start with a distinction between shipping new software to the customer, and changing the customers experience. The idea is that often you can change the customers experience without shipping them new software at all. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 8, 2009

I started my last company with 100% off-shore resources because I could never have completed Customer Development at a reasonable cost of money or regulatory burden had I employed US Citizens. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

SEPTEMBER 22, 2008

Someone has managed to convince themselves that they have to do their big architecture change in one fell swoop. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? When Ive worked to get everyone to build in small batches, I would see this pattern in action.

Product Development 68

Product Development Developer San Francisco Product 68

www.quora.com

JANUARY 16, 2011

Find Questions, Topics and People Add Question Add Question Non-Technical Co-Founders Co-Founders Technical Co-founders Finding Co-Founders Startups & "How Important Are Ideas?" " Web Development Startups Solo Founders I am a creative guy with a startup idea.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

techcrunch.com

OCTOBER 23, 2010

One of the things I do as a founder of a later stage startup is to meet with early stage entrepreneurs to help them get their companies going. Inevitably, the excuses begin: I need to hire people to build the product. I don’t know any developers. Then, forget everything else, VCs included, and just build. and Google.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

Startup Lessons Learned

JANUARY 30, 2009

Hire the absolute best and the brightest, true experts in their fields, who in turn can hire the smartest people possible to staff their departments. Here are a few: We know what customers want. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

www.rocketwatcher.com

DECEMBER 5, 2011

I had 2 conversations with startup founders this week that are trying to decide on a name for their company and I felt their pain. Most startups start out with only 1 or 2 offerings and often aren’t thinking about how things might fit into a naming architecture. customer development. customer retention.

Naming 41

Naming Startup Product Name Framework 41

Startup Lessons Learned

JANUARY 28, 2009

The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. On the other, they already have a team fully engaged on making their product architecture better.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79