Diving into someone else's code is always gonna make me cringe I guess.
@tiesselune
Sartre was mistaken.
Hell isn't other people.
Hell is other people's code.
@starbreaker It is! The project I'm working on has a script which is called "Script.cs". And a lot of comments stating "// STD"; I'm starting to guess it's an image to say "Sorry, crappy code, this is gonna spread like crabs"
@tiesselune As somebody who does C# at his day job, I apologize on behalf of my "colleagues".
@starbreaker I don't think you need to apologize. It's actually a cool ego boost when you find out that other developers let that kind of thing happen.
@tiesselune I tend to see it as, "Oh, great. Here's more fucking technical debt that I need to pay off because the original developer didn't know what they were doing or didn't give a shit."
@starbreaker I know the feeling. When I first discovered the project, I ran on windows but never displayed a frame on Xbox, crashing instantly. I discovered it came from the intensive use of a folder named "Resources" throughout the code for loading 90% of the assets of the game. Guess what the documentations says about that folder:
@tiesselune I once had to "refactor" an ASP.NET web app for a government client where every variable was global and everything was done in the pages' code-behinds. The original developers were writing C# as if it were fucking COBOL.
I went back and told my bosses to give me the original requirements documents because that app didn't need to be refactored. It needed the Ellen Ripley treatment.
@starbreaker Ahahah yes sometimes it's actually easier to re-do everything than to maintain bad freaking code.
Well, I'm maintaining a 3-year old project, coded by 2/3 people in total, two for the menus and one for the rest, and when they handed it to me I was like "great, where's the repo for the project?" with big naive eyes. Well, I'll let you know it had been three years of copying and pasting files around and suffixing stuff with "-old"
