Continuous Deployment Database Engineer Product Development 
Startup Lessons Learned
OCTOBER 20, 2008
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. This engineering manager is a smart guy, and very experienced.
Startup Lessons Learned
SEPTEMBER 10, 2008
I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. For more on continuous deployment, see Just-in-time Scalability.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 30, 2008
So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. Massive proprietary databases? Labels: product development 15comments: mukund said. I mean, have you seen other people? Heres my take.
Startup Lessons Learned
JANUARY 19, 2009
They maintain a huge database of passive candidates, by offering to pay them when they interview. Particularly the Continuous Deployment and Split testing posts. Case Study: Continuous deployment makes releases n. If you want to expand your pool of available passive candidates, give a site like NotchUp a try.
Startup Lessons Learned
OCTOBER 19, 2009
But instead of spending the time and money to develop products on spec, TPGTEX creates mocked-up webpages that list the features of a potential new product -- such as a system for making radio-frequency identification, or RFID, labels -- along with its price. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
NOVEMBER 13, 2008
Our bias as technologists is to over-focus on the product part of the problem, and five whys tends to counteract that tendency. Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day.
Startup Lessons Learned
MAY 1, 2009
Related articles by Zemanta Continuous deployment in 5 easy steps (4cloudcomputing.blogspot.com) The Lean Startup workshop coming soon (startuplessonslearned.blogspot.com) The Lean Startup Talk From Web 2.0 You mentioned as many as 50 deployments a day to production after successful local continuous integration.
Expert insights. Personalized for you.
164 
Let's personalize your content