Edit - Software Engineering Stack Exchange

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.

5

Two points: * Give "Developer proficiency" a pretty high weight, as Basile mentioned in his comment. * Consider repeating the process after discussing the results. People may find that their initial assumptions about suitable weights and scores were steering the process in an undesired direction. For example, if everyone agrees that execution speed should have utmost importance, you might end up with a technology choice that the team is unable to handle.

Hans-Martin Mosner
– Hans-Martin Mosner

2021-12-09 09:26:08 +00:00
Commented Dec 9, 2021 at 9:26

Add a comment |

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

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>

formatting help »
answering help »