this post was submitted on 08 Oct 2023
1078 points (96.6% liked)

Programmer Humor

18970 readers
521 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 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 87 points 10 months 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

[–] [email protected] 48 points 10 months ago

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

[–] [email protected] 40 points 10 months ago (1 children)

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

[–] [email protected] 38 points 10 months ago (1 children)

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

[–] [email protected] 37 points 10 months ago* (last edited 10 months ago) (1 children)

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

[–] [email protected] 7 points 10 months ago

Ahh yes memoization, the complicated way to say "remember this, I might need it again"

[–] [email protected] 22 points 10 months ago (1 children)

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

[–] [email protected] 2 points 10 months ago

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

[–] [email protected] 13 points 10 months ago

So you saying, just the tip?

[–] xmunk 10 points 10 months ago* (last edited 10 months ago) (2 children)

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

[–] [email protected] 8 points 10 months 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.

load more comments (1 replies)
[–] [email protected] 2 points 10 months ago

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