Timeline for What does "programming in a vacuum" mean?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 31, 2011 at 19:29 | comment | added | KeithS | Depends on if the programmer even has access to those communication channels. In certain corporate cultures, all input regarding code work goes through either the project manager or a liason. This has the advantage of allowing the manager to prioritize the work being requested, but if such prioritization is done by simply ignoring the lowest stuff, the programmers don't know those low-priority problems exist, and they can slip through the cracks. | |
| Oct 26, 2011 at 21:14 | comment | added | Paul Wagland | +1 this is the definition that I would have added. Programming in a vacuum also implies, to me at least, that the programmer is wilfully ignoring any improvements from the field. | |
| Oct 25, 2011 at 15:44 | history | answered | KeithS | CC BY-SA 3.0 |