3 ms·
I think such conservative approach can be justified when working on existing code, which has been somewhat proven to work. But I don't think it's justified when
by js8 10y ago
I think such conservative approach can be justified when working on existing code, which has been somewhat proven to work. But I don't think it's justified when you're building the code.
I simply don't think you can always get the good abstraction right. But if you don't attempt it, you will never get it right. What you're advocating is not attempting it.
- ktRolster 10y agoIf it's new code, and you are unsure what abstraction is needed, build the simplest abstraction possible. YAGNI That way, as the code develops, and it becomes more clear what is needed, then you can easily build it at that time. If you have code that needs to be duplicated, throw it into a function, a lightweight and powerful abstraction.
- js8 10y agoThat's what I am advocating in this thread. ;-)