You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- 3+1 For won't fix, it can be a social problem as well as a technical one. Sometimes you just have to say NO. If you keep fixing bugs, particularly trivial or superfluous feature requests peoples expectations will rise and they'll keep asking for more.Benbob– Benbob2011-10-13 09:41:22 +00:00Commented Oct 13, 2011 at 9:41
- 4Having junior programmers fix bugs is a bad idea, unfortunately this is a widespread practice in the industry. The most cost-effective way of fixing a bug is letting the developer that introduced it fix it.Trasplazio Garzuglio– Trasplazio Garzuglio2011-10-13 09:42:28 +00:00Commented Oct 13, 2011 at 9:42
- 6@MarcoDinacci - It depends on what you put in "cost-effective". With a short term view you are correct. But if the project lasts long, giving 'fix bugs' assignments to junior programmer can be seen as an investment.mouviciel– mouviciel2011-10-13 09:52:14 +00:00Commented Oct 13, 2011 at 9:52
- 2@mouviciel I think there are better and more stimulating ways to train junior programmers than let them work on bugs but I do agree that it is a way to learn the codebase. Another problem with this approach is that senior developers may end up just writing code not caring for introducing bugs because there are the junior developers that will fix them anyway.Trasplazio Garzuglio– Trasplazio Garzuglio2011-10-13 09:56:57 +00:00Commented Oct 13, 2011 at 9:56
- 3@MarcoDinacci, let me put it differently: if senior developers need an external process to force them to produce quality work, the team has a fundamental problem. IMHO any good developer - but especially seniors - ought to have an internal motivation for quality. If that motivation is lacking in the opinion leader(s) of the team, the project will almost inevitably fail, one way or another, and no amount of process can help it.Péter Török– Péter Török2011-10-13 13:54:56 +00:00Commented Oct 13, 2011 at 13:54
| Show 7 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you