shortcuts need a reason

moving quickly is useful when you know what you are trading away

i like shortcuts when they remove repetition. i get wary when they hide a decision i will need to understand later.

copying a pattern can be the right move. skipping input checks, source review, or a clear handoff usually creates work that returns in a less convenient shape. speed has to include the time spent recovering from mistakes, not just the time until the first result appears.

i want to know what a shortcut saves, what it risks, and how reversible it is. then i can choose it on purpose instead of treating fast as automatically better.

the best shortcuts preserve the parts of the work that need care.

← back to writing