Remove Architecture Remove CTO Hire Remove Product Development Remove San Francisco
article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? Often times, it seems like people are thinking its synonymous with "that guy who gets paid to sit in the corner and think technical deep thoughts" or "that guy who gets to swoop in a rearrange my project at the last minute on a whim."

CTO 168
article thumbnail

How much does it cost to build the world’s hottest startups?

The Next Web

Therefore, if you want to bring an MVP ( Minimum Viable Product ) to market, Werdelin approximates that you’ll need $50,000 to $250,000 , depending on the skill sets of the developers and designers you hire. Werdelin equates building a successful product to building a nightclub. times that amount in total costs.

Cost 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

Lessons Learned: Just-In-Time Scalability

Startup Lessons Learned

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Just-In-Time Scalability At my previous company, we pioneered an approach to building out our infrastructure that we called "Just-In-Time Scalability." After all, the worst kind of waste in software development is code to support a use case that never materializes.

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. Bring your questions.

article thumbnail

Waves of technology platforms

Startup Lessons Learned

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you? April 23, 2010 in San Francisco.

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: The hacker's lament

Startup Lessons Learned

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.