(This philosophical post provoked by discussion in another thread where we talking about cases of implementing wrappers and layers of composition.) To achieve more you shall do more. Usual truth thing in daily life. Not so true for programming. It actually 'do less to achieve more'. Because it's non-linear in programming. Because each line of code you add to the system is increasing it complexity accordingly. And that means more effort for future maintenance for you, or for some other unsuspecting victim. So, that's why i always look how to do less, reduce the amount of code, to achieve something. But not just plainly implement yet another feature, so its done. -- Best regards, Igor Stasenko.
Igor Stasenko wrote
(This philosophical post provoked by discussion in another thread where we talking about cases of implementing wrappers and layers of composition.)
To achieve more you shall do more. Usual truth thing in daily life. Not so true for programming. It actually 'do less to achieve more'. Because it's non-linear in programming. Because each line of code you add to the system is increasing it complexity accordingly. And that means more effort for future maintenance for you, or for some other unsuspecting victim. So, that's why i always look how to do less, reduce the amount of code, to achieve something. But not just plainly implement yet another feature, so its done.
Nice! I'll add one, inspired by orbital mechanics and unlocking car doors in the rain. To go faster, slow down. A slightly slower, more deliberate pace will yield greater results than rushing headlong into something.
-- Best regards, Igor Stasenko.
-- View this message in context: http://forum.world.st/Philosophy-here-tp4888073p4888456.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
participants (2)
-
Igor Stasenko -
Richard Sargent