Tag Info

New answers tagged

1

There is one drawback: Assigning both tasks in parallel (to two different people) may result in wasted effort, if both end up working in parallel (and reject the change). Consider (measure) how much the two kinds of tasks cost, and how likely they are to result in further changes before acceptance. With those numbers available, you can estimate if it ...


0

since "... the code base lacks documentation" in my opinion it is a good idea to add documentation. But i agree that having personalized comments/log-messages is not a good idea. may be the issue is just to replace personalized comments/log-messages with non-personalized ones? with unpersonlized documentation i mean change from // nike_email: code below ...


2

Your coworker is right. Putting "personalized" text into your codebase is not a good idea, because: 1) As you've described it here, the practice strongly implies that you either assume you'll be the only one maintaining this code, or you'll only ever maintain code that you wrote. Unless this code actually is for you and nobody else, and it never interacts ...



Top 50 recent answers are included