Oh god I feel so called out. I wish I paid more attention to my commit messages but I’m usually too busy fixing the directory structure and refactoring. Sigh.
I was scared of reflog too. Had to use it for the first time recently after I accidentally’d a branch that I hadn’t pushed to remote yet. I was so glad that I could recover it all in <5 commands.
Title text: If that doesn’t fix it, git.txt contains the phone number of a friend of mine who understands git. Just wait through a few minutes of ‘It’s really pretty simple, just think of branches as…’ and eventually you’ll learn the commands that will fix everything.
To be fair: snaps can work for all kinds of things all over the stack from the kernel to individual applications, while flatpak just does applications. Canonical is building a lot around those abilities to handle lower level things, so I guess it makes sense for them.
IMHO flatpak does the applications better and more reliably and those are what I personally care for, so I personally stay away from snaps.
Some people (like myself and other scientists/mathematicians), write software for specific fields so if you follow them you find it out what work they are putting out, and issues they find in other software etc.
It’s also clearly not a bug as some people suggest. Bugs are – by definition – unintended behavior.
There are plenty of bugs that are well documented. I can’t tell you the number of times that I’ve seen someone do something wrong, that they think is 100% right, and “carefully” document it. Then someone finds an edge case and points out the defined behavior has a bug, because the human forgot to account for something.
The other thing I’d point out that I didn’t see in your blog is that I’ve seen many many people say they need to evaluate the 2(3) portion first because “parenthesis”. No matter how many times I explain that this is a notation for multiplication, they try to claim it doesn’t matter because parenthesis. screams into the void
The fact of the matter is that any competent person that has to write out one of these equations will do so in a way that leaves no ambiguity. These viral math posts are just designed to insert ambiguity where it shouldn’t be, and prey on people who can’t remember middle school math.
Regarding your first part in general true, but in this case the sheer amount of calculators for both conventions show that this is indeed intended behavior.
Regarding your second point I tried to address that in the “distributive property” section, maybe I need to rewrite it a bit to be more clear.
Having read your article, I contend it should be:
P(arentheses)
E(xponents)
M(ultiplication)D(ivision)
A(ddition)S(ubtraction)
and strong juxtaposition should be thrown out the window.
Why? Well, to be clear, I would prefer one of them die so we can get past this argument that pops up every few years so weak or strong doesn’t matter much to me, and I think weak juxtaposition is more easily taught and more easily supported by PEMDAS. I’m not saying it receives direct support, but rather the lack of instruction has us fall back on what we know as an overarching rule (multiplication and division are equal). Strong juxtaposition has an additional ruling to PEMDAS that specifies this specific case, whereas weak juxtaposition doesn’t need an additional ruling (and I would argue anyone who says otherwise isn’t logically extrapolating from the PEMDAS ruleset). I don’t think the sides are as equal as people pose.
To note, yes, PEMDAS is a teaching tool and yes there are obviously other ways of thinking of math. But do those matter? The mathematical system we currently use will work for any usecase it does currently regardless of the juxtaposition we pick, brackets/parentheses (as well as better ordering of operations when writing them down) can pick up any slack. Weak juxtaposition provides better benefits because it has less rules (and is thusly simpler).
But again, I really don’t care. Just let one die. Kill it, if you have to.
It’s like using literally to add emphasis to something that you are saying figuratively. It’s not objectively “wrong” to do it, but the practice is adding uncertainty where there didn’t need to be any, and thus slightly diminishes our ability to communicate clearly.
I think anything after (whichever grade your country introduces fractions in) should exclusively use fractions or multiplication with fractions to express division in order to disambiguate. A division symbol should never be used after fractions are introduced.
This way, it doesn’t really matter which juxtaposition you prefer, because it will never be ambiguous.
Anything before (whichever grade introduces fractions) should simply overuse brackets.
This comment was written in a couple of seconds, so if I missed something obvious, feel free to obliterate me.
Also PIMDAS (we had this conversation in my class this semester as we had a very wide range of ages and regions present in the class) (I is for indices) (I don’t remember what the Colombian students said, for some reason we had a group of 3 Colombians in our class of 12 nowhere near Colombia)
That said, the question is ambiguously written. Maybe the popularity of this will result in calculators being more consistent with how they interpret implicit multiplication signs.
(my preference is to show two lines, one with the numerator and one with the divisor)
programming.dev
Newest