> Identify which of the files should be modified first.<p>I'm curious how many software engineers work this way — i.e. you need to make a big change, and you can determine a sequential order in which to make changes?<p>My working style is mostly jumping back-and-forth across all the relevant files and tests as I go, realizing new things that I need to change, and iterating until it all works end-to-end.<p>Am I the outlier, or is Maiao's expected workflow the outlier?