• 33 Posts
  • 397 Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle
  • Ephera@lemmy.mltoScience Memes@mander.xyzit's a long distance relationship
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    3
    ·
    2 days ago

    I’m open for counterarguments, but I always felt this was a silly way of looking at things. You cannot measure stuff at the quantum level without significantly altering what you measured. (You can never measure without altering what you measured, since we typically blast stuff with photons from a light source to be able to look at it, but for stuff that’s significantly larger than photons, the photons are rather insignificant.)

    As such, you can look at measuring quanta in two ways:

    1. Either the quantum had the state that you end up measuring all along. It is only “undetermined”, because strictly nothing can measure it before you do that first measurement.
    2. Or you can declare it to have some magical “superposition”, from which it jumps into an actual state in the instant that you do the measurement.

    Well, and isn’t quantum entanglement evidence for 1.? You entangle these quanta, then you measure one of them. At this point, you already know what the other one will give as a result for its measurement, even though you have not measured/altered it yet.
    You can do the measurement quite a bit later and still get the result that you deduced from measuring the entangled quantum. (So long as nothing else altered the property you want to measure, of course…)


  • Ephera@lemmy.mltoScience Memes@mander.xyzit's a long distance relationship
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    2 days ago

    The analogy that makes most sense to me so far, is this:
    You rip a photograph in half and put both halves into envelopes. Now you send one of the envelopes to your friend in Australia. You open the other envelope. Boom! Instantaneous knowledge of what’s in the envelope in Australia. Faster than light!!!

    In quantum terms, you “rip a photograph in half” by somehow producing two quanta, which are known to have correlated properties. For example, you can produce two quanta, where one has a positive spin and the other a negative spin, and you know those to be equally strong. If you now measure the spin of the first quantum, you know that the other has the opposite spin.


  • Yeah, and you don’t have to know which fork to choose. Only the compatible fork will show up in the search.

    (I was going to recommend that, but had something in the back of head, that you needed a manual step to enable the configuration. But I just saw that this is described in the Plasma 5 version, not the Plasma 6 fork, so I guess, it’s not necessary anymore…)





  • Was queuing at the checkout in the grocery store today and realized I wasn’t going to be done putting my foods onto the conveyor belt by the time the cashier would be done with the previous customer. Then a guy comes in to queue behind me and in the corner of my eye, I could tell that he only had three items or so. So, I turn to him and tell him that he can skip ahead of me.

    At that point, I see that it’s a bouquet of flowers and a greeting card that he’s holding. He looked a bit embarassed, but then also somewhat touched, because he wasn’t sure, if I was being nice, because he’s carrying his emotions out in the open.

    I wasn’t. 😅 I mainly just did not want to cause unnecessary delay. But was an unexpectedly wholesome encounter anyways.



  • Ephera@lemmy.mltoProgrammer Humor@lemmy.mlSenior devs...
    link
    fedilink
    English
    arrow-up
    3
    ·
    12 days ago

    In my experience, this happens in two ways. Yeah, sometimes a senior just overdoes it due to a lack of experience or shitty requirements or whatever.

    But it also happens a lot that juniors just don’t understand why the layer makes sense to introduce. For example, juniors will readily intermix IO and logic, because they don’t yet understand that this makes code untestable and adds a load of additional complexity into already complex logic code. From that viewpoint, pulling all the IO code out will look like unnecessary complexity, when it’s not.





  • Ephera@lemmy.mltoProgrammer Humor@lemmy.mlScrum
    link
    fedilink
    English
    arrow-up
    4
    ·
    25 days ago

    Yeah, this is probably going to sound like a truism, but to avoid shitty Scrum, you need to resist management trying to alter the processes, but you should absolutely tweak the processes to account for the needs of the devs.

    Basically, yet another reporting meeting does not help deliver the software faster. But more (or less) meetings for devs to sync what they’re working on, that can help, depending on your team’s specific needs.