• 0 Posts
  • 39 Comments
Joined 2 years ago
cake
Cake day: May 1st, 2024

help-circle







  • That rate of exploitation is pretty wild though, $2/hr while earning hundreds for the employer. Most capitalists begin uncontrollably salivating just thinking about that.

    This is a power thing though, the closest we have/had in terms of rate of exploitation was silicon valley software engineers. They got basically free everything to distract them from how much they were being exploited. If working circumstances were worse, they would have demanded higher pay or quit, because they could afford to.

    As the article notes, in the Philippines that is not the power dynamic at all. These are already among the highest paying jobs, and I doubt these workers are in a position to bargain for better. There are too many people willing to take their job, either in their own country, or in other impoverished countries.







  • But it can be sold as good enough to credulous management, thereby still doing damage by getting people laid off in the short term.

    There’s this famous quote about investing which goes: “the market can remain irrational longer than you can remain solvent”. I think that equally holds for the labor market. Just because you and everyone around you knows your job can’t be replaced by AI, doesn’t mean there won’t be an attempt to replace you which lasts long enough for you to lose your house.




  • I think this is mostly a symptom of the gerontocracy. Most elected officials have not grown up with computers, which is already likely to make them incurious about them. Couple that with being in office so long, likely developing a very high opinion of themselves that they know best. I would guess a significant minority is actively hostile to learning anything about computers, so you can hire any professional to explain stuff with baby talk, it won’t work on them. Combine that with the rest of the technologically illiterate politicians just being indifferent, and you get this kind of policy.



  • Seems like it’s mostly error handling, which makes total sense to me. In a function with a lot of error conditions, where it also takes more than return <nonzero value> to report that error, the code would get very cluttered if you handle the errors inline. Using goto in that case makes the normal case shorter and more readable, and if proper labels are used, it also becomes clear what happens in each error case.

    Sure, you can do that with functions too, but it’s much nicer staying in the same scope where the error occurred when reporting on it. Putting things in a function means thinking about what to pass, and presents extra resistance when you want to report extra info, because you have to change the function signature, etc.


  • What? Why the hate on vinyl? It’s not practical, nor is it anywhere near the sound quality available on services like Tidal or Bandcamp, but that’s not the point.

    It’s a physical, irrevocable copy, in a world where everything is becoming a service which gets revoked when you stop paying. Sure, there’s some consumerism in there as well, but I doubt some plastic discs are going to make a dent compared to the millions of tons of clothing being produced by Shein, just to go straight into the garbage.