Not too long ago I was explaining to people how Garry is both an asshole and bad at coding… now we get to see the unprofessional struggle session.
Like, if you are frustrated that calling methods from your own code base doesn’t work… maybe fix your code’s utility functions?
Instead of doing one off hackjobs for everything?
Any serious, experienced coder has tendencies toward this or even versions of their code with some of this kind of stuff in it.
… but you fucking clean it up and rewrite the rage with actually helpful documentation, if you actually give a damn about other people who might use it.
Ah, yes I also work professionally, in very clean non-swear-inducing code without hackjobs that are in production and does a job, because it exists, and I know because I code a lot professionally and never see hacks or swear ever and it also reflects my flawless personality. In fact, here they are now, in the room with us. All the code that is perfect and without hacks are greeting us and they speak highly of me and badly about that unprofessional garry even though we don’t really know who he is we are definitely superior since our code is without any hacks and doesn’t use any libraries with swear words in the comments
I don’t see anything unprofessional there. Just naughty words. But, the naughty words are somewhere where they warn you that the code below doesn’t behave as expected, or complain because there isn’t a better way to do something. That seems like the best time to use strong language.
Cleaning it up is a great idea in theory, but in practice almost everybody has higher priority things to be doing. Leaving a comment in the code for why something is ugly is the best thing you can do when you don’t clean something up, so that someone coming along after you doesn’t struggle with it. We have no idea how many “naughty” comments are no longer there because the issues they addressed were cleaned up.
If you were to talk like this in any job I’ve ever worked at, you’d be fired in about a week, maybe faster.
Same with writing emails with this language.
And you’re missing my point that if you made your own functions… and they don’t work right, … you should fix those functions, rework them.
Not doing that is how you get technical debt, spaghetti code, which is bad for you, bad for what you’re trying to do, bad for anyone else trying to help you do it.
Commenting on a bunch of slapdash fixes is like covering holes you punched in your wall with framed graffitti about how frustrated you are.
If you saw that in a date’s home, you’d hopefully recognizr that as a red flag and nope the hell out.
If everybody else is too busy to actually fix the code, you have inept project management.
You as well have clearly never worked in an actual professional software dev environment, if you think this is reasonable or defensible.
I always tell our new developers: If your new feature works, you aren’t done, you have to check if your code has to be refined first, before checking it in. (e.g. duplicated passages made into a common function, ugly hacks removed and “done properly”, stuff like this)
Documentation and testing are also mandatory, but that’s because of the industry we work in.
You can avoid having to do something like a total refactor that takes half the year, if you do the rough equivalent of a sanity check / clean up pass, when any new system or feature set is added, and make that habitual.
Its… kinda like how if you just do a bit of regular shopping, regular meal prep, regularly do the dishes, whatever, everything just flows easier in general.
The longer you run lean, move fast and break things… yeah it can improve output in the short term, but medium to long term, you’ll run yourself ragged, and things will break and fall apart.
Typical Garry.
Yep.
Not too long ago I was explaining to people how Garry is both an asshole and bad at coding… now we get to see the unprofessional struggle session.
Like, if you are frustrated that calling methods from your own code base doesn’t work… maybe fix your code’s utility functions?
Instead of doing one off hackjobs for everything?
Any serious, experienced coder has tendencies toward this or even versions of their code with some of this kind of stuff in it.
… but you fucking clean it up and rewrite the rage with actually helpful documentation, if you actually give a damn about other people who might use it.
As the TF2 Sniper put it:
Professionals have standards.
Ah, yes I also work professionally, in very clean non-swear-inducing code without hackjobs that are in production and does a job, because it exists, and I know because I code a lot professionally and never see hacks or swear ever and it also reflects my flawless personality. In fact, here they are now, in the room with us. All the code that is perfect and without hacks are greeting us and they speak highly of me and badly about that unprofessional garry even though we don’t really know who he is we are definitely superior since our code is without any hacks and doesn’t use any libraries with swear words in the comments
I don’t see anything unprofessional there. Just naughty words. But, the naughty words are somewhere where they warn you that the code below doesn’t behave as expected, or complain because there isn’t a better way to do something. That seems like the best time to use strong language.
Cleaning it up is a great idea in theory, but in practice almost everybody has higher priority things to be doing. Leaving a comment in the code for why something is ugly is the best thing you can do when you don’t clean something up, so that someone coming along after you doesn’t struggle with it. We have no idea how many “naughty” comments are no longer there because the issues they addressed were cleaned up.
If you were to talk like this in any job I’ve ever worked at, you’d be fired in about a week, maybe faster.
Same with writing emails with this language.
And you’re missing my point that if you made your own functions… and they don’t work right, … you should fix those functions, rework them.
Not doing that is how you get technical debt, spaghetti code, which is bad for you, bad for what you’re trying to do, bad for anyone else trying to help you do it.
Commenting on a bunch of slapdash fixes is like covering holes you punched in your wall with framed graffitti about how frustrated you are.
If you saw that in a date’s home, you’d hopefully recognizr that as a red flag and nope the hell out.
If everybody else is too busy to actually fix the code, you have inept project management.
You as well have clearly never worked in an actual professional software dev environment, if you think this is reasonable or defensible.
Absolutely correct.
I always tell our new developers: If your new feature works, you aren’t done, you have to check if your code has to be refined first, before checking it in. (e.g. duplicated passages made into a common function, ugly hacks removed and “done properly”, stuff like this) Documentation and testing are also mandatory, but that’s because of the industry we work in.
Yep.
You can avoid having to do something like a total refactor that takes half the year, if you do the rough equivalent of a sanity check / clean up pass, when any new system or feature set is added, and make that habitual.
Its… kinda like how if you just do a bit of regular shopping, regular meal prep, regularly do the dishes, whatever, everything just flows easier in general.
The longer you run lean, move fast and break things… yeah it can improve output in the short term, but medium to long term, you’ll run yourself ragged, and things will break and fall apart.
Where the fuck are you coming up with the time to refactor all of your fucking frameworks?
But the trick is to keep the code good enough that it runs, but bad enough that you have job security
I wasn’t sure if Garry was commenting on his own code, or someone was calling Garry out on Garry’s code. Either way, your comment works.
Its likely a mix of Garry and maybe 2 to 4 other coders, who Garry assigns to develop various subsystems off of his broken core systems.
Thats exactly how he did it during Garry’s Mod.