Remove Architecture Remove Continuous Deployment Remove Product Development Remove Technology
article thumbnail

Thoughts on scientific product development

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

What does your Chief Technology Officer do all day? When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. Heres my take.

CTO 168
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Waves of technology platforms

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, September 8, 2008 Waves of technology platforms I still remember the first time I switched to LAMP. That startup didnt turn out so well, but not for lack of technology. You dont need to invent a new architecture, and you dont need to even build your architecture up-front.

article thumbnail

Lessons Learned: Just-In-Time Scalability

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: Achieving a failure

Startup Lessons Learned

Build a world-class technology platform, with patent-pending algorithms and the ability to scale to millions of simultaneous users. Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Even a great architecture becomes inflexible.

article thumbnail

Lessons Learned: Customer Development Engineering

Startup Lessons Learned

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.

article thumbnail

Embrace technical debt

Startup Lessons Learned

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.