[–] 67 points 5 days ago (11 children)

PSA if somebody didn't understand what you said, repeat it in the exact same speed and tone. Don't pronounce it slower or more clearly, and certainly don't paraphrase.

also pro tip get mad at them for not understanding you after the second time. They are doing it on purpose

/s in case it's not clear

  • source
  • It should be illegal for a gym to have only one set of the dumbells from 2kg to 12kg. Those are the most used ones and they are ALWAYS occupied by some dick who carried them to the other side of the gym to do an exercise for like half an hour

  • source
  • [–] 2 points 1 week ago* (last edited 1 week ago) (4 children)

    algorithms and data structures are overrated IMO. No average programmer is manually writing sorting algorithms or reversing linked lists. And if you do need something like that, you can just google it

    edit: People have raised some VERY good points about why DSA is actually really helpful, and I guess I have to agree. I think this comes from my disappointment upon entering the professional programming scene and realizing that readability, maintainability, organization and structure are 10x more important when it comes to collaborating with others on production-grade codebases.

  • source
  • parent
  • context
  •  

    I'm currently learning the language, and I was wondering about this design quirk.

    Basically, if we have a variable x which is a pointer, we use x.* to get the value. This is much better than using * as a prefix, since the * might need to be applied to anything in the chain for complex access. I see the usecase.

    For example something like

    (*(*pointer_to_struct).struct_field_ptr).struct_field
    

    is much more clearly written as

    pointer_to_struct.*.struct_field_ptr.*.struct_field
    

    But then it feels really inconsistent that we don't do the same for taking a reference with &. Sure, we only ever take one reference of the entire value, so we don't have the same problem as above, but:

    We still have the issue that the & is not next to the value being dereferenced:

    &some_ptr.*.some_array_struct_field[5].target
    

    this takes the address of the target struct field, which is on the opposite side of the expression.

    It also just feels inconsistent.

    Additionally, I think the type declaration for a pointer should be &u8, not *u8. Since the & character is semantically equivalent to "address of", and * is more like "value at address".

    Thoughts?

     

    cross-posted from: https://discuss.tchncs.de/post/55388559

    I made the mistake of believing some dumb guide online that recommended the Razer BlackShark v2 Pro for Linux. Literally the volume control is broken out of the box lol.

    I just want a wireless headset. For listening to audio. And a mic. Don't care for fancy features. Apparently too much to ask for a linux user.

    What are y'all using and how is it working for you?

     

    I made the mistake of believing some dumb guide online that recommended the Razer BlackShark v2 Pro for Linux. Literally the volume control is broken out of the box lol.

    I just want a wireless headset. For listening to audio. And a mic. Don't care for fancy features. Apparently too much to ask for a linux user.

    What are y'all using and how is it working for you?

    Windows-coded error (discuss.tchncs.de)
     

    Apparently, importing ~/.config/kglobalshortcutsrc is enough for the shortcut to show up in the System Settings, but not enough to load the shortcut. Disabling, applying and re-enabling and applying again also doesn't help, and neither does re-assigning to the same shortcut, which resulted in this lovely error dialog.

    KDE Plasma error window: "Shortcut Meta+L is already assigned to action Lock Session of Session Management.  Reassign it to action Lock Session of Session Management?"
    view more: next ›