Continuous Deployment Database Product Development Programming 
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.
Startup Lessons Learned
SEPTEMBER 30, 2008
Massive proprietary databases? Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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. Whats wrong with this picture? I can relate to his experience all too well.
Startup Lessons Learned
JANUARY 19, 2009
Even if you have a referral bonus program, even if youve talked to that person about your company, and even if youve sent a recruiter to call her, I bet you could do more. They maintain a huge database of passive candidates, by offering to pay them when they interview. Particularly the Continuous Deployment and Split testing posts.
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
MAY 1, 2009
One of my personal heroes, Kent Beck , the creator of Extreme Programming and a truly wonderful writer was logged in and twittering, too. 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
Startup Lessons Learned
NOVEMBER 13, 2008
Its why, at my previous job, we were able to get a new engineer completely productive on their first day. We had a great on-boarding process, complete with a mentoring program and a syllabus of key ideas to be covered. Most engineers would ship code to production on their first day. February 11, 2009 8:05 AM Anonymoussaid.
Expert insights. Personalized for you.
144 
Let's personalize your content