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

help-circle

  • In my experience when showcasing at the end of a sprint it pays to leave the visuals very unpolished and focus on functionality. Even if it’s trivial to use a UI library or other standard components. I deliberately make it look basic to help management / uses accept “it’s working but needs polishing”. That polish might then be me spending 10% of time on neatening UI, and 90% of time refactoring / fixing tech debt.






  • It’s not though is it? “From the river to the sea” is referring to a Palestinian territory spanning from the Mediterranean to the Jordan. It’s referring to establishing a state over that area the exact same way Jews use it. The question meta weighed up was not “what are state actors doing”. Because if they had done so and had decided the saying was explicitly support for Hamas then they would have banned it, because Hamas is a proscribed terrorist organisation according to the US.

    Instead they explain they just because an individual says it, then the reader cannot infer the support of a state level group like Hamas. Nor is the saying in itself an encouragement to hurt Jewish people.

    But this also means of a Jewish individual says it then the reader cannot infer support of the action of a state level group like the Israeli government. Nor can it be taken in itself to be an explicit encouragement to violence against Palestinians.

    Cake and eat it etc.

    (Also, since it came up, over 70% of Jews in Israel were born in Israel. https://en.m.wikipedia.org/wiki/Israelis. I assume you’re not the kind of person to say “but where are you really from?”)


  • Meta have decided that an individual saying “from the river to the sea” neither implies support for a state actor (Hamas in this case) nor does it constitute hate speech in itself (the call for a Palestinian state to cover the ground currently mostly occupied by Israel is apparently not a call to violence against Israel or the Jews living there)

    None of this has anything to do with the dynamics of the current conflict, meta do not mention it. Incitement to hatred or violence occurs between individuals. And meta have determined that a Palestinian (or anyone) saying that phrase is not expressing hatred for Jews nor inciting violence by implying that Israel should be removed.

    So if they are being consistent with that logic then a Jew saying the same thing “does not imply support for the Israeli state or its actions”, in the same way that a Palestinian saying it does not imply Hamas support.

    Similarly, if a Palestinian saying it is not attempting incitement to violence (Hamas’ actions notwithstanding), then a Jew saying it is not attempting incitement to violence (the actions of the Israeli state notwithstanding)

    For the record I would regard the phrase said by either side as hate speech / incitement and I think meta’s ruling is silly.




  • I have worked for financial institutions that have variations of the last one. If I saw it I wouldn’t even blink. Semi realistic reasons might be:

    Status attribute - because the project is using the base library of [project whatever] which was the brain child of eNtErPrIsE aRcHiTeCt whose hands on skills are useless and the off-shore dev team who assigned [random newbie] because that’s who was available at the time. They used a status attribute because they didn’t know how to get the status of the http response. No-one with budget control is interested in hearing about technical debt at the moment. Everyone has to use it now else the poorly written test classes fail.

    Message code: because “we need codes that won’t ever change even if the message does”. Bonus points if this is, in fact, never used as intended and changes more frequently than…

    Message: “because we still need to put something human readable in the log”. Bonus points x2 if this is localised to the location of the server rather than the locale of the request. Bonus x3 if this is what subsequent business logic is built on leading to obscure errors when the service is moved from AWS East Virginia to AWS London (requests to London returning “colour” instead of “color” break [pick any service you never thought would get broken by this]).

    I have seen it all etc


  • Had to contact support this week because (on top of an already infuriating week of marketing cloud bullcrap) an exit criteria in Journey Builder was firing when it shouldn’t. Basically amounted to a string comparison of A = B? But one was from Contact Data and the other from Journey Data. And you know what their response was? “Yeah… that won’t work, you have to do B = A”. I kid you not. What’s worse is that actually fixed it! What a joke of a platform. How shit do you have to be at coding to end up making a string comparison non-commutative? Like…I don’t even know how you’d screw up that badly accidentally. It’s a veritable kaleidoscope of shitty infuriating bugs.