When you're working on a file that was last updated six years ago
When you're working on a file that was last updated six years ago
I inherited code that contained files that were last updated in 1997
That isn’t a bad thing. On the contrary, according to the open-closed principle, you should strive for writing code you never have to touch again.
And that’s why so many core Linux utilities have worked almost exactly as they did from the very beginning. If your input and output demand no changes, the only improvements left to make are performance.
I haven't touched those files. The code works, I don't need to change it. I've mostly been working on the later additions.
Even if it was my code, after 6 years:
“Who the fuck wrote this garbage?! …..oh.”
I mean if it’s worked without modification for 6 years….
2019
don’t do this to me
I keep forgetting 2019 is not 1 year ago
Ah yes, the “fuck it, no-one is going to use this” code.
I've written semi-personal tools that other team members sometimes use that will break in 2100. The comments note this and really hope they aren't still using these by then
Or the “too critical and poorly documented so nobody dares change it” code. Good Luck!
I get to say that I've truly made it as a programmer. The reason is that I wrote around 75 lines of Rust, came back a year later, and I could see exactly how it works.
In case you're wondering, it's a command line Slack client for sending notifications. Colored highlights and everything.
“Lmao, who runs mathematically optimized assembly? Let’s get this objective-c rewrite going.”
One title would have been enough.
When you're working on a file that was last updated six years ago
Is that...The 7th Guest?
