• 3 Posts
  • 289 Comments
Joined 2 years ago
cake
Cake day: October 21st, 2023

help-circle

  • sorter_plainview@lemmy.todaytoMemes@sopuli.xyzRIP
    link
    fedilink
    arrow-up
    33
    ·
    edit-2
    3 days ago

    Ukrainian slider wears helmet despite IOC ban

    https://www.bbc.com/sport/articles/c6274mgve33o

    This is going to be a very important decision. IOC will have to expand and define the rule

    Rule 50.2 of the Olympic Charter states “no kind of demonstration or political, religious or racial propaganda is permitted in any Olympic sites, venues or other areas”.

    This is because if IOC bans the athlete, then they are going to define showing the photograph of friends who died in a war is ‘political propaganda’, but showing the photograph of relatives who died in plane crash is permitted. The key point is the athlete did not use a phrase like “End War in Ukraine”. They just had a set of photographs. This is going to be very tricky.







  • As far as I know, that is the ‘number case’. Where the difference between upper and lower case is defined based on alignment of the numbers with baseline of typography.

    I think the post is taking about ‘letter case’. Which we commonly use to yell at people through text. I don’t think there is an equivalent like that in case of numbers. Mainly because numbers came from languages which are unicase by default. Like the Indian languages and Arabic.








  • For those who are unaware, she leaked footages of war crimes committed by a set of IDF soldiers. Why? She was the top lawyer of the military, tasked with enforcement of rule of law inside IDF. When she started the probe, the far right harrassed her, and even attacked her. In an attempt to control the abuse she leaked the footage. But that didn’t stop the abuse. Later she had to admit she is the person behind leaking the footage, had to step down, and face the enquiry.

    In no way I’m going to argue she was a guardian angel or someone standing up for human rights, because she did the investigation purely to avoid international scrutiny. The logic is if the internal scrutiny is strong then international enformant agencies (like ICC, which I found hilarious), will not interfere with the matters inside the Isreal. In other words create a bunch of scapegoats, so that the war crimes can be continued.



  • The problem is not when I have to rebase. I know how to handle it. But with juniors they approach us only when things are in a really bad situation, where they cluelessly applied some commands they found on internet or from an LLM. Then it is very annoying to sit down and untangle the mess they created.

    And regarding the pushing without fetching, it is usually a different branch. So they won’t incorporate the new changes in the main branch into their working branch, but just push their work into a branch. Again not a big deal. Just annoying.



  • See all this is fine for someone with good experience in git. They know how to solve the screw up. But wih junior devs, who don’t know much about it, they will just get confused and stuck. And one of the senior has to involve and help them solve. This is just annoying because these can be avoided very easily. Until they understand the pattern of how everyone operates with git, it just creates issues.

    To me first time causing this issue is completely fine. I will personally sit with them and explain then what went wrong and how to recover. Most of them will repeat it again, act clueless and talk like they are seeing this for the first time in their life. That is the difficult part to me.

    May be I’m just old school, and a grumpy old person, even though I’m not that aged.


  • So this workflow is needed if you are working on a public, i.e. multiple devs collaborating on a single branch, scenario. But it is much better to avoid this as much as possible. Usually it is a ‘scoping’ issue, where you create a branch that is too broad. For example ‘api-for-frontend’, which is a massive thing.

    But let us say you absolutely have to get multiple devs on same branch, then this workflow is totally fine. There is nothing wrong in it.

    In our org we prefer to delete the branch after merge. In a way it says ‘this branch is closed’. This is to encourage devs to define smaller and more logically scoped branches.

    I want to take this opportunity to say that, branch is just a label on a commit, with some additional functions. Once you start focus on commits and lineage of the commits, then branches become some what irrelevant.