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.
Required fields*
- Can you add some clarification to what you mean by, "Handing out decisions by edict is a terrible way for any development team to run"? I agree with the rest of your post but I only agree with the mentioned statement in certain ways but not others. For example, how would it be decided to use SOA over a database tier? Wouldn't that have been an edict or wouldn't someone have to have the final say? I ask because I am a team lead and ran into this very situation. I made a call not to use SOA based on business need. There just isn't enough time to allow all developers to discuss/argue every point.Brian– Brian2014-06-27 16:41:20 +00:00Commented Jun 27, 2014 at 16:41
- @Brian making architecture decisions would be a story in a sprint, probably one earmarked for a specific member but otherwise the same as any other story. It should be subjected to peer review like any other story. The time argument is bullshit, if you happened to miss X or decided to try Z that everyone else on the team isn't familiar with you WILL spend more time developing as a result, even a full day of arguing about design would be insignificant comparatively. A simple meeting/review to say "I chose A because X,Y,Z." would likely take an hour and get just made it a collaborative effort.Ryathal– Ryathal2014-06-30 17:27:47 +00:00Commented Jun 30, 2014 at 17:27
Add a 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