TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Pros/Cons of the "drive by" code fix?

2 pointsby hlshipabout 1 year ago
A question for HN: I&#x27;m in the habit of making small changes, as I see them, in code - usually fixing documentation strings and comments, occasionally refactoring code or even adding missing tests.<p>These &quot;drive by&quot; fixes, as I call them, are often not related to why I&#x27;ve created a branch and PR on some codebase, they&#x27;re incidental.<p>I feel like if I tried to put them aside and address them later, they would never get fixed. The work of tracking them, checking out a fresh branch, making those changes, and getting them reviewed, merged, and released - outside of &quot;real work&quot; on the codebase - seems too difficult.<p>This applies to many open source projects I work on, as well as many of my current and past companies&#x27; internal code.<p>So is this a common habit? Is it something I should embrace, or something I should avoid?

no comments

no comments