Its definitely a bad idea writing new code that builds up on your old code, that has not been tested properly, because you quickly have to start debugging multiple layer is code at once.

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

[–] bleistift2@sopuli.xyz 10 points 1 day ago (6 children)

Opposing opinion: If it’s legacy code, and no-one has found a bug yet, it works as intended.

No, I don’t mean that ironically.

[–] who@feddit.org 8 points 1 day ago* (last edited 1 day ago) (5 children)

It's refreshing to see someone on social media who doesn't dismiss code as "outdated" just because of its age.

[–] Lemminary@lemmy.world 2 points 1 day ago (4 children)

There are dozens of us! But also, I have a masochistic tendency to update my old code to use the new language features and make it somewhat readable.

[–] yetAnotherUser@lemmy.ca 2 points 17 hours ago (1 children)

Shouldn't you write tests for your code before using the new language features though?

[–] Lemminary@lemmy.world 2 points 16 hours ago (1 children)

😬

[–] yetAnotherUser@lemmy.ca 1 points 14 hours ago (1 children)

Don't worry, it's probably fine, as long as you have a good grasp of the new feature. Right?

[–] Lemminary@lemmy.world 1 points 13 hours ago

Erm, yes? Been programing for 15 years, I think I know my way around. 😅

load more comments (2 replies)