Timeline for Should a developer be forced to memorize details?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2011 at 14:18 | comment | added | Thomas Owens♦ | I wouldn't expect you to know everything, but I would expect that anyone working on a particular subsystem would know that subsystem inside and out. I would consider that knowledge caring about your work. | |
| Jun 11, 2011 at 13:56 | comment | added | edA-qa mort-ora-y | I strongly disagree with remembering details. You should remember concepts and functions. That is, know what your system can do, and know how to find out what the exact method/variable/column name is. | |
| Jun 11, 2011 at 12:39 | history | edited | Thomas Owens♦ | CC BY-SA 3.0 | added 69 characters in body |
| Jun 11, 2011 at 12:33 | history | answered | Thomas Owens♦ | CC BY-SA 3.0 |