Linux

48622 readers

1667 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

162

Are there any things in Linux that need to be started over from scratch? (lemmy.ca)

submitted 8 months ago by [email protected] to c/[email protected]

268 comments fedilink hide all child comments

I'm curious how software can be created and evolve over time. I'm afraid that at some point, we'll realize there are issues with the software we're using that can only be remedied by massive changes or a complete rewrite.

Are there any instances of this happening? Where something is designed with a flaw that doesn't get realized until much later, necessitating scrapping the whole thing and starting from scratch?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 15 points 8 months ago (1 children)

Yeah, this was something I recognized about myself in the first few years out of school. My brain always wanted to say "all of this is a mess, let's just delete it all and start from scratch" as though that was some kind of bold/smart move.

But I now understand that it's the mark of a talented engineer to see where we are as point A, where we want to be as point B, and be able to navigate from A to B before some deadline (and maybe you have points/deadlines C, D, E, etc.). The person who has that vision is who you want in charge.

Chesterton's Fence is the relevant analogy: "you should never destroy a fence until you understand why it's there in the first place."

[–] [email protected] 3 points 8 months ago (1 children)

I'd counter that with monolithic, legacy apps without any testing trying to refactor can be a real pain.

I much prefer starting from scratch, while trying to avoid past mistakes and still maintaining the old app until new up is ready. Then management starts managing and new app becomes old app. Rinse and repeat.

[–] [email protected] 5 points 8 months ago (2 children)

I made a thing.

The difference between the idiot and the expert, is the expert knows why the fences are there, and can do the rewrite without having to relearn lessons. But if you're supporting a package you didn't originally write, a rewrite is much harder.

[–] [email protected] 5 points 8 months ago (1 children)

Which is something I always try to explain to juniors: writing code is cool, but for your sake learn how to READ code.

Not just understanding what it does, but what was it all meant to do. Even reading your own code is a skill that needs some focus.

Side note: I hate it to my core when people copy code mindlessly. Sometimes it's not even a bug, or a performance issue, but something utterly stupid and much harder to read. But because they didn't understand it, and didn't even try, they just copy-pasted it and went on. Ugh.

[–] [email protected] 1 points 8 months ago

Side note: I hate it to my core when people copy code mindlessly

Get ready for the world of AI code assist 😬

[–] [email protected] 1 points 8 months ago (1 children)

https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/

[–] [email protected] 1 points 8 months ago

Hah yeah, this was in the back of my mind. I forgot the context of it, though, thanks.