News for hackers. Stuff that matters.
Re:Forrst Blog: How we deploy new features on Forrst by sync on Wednesday July 07, 2010 @08:33PM (#1496049)
Wouldn't this make debugging and (manual) testing so much more difficult?
Re:Forrst Blog: How we deploy new features on Forrst by patio11 on Thursday July 08, 2010 @12:43AM (#1496508)
Feature flags are essentially identical to operating A/B tests in this respect, right? I have a magic button which logs me in as a target user, and it reproduces exactly what they would see, including the results of A/B tests. This helps to reproduce unanticipated interactions between tests. (This has only happened maybe twice, but they were doozies.)
Re:Forrst Blog: How we deploy new features on Forrst by technoweenie on Wednesday July 07, 2010 @11:38PM (#1496404)
Not really. You just add extra tests for your new functionality as usual. If you're replacing old functionality, you'll have duplicated tests until the feature is rolled out for everyone.

I think the key is being able to tell if bug reports are related to an activated feature. For instance, our error tracker tells us which user account triggered the error. From there, we can see what new features they have enabled, and factor that into our debugging.

Re:Forrst Blog: How we deploy new features on Forrst by kylebragger on Wednesday July 07, 2010 @08:43PM (#1496070)
How so? I'm not sure I follow...