Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The biggest problem that I see with having heavy QA as a gateway to release (from a lean production perspective) is that it tends to encourage deploying large batches of changes at once. When something goes wrong (which it will) which one of the n changes (or combination of changes) caused the problem. How can you roll back/roll forward a fix to just the one problem?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: