article thumbnail

Think about Performance Before Building a Web Application

TechEmpower

We’ve heard this from startup founders, product managers, development team leads, CTOs, and others who see their product gaining traction, but simultaneously see performance falling off a cliff. Too often though, it’s the result of performance needs not being properly assessed at the start of work. So, why does this happen?

Web 200
article thumbnail

Startup Advice: When to Use a Consulting CTO

rapidrollout.wordpress.com

Investors use a consulting CTO for technical due diligence. A consulting CTO can help you find and qualify a permanent technology partner, a lead developer, a user experience expert or interaction designer, a graphic designer, or a VP of engineering. third party to vet or manage&# your development team.

Insiders

Sign Up for our Newsletter

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

article thumbnail

The Principles of Product Development Flow

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Wow, great review!

article thumbnail

How to pick a co-founder

venturehacks.com

SUPPORTED BY Products Archives @venturehacks Books AngelList About RSS How to pick a co-founder by Naval Ravikant on November 12th, 2009 Update : Also see our 40-minute interview on this topic. Learn more about: Founders 40 responses so far · Comments RSS # scott edward walker · Nov 12, 2009 Great post.

Cofounder 101
article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

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. A project usually has an absolute duration and budget whereas the time and money dedicated to development within the project is where the tradeoffs are made.

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 they see a problem with the teams process, why dont they just fix it? When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding.

article thumbnail

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. what happens if we have a pipelined architecture?