| Essay 32 | Develop a Programming Cadence |
So, how do we manage anticipating too early to change vs. reacting too late to change?
Consider software development like we’re driving a stick shift. As we start, we’re in first gear: coding away at a steady pace. The more we code, the less efficient we become. At some point, we have to shift up a gear.
Shifting up a gear, in programming terms, is cleaning up our code: taking a step back to refactor, abstract, or implement a pattern. It means taking the time to consider how to change our habits at a particular point in the development process. Doing this does not mean we’ve made a mistake. It’s natural and necessary.
We have to shift in code just as we have to when we’re driving. Still, if we do ...
Get The Developer's Code now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
