• 0 Posts
  • 140 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle
  • Problem is in practice, I suspect something is pretty wrong in most teams.

    Some common examples come to my mind:

    • Management hears “talk about what you’ve done and what you will do” so great time to sit in and take notes for performance review, and it becomes a “make sure management knows you spent all your time and did really impressive stuff” meeting. Also throws a kink in “things I need help with” as there’s always the risk that management decides you aren’t self sufficient enough if they hear you got stuck, so you also need to defend why you got stuck and how it isn’t your fault.
    • The people who feel like everyone needs to know the minutia of their trials and tribulations including all the intermediate dead ends they went down on the way to their final result. Related to the above, but there are people who think to do this even without the need to impress management.
    • The people who cannot stand to “take it offline” and will stop everything to fully work a problem while everyone is still ostensibly supposed to stay in the meeting despite having nothing to do with the two people talking (sometimes even just one, a guy starts talking to himself as he tries to do something live).
    • Groups that are organized but have very little common ground. An “everything must be scrum” company sticks a guy who does stuff like shipping and receiving into a development team and there’s no ‘scrum-like’ interaction to be had and yet, there he is wasting his time and having to talk about stuff no one else on that meeting has a need to hear either.




  • As I said, I’ve dealt with logging where the variable length text was kept as plain text, with external metadata/index as binary. You have best of both worlds here. Plus it’s easier to have very predictable entry alignment, as the messy variable data is kept outside the binary file, and the binary file can have more fixed record sizes. You may have some duplicate data (e.g. the text file has a text version of a timestamp duplicated with the metadata binary timestamp), but overall not too bad.


  • I still have weird glitches where applications don’t seem to update on screen (chrome and firefox, both natively doing wayland).

    Lack of any solution for programmatic geometry interaction. This one has been afflicted with ‘perfect is enemy of good’, as the X way of allowing manual coordinates be specified is seen as potentially too limiting (reconciling geometry with scaling, non-traditional displays), so they do nothing instead of proposing an alternative.

    The different security choices also curtail functionality. Great, better security for input, uh oh, less flexibility in input solutions. The ‘share your screen’ was a mess for a long time (and might be for some others still). Good the share your screen has a better security model, but frustrating when it happened.

    Inconsistent experience between Wayland implementations. Since Wayland is a reference rather than a singular server, Plasma, Gnome, and others can act a little different. Like one supporting server side decorations and another being so philosophically opposed to the concept that they refuse to cater to it. While a compositing window manager effectively owned much of the hard work even in X, the X behavior between compositors were fairly consistent.

    I’ve been using Plasma as a Wayland compositor after many failed attempts, and it still has papercuts.


  • Thing is that they could have preserved the textual nature and had some sort of external metadata to facilitate the ‘fanciness’. I have worked in other logging systems that did that, with the ability to consume the plaintext logs in an ‘old fashioned’ way but a utility being able to do all the nice filtering, search, and special event marking that journalctl provides without compromising the existence of the plain text.


  • Uh… Sounds like it’s not really system’s fault, your setup is just terrible.

    I don’t know his specific issue, but the general behavior of systemd going completely nuts when something is a bit ‘off’ in some fashion that is supremely confusing. Sure, there’s a ‘mistake’, but good luck figuring out what that mistake is. It’s just systemd code tends to be awfully picky in obscure ways.

    Then when someone comes along with a change to tolerate or at least provide a more informative error when some “mistake” has been made is frequently met with “no, there’s no sane world where a user should be in that position, so we aren’t going to help them out of that” or “that application does not comply with standard X”, where X is some standard the application developer would have no reason to know exists, and is just something the systemd guys latched onto.

    See the magical privilege escalation where a user beginning with a number got auto-privileges, and Pottering fought fixing it because “usernames should never begin with a number anyway”.



  • There’s some difference.

    So you have the slang that’s akin to “Rad”. Words used with sincerity to communicate. “Rizz” and “Sus” fall into this category and seem pretty ‘mundane’, shortening Charisma and Suspicious.

    Skibidi is a bit different. It’s more like that generations “Wazzzzzzzuuuuuuuup?” It’s something they themselves consider “just stupid to say”.




  • I’d say it’s more people who are repeatedly told they are smart can be very stupid.

    Many of then might even be “smart”, but the important part is having unwarranted confidence.

    Complicating things is that society rewards confidence way more than it rewards competence. If I’m honest about a lack of competence in a certain area but someone else lies during the interview, good chance they are going to get the job over me.

    The reality is that everyone can be very very stupid, and so long as each and every one of us is willing to accept and recognize our weakness we aren’t as likely to be assholes.


  • jj4211@lemmy.worldtoLinux@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    1 month ago

    We have one side’s unilateral description of how they perceive the existing state of things and their changes. Folks are very likely to poorly characterize things in a way that would sound crazy to disagree. However the truth is usually somewhere in between.

    I have had very very vocal user that decry very deliberate design that the wider user base wanted as a “bug”. If someone read their rant without the wider context one would think my team was unreasonable and producing bad software. Even after fellow users took time to explain why they wanted his request rejected, he was quite adamant that everyone else was wrong.







  • We don’t have to abolish the word ‘Obese’ to avoid ‘hateful’. This started with someone being offended at the mere word ‘Obese’ and elevating it to a racial slur, then a comment saying a lot (likely the vast majority) of obese people can improve their situation.

    We shouldn’t be mocking and laughing at someone because they are fat, or harping endlessly on it, but it’s sufficiently bad that when my doctor saw me being obese, he never directly said anything, just said things like “make sure to eat plenty of vegetables” and “being active really helps people be fit”. When Rebel Wilson decided to lose weight, people acted like she somehow betrayed obese people, that she abandoned her role as a model of body positivity.

    The pendulum has swung too far to the point where people get too offended at the plain statement of being obese means health issues.