2 ms·
As someone who does this with a lot of programs I've written, I'll say that avoiding abstractions is just as important as distractions --- if doing the simplest
by userbinator 8y ago
As someone who does this with a lot of programs I've written, I'll say that avoiding abstractions is just as important as distractions --- if doing the simplest of tasks takes half a dozen layers of abstraction and indirection, it makes it all the more difficult to see the whole program at once. "Too many moving pieces makes it hard to see what's going on", as the saying goes.
The amount of "fluff" introduced by "modern" languages and their culture, like Java and C#, is certainly an obstacle to this; it seems like they encourage overcomplexity and the creation of huge complex software, so that all programs written in them naturally take on that style, no matter how trivial they actually should/need to be.
- kungtotte 8y agoThe languages themselves sort of forces people's hands depending on how rigid they are and how easy it is to change your mind afterwards. Take Python for example. Firstly they have a culture of "we're all adults here" and don't really bother with public/private distinctions in classes, and secondly the language makes it easy to turn a variable into a property with the @property decorator. I'm not that familiar with Java or C#, but I guess turning a variable into a property after the fact is non-trivial. In Python all the calling code remains unchanged (`val = object.field`)