Have a good day.
99 little bugs in the code
Take one down, patch it around
… 149 little bugs in the code.
Oh well, just mark them as work on in the next release. Then shove them to the bottom of the pile when marketing wants you to work on ten new features instead.
It’s a FOSS project, so wish me luck, as you can now get it in the mail eventually.
I had to run a makepkg today, which now includes my self-written pieces of code in master. So I’m eating my own dog food now, and it’s good. Also, the itch from before has somehow relieved.
If “all bugs” was like 50 or so, that’s pretty good. Well done!
Bugs that have existed for +3 years in a component and are nearly immediately visible to the end user. Oldest source line I touched was from before 2010.
If you fix a bug, the number of bugs in the world remains the same.
- Batman
Hey, I still need to pay my bills next month. Better also put in some speed-up loops while you are putting in the bugs.
I love when I make a small code change and then I make my PR, CI runs and some piece of code entirely unrelated fails and it’s now my job to work out how these two unrelated things are related.
Mentor of mine used to say
Developers, fix their heads, they lose their asses. Fix their asses they lose their heads.
This is why tests and the Beyonce-rule exist, friends.
Beyonce rule?
If you liked it, you should’ve put a test on it.
Basically, any attribute of the code in question that matters to you should be under an automated test verifying the attribute.
It comes from Google. You can read more here: https://abseil.io/resources/swe-book/html/ch11.html
deleted by creator
