Steve Blank

MAY 28, 2009

For example, complex new semiconductor architectures, (i.e. a new type of graphics architecture, or a new communications chip architecture) mean you may not know if the chip performs as well as you thought until you get first silicon. Reply Alpha Testing « Two Sixes Blog , on July 5, 2010 at 7:04 pm Said: [.]

Vertical 144

Vertical Silicon Valley Marketing Customer 144

Steve Blank

MAY 11, 2009

They had this great architecture, and Apple had figured out to get movies into their own computers for a demo, but for the rest of us there was no physical device that allowed an average consumer to plug a video camera or VCR into and get video into a Mac. It was fun watching it happen. com Michael Robertson.

Video 164

Video Silicon Valley RSS California 164

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. Yet there is one silver lining when it does happen: we wind up throwing out working code , debt-riddled and elegantly designed alike.

Technical Review 168

Technical Review Software Review San Francisco Lean 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. After all, the worst kind of waste in software development is code to support a use case that never materializes. Case Study: Continuous deployment makes releases n.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Steve Blank

NOVEMBER 30, 2009

Customer Development is all about gathering a list of what features customers want by talking to them, surveying them, or running “focus groups.” Customer Development is all about gathering a list of what features customers want by talking to them, surveying them, or running “focus groups.”

Customer Development 278

Customer Development Developer Customer Silicon Valley 278

Startup Lessons Learned

JUNE 17, 2010

Lessons Learned by Eric Ries Thursday, June 17, 2010 No departments Big companies have departments. The artists on the team had called in the big guns, and VP-level folks were there to explain the importance of certain aspects of the visual design that threatened to be cut. Startups are companies. Why do companies have departments?

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

OCTOBER 20, 2008

For many projects, customer approval and sign off was required as well. Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors. Eric, Is this post about Architecture? Im keen on the two-kinds-of-bugs thing.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 8, 2008

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? Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Were in a new wave of platform evolution.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

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. You might have the interaction designer who designed it take a look to see if it really conforms to their design.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

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.&# Glad you don't develop software for space shuttles.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

APRIL 26, 2009

But part was a recognition that we could gain substantial competitive advantage by leveraging a community of like-minded visionary customers to serve a wider (and more mainstream) audience than we could alone. Making UGC work requires good tools, open standards, and proper incentive design. A true follower of Wikinomics concepts.

Product Development 88

Product Development Developer San Francisco Product 88

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 324

Silicon Valley Software Review RSS Technical Review 324

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

blog.startupsquare.com

APRIL 13, 2010

2 Comments Tags: Customer Development , lean startup , pivot , Strategy. Having gone through 51 iterations of my mockups and gathered as much as feedback as I could with our primitive alpha, I feel confident about our basic customer problem hypothesis. This is “Customer Need&# in Eric’s list.

Lean 40

Lean Startup Cofounder Architecture 40

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. Product development deals in designs, which are fundamentally intangible.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

NOVEMBER 29, 2008

and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. Its nearly impossible to get a good read on all six attributes in a single interview, so its important to design an interview process that will give you a good sampling of data to look at.

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

San Francisco 151

San Francisco Architecture Startup Database 151

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? Building a good application architecture is not just coding. Its common to find a hacker at the heart of almost any successful technology company.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

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. Its design goals arent geared towards efficiency in terms of technical costs.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

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? Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, What is customer development?

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

www.quora.com

JANUARY 16, 2011

" => I have not bothered to put up a landing page, survey to test customer demand, or done any customer development whatsoever. "Where is the best place to find a rockstar developer to bring it to life?" 24 Comments • Nov 8, 2010 I love this answer. Yishan Wong • Nov 8, 2010 lol.if

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

Startup Lessons Learned

SEPTEMBER 8, 2009

Policy makers need to know: regulations designed to manage big-companies actually protect those companies by stifling innovation (and competition) from startups. You can see the design of the program here. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? conference attendees.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

SEPTEMBER 22, 2008

Keep split-testing, but keep this iron rule: if it doesnt change customer behavior, its not a feature. A second idea is that less is more in product design: A key tenet of the philosophy is that uncluttered products with fewer, better features are preferred to similar products with more features. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Steve Blank

APRIL 16, 2009

The plug-in co-processor architecture was too complex and couldn’t be made to work reliably. Nothing else was in the development pipeline for the next 12 months. This turned out to give our customers immense value. Now we could give customers lower price boards without Engineering spending 12 months to design new ones.)

Silicon Valley 134

Silicon Valley Product RSS Engineer 134

techcrunch.com

OCTOBER 23, 2010

The problem is that many programmers have loads of talent with no product sense and business students have great designs with no way to implement them. Programmers feel exploited when they build out a product that is successful but are reluctant to admit they wouldn’t have been able to design the product themselves.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

Startup Lessons Learned

JANUARY 30, 2009

Insist on high levels of usability, UI design, and polish. Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. 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

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