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.
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.
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.
It’s refreshing to see someone on social media who doesn’t dismiss code as “outdated” just because of its age.
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.
Shouldn’t you write tests for your code before using the new language features though?
😬
Don’t worry, it’s probably fine, as long as you have a good grasp of the new feature. Right?
Erm, yes? Been programing for 15 years, I think I know my way around. 😅