His methodology has a lot of planning. I'm in general, terrible at planning how long a program will take to be written. But there is one class of programs I a

His methodology has a lot of planning. I'm in general, terrible at planning how long a program will take to be written. But there is one class of programs I am pretty good at: very short, very simple, programs. Good news is that every problem you'll ever face can be broken down into sub-problems which are easier to solve. Bad news is planning a software project in that much detail, down to the granularity needed for me to get accurate time estimates, takes as long as actual doing the programming would. And even at that, there will still be many problems with the plan, because all that time we were not, say, making unit tests, or proto-types large enough to expose problems. But yet, here he is, and his methodology certainly worked for him. I wonder how much Forth itself contributed to that success, or could he have used any interpreted language. Any pointers on how to better estimate programming effort would be greatly appreciated.