2 ms·

This is a good read, I liked the philosophy behind Do not put code in your program that might be used. Do not leave hooks on which you can hang extensions. The

• tjoff 4y ago
  >The things you might want to do are infinite; that means that each one has 0 probability of realization. That does not follow. >If you need an extension later, you can code it later - and probably do a better job than if you did it now. Not if it requires intimate knowledge of the internals. Then you'll need weeks just to get reacquainted and then you might still not know enough to do a good job of it. Just today I was implementing a feature that I chose not to do initially. Now I was burdened with an incomplete view of the system and also had to deal with a lot of other code that was written in a certain way because the feature didn't exist at the time. I'm sure it would have been better if I had done it in the beginning. I agree with the sentiment, but disagree with the arguments. In the end it is a judgement call as any.
  • justincormack 4y ago
    Of course, and it only works well in certain situations, like you do have a complete view of a Forth system because it is small and you write it yourself, and it doesn't take weeks. I recommend reading it, just as a different point of view.