1 line of code?
Amateur, I changed 1 byte of code in the Linux kernel!
It was random driver with something along the lines of “if (hardware_version > 3) fail()”.
One day we got a new shipment of hardware that wasn’t working for some reason until I upped that 3 to a 4.
Actual code!? Most of us have to settle for fixing a grammatical error in the documentation
Yeah, I also do that sometimes, but it doesn’t feel as good to be honest…
🥳I am mentioned in the kernel git (even if it is only for a found bug in driver about a specific wifi dongle that had wrong MAC address)
It really feels like that ☺️💕
I was thinking about trying to contribute, but the code I was fixing is filled with so many workarounds that I’m terrified of breaking one.
These days id prefer a developer produce negative lines of code without breaking anything.
As experience tells me, every program contains at least one bug.
Experience also tells me, that you can remove the buggy line of code and the program will still not work as intended.
From this follows, that every program can be reduced to a single line of code that doesn’t work as intended.
I want to roll back my commits, not make more!
I saw it put really well the other day. Any software has in general a set number of bugs per lines of code. Something like Debian the number of bugs goes down after release as only bugfixes occur, while anything constantly moving like a rolling release, is certain to grow in number of bugs as the less tested newer software (which generally includes more loc) is pushed. There are tradeoffs to both methods, and edge cases of course.
How I feel like after contributing
