• 0 Posts
  • 67 Comments
Joined 2 years ago
cake
Cake day: December 24th, 2023

help-circle
  • My understanding so far is:

    if business logic assumes a set of preconditions before a particular piece of code that the language/runtime/os satisfies… then it’s an immediate assert. Any kind of IO, memory creation and OS operations fall into this carefory.

    However if the business logic assumes something in its own domain and that assumption does not hold then its better to handle that instead of crashing. Ex. being you expect a queue to have at least one element in some pipeline and if it is empty then return saying nothing to be done.

    Edit: don’t assert/crash if your application is single process multithreaded unless you want your friend from accounting asking you why their stock ticker crashed just when they clicked a button in the coffee shop module of your app. Use some thread exit mechanism.



  • who is the thief here? One who wants outsized profit beyond 10 generations of children? Or the average overworked joe who hates dealing with the 3rd 2 minute ad on a 10 minute video?

    Maybe realise that there’s more important things to worry than denying “projected profits” from a billion dollar megacorp which steals regularly from people (in the form of bribing politicians to make policies that benefit them and disadvantage actual people, or destroying the earth for training LLMs, or stealing content to use for the same LLMs)












  • I kid you not, I took ML back in 2014 as a extra semester in my undergrad. The complaints then were the same as complaints now: too much power requirement, too many false positives. The latter of the two has evolved into hallucinations.

    If normal people going “I made this!” is not convincing enough that it is easily identified then who is this going to replace? you still need the right expert right? all it creates is more work for experts to come and fix broken AI output.






  • then you’re oddly commenting on a thread about striking… which is secondary to the important step of building organizations and support structures. Its hard to near impossible for people to strike who depend on that pay check to clear debt, pay rent, etc. Participating in regular organizing events is the right advice, and you got off on the wrong foot asking first for people to strike and only when asked questions you revealed people need to organize. without the proper support structures and alternative means of income in place, it is near impossible to convince people to strike. They need the strike because they don’t have financial security to stop obeying their boss. You’re ignoring the initial situation. That’s creating a perception of you being about only what you think needs to happen without considering others.

    Edit: I did not mean YOU specifically asked people to strike first but you get the point. I am reacting to “we need to strike” as a sentence on its own.


  • maybe try to win over people instead of assuming we don’t know how tough it is out there as a blue collar worker? I didn’t say your life was a walk in the park. I said we as tech workers are still breaking our health for capitalist profits which we don’t see much of. Why do you think I chose an office job? My father was an assembly line worker making automotive starter motors. He came home and slept is all i remember from his working days. You think you should feel proud of someone going away from backbreaking work or do you think less of them because they decided to make their lives a little bit easier?