Timeline for How necessary is it to follow defensive programming practices for code that will never be made publicly available?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 7, 2014 at 21:18 | history | suggested | samthebrand | CC BY-SA 3.0 | I edited the question. No double jeopardy to see here. |
| Mar 7, 2014 at 21:09 | review | Suggested edits | |||
| S Mar 7, 2014 at 21:18 | |||||
| Dec 9, 2013 at 13:28 | audit | First posts | |||
| Dec 10, 2013 at 5:11 | |||||
| Dec 4, 2013 at 21:08 | comment | added | Katie Kilian | "Efficiently" can mean many different things! In my experience, novices (not that I'm saying you are one) often overlook how efficiently they will be able to support the program. Code usually spends far longer in the support phase of its product life cycle than it does in the "writing new code" phase, so I think that is an efficiency that should be considered carefully. | |
| Dec 4, 2013 at 20:57 | comment | added | codebreaker | Good to know. In the past I used to just program as efficiently as I could, so I sometimes have a tough time getting used to ideas like this. I'm glad I was going in the right direction. | |
| Dec 4, 2013 at 20:54 | vote | accept | codebreaker | ||
| Dec 4, 2013 at 20:30 | history | answered | Michael K | CC BY-SA 3.0 |