I 100% fully agree. the best pattern is to write and test small parts together. I think that unit testing really clears up a bunch of junk by hard defining the inputs and outputs - ex "on x input, do y". without that guidance I think it's easy for a developer to kind of lose track of the goal.