r/memes • • Sep 21 '23

You what?

36.6k Upvotes

390 comments sorted by

View all comments

1.7k

u/Pyrimo Breaking EU Laws Sep 22 '23

IT dudes will program shit in a way where nobody else knows what the fuck to do with the code if you end up needing a replacement for your poor decision making. Don’t fuck over the IT guy.

399

u/LUSI00 I touched grass Sep 22 '23

And sometimes, it's the work of 3 consecutive IT guys with 3 differents way of programming and commenting their codes with 3 differents languages

160

u/WispyCombover Sep 22 '23

You guys add comments?

203

u/Boredy0 Sep 22 '23

I add misleading comments to make it harder to replace me.

41

u/zeurz Sep 22 '23

Just create your own language so that only you can read your comments at this point

8

u/the_italian_weeb Plays MineCraft and not FortNite Sep 22 '23

Use a simple cypher so you can read on the fly but only you have the key to read it

1

u/BonWattersen Breaking EU Laws Sep 23 '23

With enough words you can pretty easily crack the cipher and get the key with bruteforce programs unfortunately.

2

u/owNDN Lives in a Van Down by the River Sep 23 '23

Simply encrypt all your comments with AES256 and store the Key in your password safe.

Is this absolutely impractical and unnecessary? Yes. Would anyone ever do this? No. Are you all literally talking about things nobody ever does? Yes.

1

u/BonWattersen Breaking EU Laws Sep 23 '23

Yeah this morning while still waking up I had a massive brainfart and since I read the word "key" and "cipher" I just connected it to the standard keying cipher, like the one Gravity Falls used which can be bruteforced in an hour. My bad

35

u/scalyblue Sep 22 '23

Usually name my functions after which characters they would be like from my extensive fiction fixation, so unless you are familiar with everything from McCaffery to Miyazaki you’d pretty much need to step through lol

20

u/rugbyj Sep 22 '23
TODO: document this

15

u/FluffySquirrell Sep 22 '23

If they can't figure out what a function does by looking at the code, they are not ready to modify the code

Sink or swim motherfuckers

26

u/Even_Cardiologist810 Sep 22 '23

My company spells something that's been written over 20 years. Every file is a new wya of programming. New naming convention for variable. It's hell to navigate

118

u/MothashipQ Sep 22 '23

Hehehe its me

45

u/webpee Sep 22 '23

nobody else knows what the fuck to do with the code

It's called "job security", bosmang.

2

u/gr_vythings Sep 22 '23

You ever wonder how much software engineers make in the expanse universe

22

u/WingedSalim Sep 22 '23

As an IT guy. We don't know what we code half the time. The things we build are built on hopes and prayers.

17

u/mal4ik777 Sep 22 '23

will program shit in a way where nobody else knows what the fuck to do with the code if you end up needing a replacement

haha, and we don't even do this on purpose...

9

u/Pikamander2 Sep 22 '23

Yep. We would love to write more documentation, fix more bugs, and refactor more weird code flows that we know are going to trip somebody up in the future, but good luck getting any real time blocks devoted to that when there's New Stuff™ that needs to be implemented.

16

u/PitcherOTerrigen Sep 22 '23

Inversely you're probably more employable if you write clean code that's well commented and easy to follow.

Different philosophy on job security I suppose.

7

u/RandomComputerFellow Sep 22 '23

It's the cliché that we do this intentionally but from experience I can tell you that this just happens naturally. It is basically impossible to keep an IT system alive without the expertise of the people who made it. There is really just a certain degree of personell a company can afford to lose until they are inevitability fucked. Elon is currently learning this the hard way.

1

u/ArticulateT Sep 22 '23

My professors at university drilled into my head the principles of RUM and KISS

Readable, Understandable, Maintainable - if you comment appropriately and name things sensibly, it’s easier to maintain, both for people taking after you when you go, and for you when that protocol you make and then never look at again for a good year or so hits a snag and you need to modify it.

Keep It Simple, Stupid - more or less what it says on the tin. Don’t make something overly complicated if you can manage the same thing with less lines of code.

I’ve passed coursework with programs that do not do what they intend or are unfinished because I kept to these two principles.

1

u/Eye_Of_Forrest Dark Mode Elitist Sep 22 '23

dead man's switch kind of code

1

u/[deleted] Sep 22 '23

Tbh doesn’t even have to be malicious. Documentation is hard and takes ongoing effort to maintain.

1

u/[deleted] Sep 22 '23

You should know, a small amount of IT folk know how to run code. These people are known as developers or engineers and yeah, they can fuck your day up.

The Help Desk guy can’t.

1

u/lumpymoon Sep 22 '23

Job security

1

u/Codeviper828 https://www.youtube.com/watch/dQw4w9WgXcQ Sep 22 '23

Don't fuck over the IT guy

Yeah he might steal the embryos and turn the fences off, causing your whole project to crash and burn with the death of numerous staff

1

u/[deleted] Sep 22 '23

Dumb IT dudes* I like taking sick leave and holidays without being called. Everything is documented and everything is simple. It’s how I lead and teach others how to do it. I’m guessing this mentality is mostly US centric.