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.
- Great answer and good quotes! I would say that in a perfect world with the perfect team that Strong Code Ownership makes perfect sense. A lot of companies carry dead-weight developers though and when they are given ownership of a task, then everybody suffers and software quality is brought down to the lowest possible level as a result. Extreme programming and collective ownership is better in this case because ineffective developers can be worked around.maple_shaft– maple_shaft ♦2013-02-11 17:08:00 +00:00Commented Feb 11, 2013 at 17:08
- 3@maple_shaft: I would say that in a perfect world with the perfect team that Collective Code Ownership makes perfect sense. All the developers would fully understand all the code and be competent to make changes anywhere. Any developer could do all the work needed for any user story. There would be no bottlenecks as one owner or another became overloaded.kevin cline– kevin cline2013-02-11 17:13:38 +00:00Commented Feb 11, 2013 at 17:13
- @kevincline Good point and a perspective I didn't considermaple_shaft– maple_shaft ♦2013-02-11 17:33:33 +00:00Commented Feb 11, 2013 at 17:33
- Great answer. I think what makes me uncomfortable with Agile is the large difference between my former and new team's practices. In my former team, everybody had Master and PhD degrees in an engineering field. They were first an expert in an area who would then implement specialized code in their domain of expertise. So shared code ownership would be practically impossible. Whereas in my current team, everybody is essentially a computer science major with similar backgrounds and experience, which seems to make shared ownership more feasible.anon– anon2013-02-11 22:44:07 +00:00Commented Feb 11, 2013 at 22:44
- @Kavka: I'm guessing your former team was relying on domain expertise as a substitute for explicit unit-level requirements (i.e. unit tests). Domain expertise is needed to define requirements. It is not needed to implement requirements once defined. In my experience code written by domain experts tends to be difficult to maintain because the domain experts are rarely also expert programmers.kevin cline– kevin cline2013-02-11 23:08:17 +00:00Commented Feb 11, 2013 at 23:08
| Show 1 more comment
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