On trivial changes
Intended audience |
|
Origin | General software engineering experience. |
Mood | Amused. |
One day, perhaps three years into my career, I had a very small, one-line code change to make. I don’t remember exactly what it was, but I think it involved computing a value and interpolating it into a string. I considered committing it directly, but submitted it for code review despite how small of a change it was.
My reviewers pointed out three different bugs, which makes it perhaps the buggiest commit I’ve ever written (by density of bugs per lines of code). Since that day, I always submit code for review and I always wait for builds and tests to finish, even for changes which “obviously” don’t affect anything.
Related posts
The following are hand-curated posts which you might find interesting.
Date | Title | |
---|---|---|
24 Aug 2023 | Writing brittle code | |
01 Sep 2023 | (this post) | On trivial changes |
30 Dec 2023 | Testing terminal user interface apps |
Want to see more of my posts? Follow me on Twitter or subscribe via RSS.