This is essentially bottom-up programming where you build a small language first (could be just functions, not a "real" new language), then build your app out o

This is essentially bottom-up programming where you build a small language first (could be just functions, not a "real" new language), then build your app out of your new language. Paul Graham advocates/advocated this. Being able to figure out what primitive pieces are important now and will be important later is something that takes practice and something that I've never ever been able to convince a manager of the importance of and that it's far more important than knowing 25 design patterns or some similar buzzwordy stuff. There are many ways to decompose problems. Bottom-up is the right way, though. Contrast with top-down/stepwise refinement for the wrong way.