Architecture Distribution Engineer Product Development 
View from Seed
NOVEMBER 6, 2014
Then as your business grows, you’ve already established a culture of good engineering practices, you already have the senior staff up to speed, and you’ll find it easy to attract more talent. It means you’ve set up good tooling so that developers can attack problems quickly without a lot of grunt work.
Startup Lessons Learned
APRIL 26, 2009
Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Leveraged distribution channels.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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. Its a nice complement on the product engineering side to his customer development methodology.
The Next Web
DECEMBER 2, 2013
Luck, timing and social engineering are bigger components than most entrepreneurs care to imagine,” adds Werdelin. With the existing product in mind, the $500,000 would be broken out evenly over the nine months with the first two months dedicated to design, specifically user architecture, brand and polish design. 3) Facebook.
Startup Lessons Learned
SEPTEMBER 30, 2008
So I initially gravitated to the CTO title, and not VP of Engineering. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. They might do anything !
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. How to listen to customers, and not just the loud.
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. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. yeah, its awesome.
Expert insights. Personalized for you.
334 
Let's personalize your content