521
submitted 11 months ago by [email protected] to c/[email protected]
you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 114 points 11 months ago

You seem to like the lines-of-code metric. There are many lines of GNU code in a typical Linux distribution. You seem to suggest that (more LOC) == (more important). However, I submit to you that raw LOC numbers do not directly correlate with importance. I would suggest that clock cycles spent on code is a better metric. For example, if my system spends 90% of its time executing XFree86 code, XFree86 is probably the single most important collection of code on my system. Even if I loaded ten times as many lines of useless bloatware on my system and I never excuted that bloatware, it certainly isn't more important code than XFree86. Obviously, this metric isn't perfect either, but LOC really, really sucks. Please refrain from using it ever again in supporting any argument.

[-] [email protected] 66 points 11 months ago

Can confirm it's a shitty metric. I once saved the company I was working at few millions by changing one line of code. And it took 3 days to find it. And it was only 3 characters changed.

[-] [email protected] 27 points 11 months ago

That's the curse and blessing of our profession: efficiency of work is almost impossible to measure once you go beyond very simple code.

You can feel like a hero for changing three characters and finally fixing that nasty, or you can feel like an absolute disgrace for needing days to find such a simple fix. Your manager employs the same duality of judgement

[-] [email protected] 15 points 11 months ago

I feel like a hero in this particular case, it was a bug in a code that was written when I was still too young to even read. And no one knew how to run it. We didn't have access to the pipelines so no one knew how to build it and how to run it. It was a very obscure hybrid of C and PHP. I basically had to be the compiler, I went line by line through the whole codebase, searching for the code path that caused the error. Sounds easy enough, right? Just CTRL+click in your IDE. Wouldn't it be a shame if someone decided that function names should be constructed as a string using at least 20 levels of nesting where each layer adda something to the function name and then it's finally called. TL;DR it was a very shitty code.

[-] [email protected] 9 points 11 months ago

What the fuck. I'm so appalled I had to leave this useless comment to digitally stare with an agape mouth.

[-] [email protected] 5 points 11 months ago

To be fair, they said I'll be dealing with legacy code from time to time during the interview.

[-] [email protected] 14 points 11 months ago

But did you add 3 characters? Gotta bump up that code count bruh.

[-] [email protected] 13 points 11 months ago

Nope, removed 3, added 1.

[-] [email protected] 20 points 11 months ago

I wrote a program that does nothing but busy loop on all cores. stylist_trend/Linux is my favourite OS.

[-] [email protected] 8 points 11 months ago

i’m partial to the more relaxing sleep(500)/linux os, but to each their own

[-] [email protected] 4 points 11 months ago

Any good sleep will give back control to other threads.

[-] [email protected] 8 points 11 months ago

that’s why sleep(500)/linux uses bad sleep

[-] [email protected] 11 points 11 months ago

Then this: :(){ :|:& };: is most important code in existence.

[-] [email protected] 14 points 11 months ago

What you refer to as Linux, is actually called Forkbomb/Linux, or as I've recently taken to calli-[Process Killed]

[-] [email protected] 3 points 11 months ago

No, he doesn't. He suggests that there are Linux systems with no GNU code, like one I'm replying from, and whether "no" meant "no SLOC" or "no instructions spent executing" or "no packages" absolutely doesn't matter.

this post was submitted on 14 Aug 2023
521 points (95.8% liked)

linuxmemes

19849 readers
714 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS