Every big change is ultimately just a series of small changes. It takes skill and engineering chops to be able to break up big ideas into small steps with quick feedback loops, but it can be done. Usually worth the effort too.
Not every big change is necessarily something you can meaningfully break up into small changes. Sometimes when you could break it up into small changes, you have to change its structure in a meaningful way to half-implement it and test out that half-version. It takes experience to know when it’s best to get the whole structure expressed it code, then to go back and tweak it based on any compiler errors. Most of the time the compiler errors are very minor things like a typo, so you don’t lose any meaningful time fixing them.
Every big change is ultimately just a series of small changes. It takes skill and engineering chops to be able to break up big ideas into small steps with quick feedback loops, but it can be done. Usually worth the effort too.
Not every big change is necessarily something you can meaningfully break up into small changes. Sometimes when you could break it up into small changes, you have to change its structure in a meaningful way to half-implement it and test out that half-version. It takes experience to know when it’s best to get the whole structure expressed it code, then to go back and tweak it based on any compiler errors. Most of the time the compiler errors are very minor things like a typo, so you don’t lose any meaningful time fixing them.