Timeline for Documentation degrading - how to deal with it?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 24, 2012 at 0:12 | comment | added | gnat | if I keep "motivations behind design decisions for parts of API", in the code / comments, my source files will explode. Instead, I track these in much details in issue tracker and only refer to respective ticket in code comments | |
| Jul 23, 2012 at 21:08 | comment | added | parsifal | @jimmy: while you can't write a useful unit test for GUI layout, you can certainly test actions and invocation of back-end logic | |
| Jul 23, 2012 at 20:56 | comment | added | k.m | +1: Decent advises overall, but unfortunately you can't cover all your "code related issues" with unit tests (UI dev being prime example). Wish it was so though! | |
| Jul 23, 2012 at 20:44 | comment | added | lurkerbelow | +1, I do think that documentation, which rapidly changes, should be extracted from source code. It's less painful for the developer. | |
| Jul 23, 2012 at 20:33 | history | answered | parsifal | CC BY-SA 3.0 |