this post was submitted on 08 Oct 2023
1061 points (96.7% liked)

Programmer Humor

25620 readers
769 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
1061
The temptation is always there (lemmy.world)
submitted 2 years ago by Sgt_choke_n_stroke@lemmy.world to c/programmer_humor@programming.dev
74 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] idunnololz@lemmy.world 84 points 2 years ago (7 children)

Just create a global object and stuff your variable in there. Now you have a global singleton and that's not a purely bad practice :D

[–] Techmaster@lemm.ee 47 points 2 years ago

Just call it "state management" and nobody will even care.

[–] Anonymousllama@lemmy.world 21 points 2 years ago (1 children)

Important to contain all your mess to one side of the room, makes it easier to manage

[–] shotgun_crab@lemmy.world 2 points 2 years ago

Yeah yeah let's put all the eggs in one basket

[–] mdk_@lemmy.world 13 points 2 years ago

So you saying, just the tip?

[–] xmunk@sh.itjust.works 8 points 2 years ago* (last edited 2 years ago) (2 children)

Real enterprise programmers know that everything should be on the stack... so they declare a List《void*》 in main.

[–] manapropos@lemmy.basedcount.com 7 points 2 years ago

Real enterprise programmers know you can get another job in the next year or two so fuck best practice

[–] idunnololz@lemmy.world 7 points 2 years ago

But we might need to add more features in the future so it might not just be a list in a few years. Better encapsulate it in a few layers of abstractions just to be safe.

[–] magic_lobster_party@kbin.social 3 points 2 years ago (1 children)

Not necessarily a bad practice if the singleton is immutable, and it’s provided via dependency injection for example.

[–] wreckedcarzz@lemmy.world 0 points 2 years ago (1 children)

As a hobby coder: "mmmhm, mmmm, mmhm... I know some of these words!"

[–] SkyNTP@lemmy.ml 1 points 2 years ago* (last edited 2 years ago)

Software dev is full of obscure keywords that describe otherwise pretty simple or basic concepts you stumble upon in practice naturally and that you probably already understand.

  • singleton: a class/object that is designed to be single use, i.e. only ever instantiated with a single instance. Typically used when you use class/objects more for flow control or to represent the state of the program itself, rather than using it to represent data
  • immutable: read-only, i.e. unchangeable
  • dependency injection: basically when you pass a function or object into another function object, thereby extending their effective functionality, typically for modular code and to separate concerns.

Here's one more of my favourite examples of such a keyword: memoization

[–] z3rOR0ne@lemmy.ml 2 points 2 years ago

Ah yes. Global Objects, AKA the thinnest of condoms, lol.