Wed 13 Feb 2019
@MQRY and on-the-fly data retrieval
Mon 11 Feb 2019
Thu 7 Feb 2019
Could working with rich text really be RESTful?
The very opposite of YAGNI - more like IYBITWCE
Wed 20 Aug 2014, 12:14 PMTweet
by Ben Langhinrichs
Copyright © 2014 Genii Software Ltd.
What has been said:
1097.1. Doug Finner (08/20/2014 06:59 PM)
Keep in mind the whole 'vision' thing. There are lots of folks who have ideas for useful tools that turn out to have little value (and probably the reason YAGNI was invented). There is a subset of the development community who have a very good understanding of what businesses actually do and the kinds of tools that add real value. I'd suggest that you fall into that second category and your decision to work on these concepts was grounded in a deep understanding of how to make systems work better.
1097.2. Ben Langhinrichs (08/20/2014 07:14 PM)
Thanks, Doug. I appreciate your kind words. (And I certainly like that interpretation more than my simply being so damn stubborn that once I've built something I won't rest until I find some use for it, which is another alternative.)
1097.3. Andrew Magerman (08/21/2014 05:14 AM)
I'd agree with Doug. YAGNI is not arguing against product development nor making estimate's of customer's needs. I see it more as an effort to fight the anti-pattern of having too many layers of abstraction - i.e. fighting the urge to change a practical solution to a more general one, which introduces too many abstractions. Take WAS for instance: it's massively configurable, but the added complexity is of the same order of magnitude as that which it tries to simplify --> waste of time.
1097.4. Ben Langhinrichs (08/21/2014 06:07 AM)
Andrew - That's a helpful perspective, actually. I've spent a lot of years in my own company (in more ways than one), and don't always understand completely what the trends are out there. The WAS example helps a lot.