Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with teamwork
Search options not deleted
user 81981
Questions about working together with co-workers or a team. (Teamwork questions are at risk of being "put on hold as off-topic" for being about career advice or education.)
3
votes
What's with the aversion to documentation in the industry?
Here are my two cents.
The Agile Manifesto states "Working software over comprehensive documentation" and not everybody reads on to reach "That is, while there is value in the items on the right, we …
- 1,713
0
votes
My boss decided to add a "person to blame" field to every bug report. How can I convince him...
I would suggest a combination of:
Humour
Logic - preferably razor-sharp
Positive framing.
For example you could create a bug: 'Person to blame' field fails to capture root causes and fails to addres …