Timeline for Are there any easy-to-follow/reliable methods for simplifying code?

4 events

when toggle format	what		by	license	comment
Mar 10, 2015 at 11:41	audit	Low quality posts
Mar 10, 2015 at 11:42
Feb 10, 2015 at 21:12	comment	added	supercat		...other needs which could be satisfied if the library's internals were available and documented, and cannot be efficiently satisfied otherwise. Keeping the internals hidden retains for the library author the ability to change the information later, but at the expense of possibly limiting what consumers of the class will be able to do with it. The class author isn't just deciding for himself that certain things won't be needing--he's deciding for everyone else that nobody is going to need it (or if they do need it, they won't get it).
Feb 10, 2015 at 21:09	comment	added	supercat		It's important to separate YAGNI from what I'd call "NIGNI". The idea behind YAGNI is that one shouldn't do something now to fill a possible future need if one could just as well do it when the need actually arrises. NIGNI ("no one is going to need it") is what one effectively says [or hopes] if one declines to include something which may later be needed but which cannot be done later. NIGNI comes up when deciding on the `public` and `protected` members a library should expose; the fact that an author might find the library's own API adequate doesn't mean that consumers won't have...
Feb 10, 2015 at 7:32	history	answered	200_success	CC BY-SA 3.0