strategic programming term
investing in design quality even when tactical fixes would ship sooner
Approach where you spend a bit more time per change to leave the system better than you found it — refactor the surrounding code, fix the design flaw, write the comment. Slower per ticket but compounds: 6 months in, the strategic programmer's codebase is far easier to work in. Opposite of tactical tornado.