I don't think the author is suggesting you go out and hire a "refactor person", a "new feature person", a "documentation person", etc. Rather, assigning the bod

I don't think the author is suggesting you go out and hire a "refactor person", a "new feature person", a "documentation person", etc. Rather, assigning the body of required work to each developer based on her interests. If you have one new feature ticket and one refactoring ticket, don't give the new feature ticket to the developer known for refactoring too often. > But there needs to be constraints on when to start optimizing and when to stop. Now that is very true. But feels like a separate issue to me.