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.
76 0 ReplyThat's 3 bits, from 00110011 to 00110100. Can anyone top that?
56 0 ReplyI've changed 0 bits of the kernel
91 0 Reply
Still asking myself what that four year old girl who contributed to the kernel is doing today. Hopefully she goes into IT somewhere, she'd have a killer résumé.
64 0 Reply14 year old with 10yoe of contributing to the Linux kernel is exactly the current IT market is looking for
5 0 Reply
Actual code!? Most of us have to settle for fixing a grammatical error in the documentation
45 0 ReplyYeah, I also do that sometimes, but it doesn't feel as good to be honest...
1 0 Reply
🥳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 ☺️💕
24 0 ReplyI 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.
23 0 Reply"What if I just change this a bit..."
segmentation fault
"Nope, nope, let's put that mystery code back..."
31 0 ReplyDo not touch The Coconut!
13 0 Reply
These days id prefer a developer produce negative lines of code without breaking anything.
17 0 ReplyAs 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.
18 0 ReplyI want to roll back my commits, not make more!
5 0 ReplyI 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.
2 0 ReplyWasn't there a kernel release a few years back that actually resulted in less code? Or at least at some huge part?
2 0 Reply
How I feel like after contributing
8 0 Reply