Skip Navigation

Programmer Humor @programming.dev

Rikudou_Sage @lemmings.world

4w ago

I'm not sure, but it might be something about UUIDs

41 comments

Semantic satiation. Or whatever it's called, i think ive officially lost it after reading this
- I read the code like half a dozen times and my brain hurts.
Is "main" a valid Java identifier?
UwUID
Where did i put that Spiderman x3 pointing meme?
I can see how this may be useful. My understanding is that this is go lang and the person created a wrapper type UUID and this function takes the go standard library uuid.UUID and returns the wrapped UUID.
The wrapped UUID could be useful as you can then define methods for it like toInt() or something to make it implement some ID interface you have set up. It's a common pattern in go to create a thin wrapper around an imported type so you can implement all the methods required for some interface you defined. It does make naming those thin wrappers hard because what are you supposed to name the struct that just contains a uuid?
- Yep, that person would be me and that's exactly what I was doing, just found it funny that there was so many uuids in the piece of code.
  Originally the function was named FromUuid but I couldn't resist renaming it to make it even better.
- Clearly, the answer is uuid.
When you get a new boss at Twitter who ranks people by lines of code written
UwUIDs
New Dutch programming language just dropped.
Why I love the Into trait in rust
If this was C:

#define uuID func #define uuiD return
- #define satan fubarx
Plot twist: it returns the bios serial.
Picture isn't loading for me?
- Thanks, kind stranger. And wow, I haven't seen that much UUID since I coded for Second Life.
- are you from the UK by any chance
  
  Yes
Not exactly the same, but this reminded me of the MuffinMail.MuffinHash.MuffinHash talk: https://www.youtube.com/watch?v=o9pEzgHorH0
- A colleague wrote Java style Python. SomethingDispatcher().dispatch() all the way. It's a mess. Poor guy was thrown into the deep end and left alone for a year. I don't blame him for the outcome.
  Meanwhile, functools.partial is one of my favorite tools. I wrote a whole SCADA system in which the initialization just builds data pathways using functools.partial so that incoming event callbacks can be handled with all necessary resources already in scope. Any missing data is made apparent at init, not at event time. It's fast and stable (and I'm pretty proud of it lol).
i've now read UUID so many times i'm starting to think it's some kind of sex disease
- That must one awkward conversation... "Can you explain where did you get the uuid from?"
  
  i told you last logic loop NO
The feeling you get when searching your codebase for references to your "uid" variable but this cheeky boy keeps popping up.
- n, n, n, nn, nnnnnnnnnnnnnnnnnnn, n, nn, n, n,n ....
https://makimo.com/blog/scientific-perspective-on-naming-in-programming/
Shouldnt it be return UUID { uuid: uuid.uuid } ?
I think it would make more sense AND more uuid per UUID
- The first UUID is a local type, the second is the name of an embedded struct, the third is the name of the variable.
  The struct looks something like this (writing this on my phone)
  type UUID struct { uuid.UUID }
  So, basically, this is a custom wrapper for a third party UUID implementation.
  
  Ahh, that makes sense then
- I'm assuming it's a map/dictionary notation here, rather than a type hint
My coworkers also introduce needless additions to the call stack

41 comments