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 team
Search options not deleted
user 29344
It refers to the group of people (software developers, testers, project managers, product owners, etc.) who are working on the same project or company. However, usually it refers to a team of software developers.
15
votes
How do I convince my team to use smaller classes/methods?
Code Complete, by Steve McConnell, has tons of good statistics on the very topic you're talking about. I don't recall all the numbers, but he talks about how numbers of bugs increase with longer metho …
- 399