400
Shit, it's how I feel after contributing 1 line of code to fastfetch (sh.itjust.works)
submitted 3 months ago by 0x4E4F@sh.itjust.works to c/linuxmemes@lemmy.world
27 comments fedilink hide all child comments
all 29 comments
sorted by: hot top controversial new old
[-] homura1650@lemm.ee 76 points 3 months ago

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.

[-] bjoern_tantau@swg-empire.de 56 points 3 months ago

That's 3 bits, from 00110011 to 00110100. Can anyone top that?

[-] Wilzax@lemmy.world 91 points 3 months ago

I've changed 0 bits of the kernel

[-] trashgirlfriend@lemmy.world 38 points 3 months ago

Someone needs to hit us with "I convinced someone to not contribute to the kernel"

[-] cactusupyourbutt@lemmy.world 25 points 3 months ago

Linus does this well enough on his own, he doesnt need help

[-] Kyouki@lemmy.world 6 points 3 months ago

Myself, because I'm stupid with coding.

[-] SaharaMaleikuhm@feddit.org 9 points 3 months ago

If you revert a change that's negative bits. You can do it!

[-] bjoern_tantau@swg-empire.de 64 points 3 months ago

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é.

[-] spread@programming.dev 5 points 3 months ago* (last edited 3 months ago)

14 year old with 10yoe of contributing to the Linux kernel is exactly the current IT market is looking for

[-] ImplyingImplications@lemmy.ca 45 points 3 months ago

Actual code!? Most of us have to settle for fixing a grammatical error in the documentation

[-] 0x4E4F@sh.itjust.works 1 points 3 months ago

Yeah, I also do that sometimes, but it doesn't feel as good to be honest...

[-] Petter1@lemm.ee 24 points 3 months ago* (last edited 3 months ago)

🥳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 ☺️💕

[-] henfredemars@infosec.pub 23 points 3 months ago

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.

[-] TimeSquirrel@kbin.melroy.org 31 points 3 months ago

"What if I just change this a bit..."

segmentation fault

"Nope, nope, let's put that mystery code back..."

[-] rtxn@lemmy.world 13 points 3 months ago

Do not touch The Coconut!

[-] foggy@lemmy.world 17 points 3 months ago

These days id prefer a developer produce negative lines of code without breaking anything.

[-] elvith@feddit.org 18 points 3 months ago

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.

[-] Skullgrid@lemmy.world 5 points 3 months ago

I want to roll back my commits, not make more!

[-] h0bbl3s@lemmy.world 2 points 3 months ago

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.

[-] bjoern_tantau@swg-empire.de 2 points 3 months ago

Wasn't there a kernel release a few years back that actually resulted in less code? Or at least at some huge part?

[-] ICastFist@programming.dev 8 points 3 months ago

How I feel like after contributing

this post was submitted on 29 Jul 2024
400 points (99.5% liked)

linuxmemes

21251 readers
1425 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world