Telescope Rule (2008)
wiki.c2.com
wiki.c2.com
When I started in IT I would frequently run projects over my head and then have to do a lot of backtracking wasting time.
Now, whenever I need to do something I don't know exactly how to, I first run a bunch of test projects to learn the ropes on small and manageable examples and only then attempt the large project.
I like to think that in almost all cases doing the small example projects and the project take less time than if I started with the large project right away. The only complaint is that managers do not always see it this way and they want to see constant progress.
(Prolog is so much more "compiler-shaped" than imperative languages and so simple itself that it's much easier to use it to write compilers. In fact the last chapter of "Art of Prolog" is about writing compilers.)
(This is a joke about prolog error handling)
(In practice the issue can be overcome by making a meta-interpreter that does tracing or error reporting or whatever. It's standard Prolog idiom, "in the book". See also: https://www.metalevel.at/prolog/debugging )
I haven't followed this rule, starting small and easy, and my first mirror took me 19 months. The second of similar difficulty took about 2 months. Looking back, I find it strange to have taken such a difficult first one, because I do start small and build upon small steps in software.
Also, Brooks reminds us to plan to throw one away since you will anyway.