Chuck Moore, inventor of Forth, is also an advocate of bottom-up development.
> You mentioned that a lot of Forth programs you’ve seen look like C programs. How do you design a better Forth program?
> Chuck: Bottom-up.
> First, you presumably have some I/O signals that you have to generate, so you generate them. Then you write some code that controls the generation of those signals. Then you work your way up until finally you have the highest-level word, and you call it go and you type go and everything happens.
> I have very little faith in systems analysts who work top-down. They decide what the problem is and then they factor it in such a way that it can be very difficult to implement.
> You mentioned that a lot of Forth programs you’ve seen look like C programs. How do you design a better Forth program?
> Chuck: Bottom-up.
> First, you presumably have some I/O signals that you have to generate, so you generate them. Then you write some code that controls the generation of those signals. Then you work your way up until finally you have the highest-level word, and you call it go and you type go and everything happens.
> I have very little faith in systems analysts who work top-down. They decide what the problem is and then they factor it in such a way that it can be very difficult to implement.
https://www.oreilly.com/library/view/masterminds-of-programm...