Re:Applying the Unix Philosophy to Object-Oriented Design
by wting on Wednesday November 28, 2012 @01:47PM
(#4844009)
Your argument taken to the extreme leads to code golf.
Sure abstraction is worth it. You get code reusability, better unit testing, and faster understanding of the code.
Maybe a small script doesn't need it, but once something starts growing past a few hundred lines you're better off.
Re:Applying the Unix Philosophy to Object-Oriented Design
by comex on Wednesday November 28, 2012 @02:48PM
(#4844299)
Nobody suggested taking his argument to the extreme.
A larger script might indeed need it, but knowing when you need abstraction and when you don't is key. In this case, YAGNI.
Re:Applying the Unix Philosophy to Object-Oriented Design
by mercurial on Wednesday November 28, 2012 @02:30PM
(#4844201)
It's worth it for most things you'll end up maintaining. How many of these "one-shot" scripts have stayed and grown to full-size systems, preferably by keeping the same hastily thrown together structure over the years?
The "mental" abstraction is nice to have, but when you end up typing more characters, it's just counterproductive.
Once you start repeating yourself, then it makes sense. To do it from the start is overengineering—"you ain't gonna need it".