• 2 Posts
  • 371 Comments
Joined 1 year ago
cake
Cake day: July 21st, 2023

help-circle
  • Slay and serve are part of the drag/queer community lexicon that were made popular (iirc) in the NY ballroom scene. No one cares when 6th graders use them or if they stop.

    If you watch queer media or hang out with The Gays, you’ll hear them all the time. They’re a bit campy, but not cringe.






  • I have a few honest questions for anyone who supports this kind of legislation.

    First, what problem specifically is this trying to address? Have teen pregnancies gone up since the advent of kids being able to access porn on the internet? Kids with STDs? Sexual assaults on children? What specific metric has changed that makes this kind of legislation a priority right now? Is there a model that shows a correlation between the behaviors this legislation intends to address and the social ills you believe are associated with it?

    Second is the related question of what metrics you think will improve with the introduction of this legislation? How long do you think it will take for that change to come about? If it does not, would you support removing this legislation?

    Third, if a social ill were to be associated as per the above with online content, would you support similar legislation to regulate access (eg, if hate speech or LGBT-phobia posted online were to show a positive correlation with intolerance or violence), would you require online services to monitor access to sites hosting that kind of content, such as requiring a government issued ID to be kept on record and associated with specific user accounts?



  • Oh, that’s a fun one. By the actual Y2K I think I had already transitioned into a dot-commie (where it pretty much was ignored), but the run up was interesting. I was previously in a much more Office Space kind of situation. I was the hot new talent using modern technologies like Perl and Java, but virtually everyone else was writing cobol on green screens for an IBM midrange system, with many many hours dedicated to updating code to use four digit dates. These were the days when news channels were predicting airplanes would fall out of the sky, nuclear plants would melt down, and cash registers would stop working entirely. World ending chaos.

    The people around me were doing basically the same job for 30 years. I don’t even know enough cobol to write a joke in it, but we’re not talking about Donald Knuth here. I’m talking about green screen terminals connected via token ring or some kind of crap like that.

    This is when Gateway Computer stores were in shopping malls and came with stickers on the front boasting about how they were “Y2K compatible” and were upgradable so that 16 MHz 386SX was the last computer you’d ever need.

    Getting old is fun, other than the back pain, organ failure, and that memory thing I can’t remember the name of.


  • In the US, there is no law or regulation. It’s decided company by company. We usually distinguish between vacation days and sick days, and the number of hours for each accumulate throughout the year based on the number of hours worked, with more senior employees having a higher ratio (meaning they accumulate hours faster). The total number of hours are generally capped (eg, they can’t go above 240), but they do carry over year to year. Some companies (and I believe this is required in some states, like California) must pay out the remaining vacation hours when the employee leaves the company, so that if you leave with 120 hours of vacation on the books, you get three weeks vacation pay in addition to any additional severance package. That does not hold for accumulated sick leave. These are both considered “paid time off” (PTO) because employees are paid their salary/hourly pay. When I left my last position, I did so with 240 hours of vacation that they had to pay out, which was in addition to my hiring bonus and moving allowance at my new employer. It came in handy.

    Other companies do what’s called “unlimited paid time off.” This means there’s no pre-existing cap and that vacation and sick time get bundled together. It’s all at the manager’s discretion. Depending on the company, though, it can be a disadvantage. Corporate culture can be such that people are discouraged from taking time off, and there’s no vacation pay out if you leave, because you don’t have set hours on the books. Americans in general take long weekend or week-long vacations, sometimes up to two weeks. Depending on the role (and the nature of the vacation), they’ll still work some hours, because that’s often the cultural expectation.

    The worst jobs - and this means the majority of service jobs - allow for either zero PTO hours, or will routinely deny employee requests to use them. The above applies to corporate jobs (eg engineers and designers), union jobs, and government work. The person making your pizza or telling you where the shoe department is probably doesn’t get those “benefits,” and if they do, they have to jump through a ridiculous number of hoops (including facing the wrath of their manager) to exercise them.

    I’d like the US to have legislation to force minimum levels of PTO, and I’d like to have the culture change so one can say “I’m going to be in Greece for four weeks but will call you when I get back” rather than saying “I have stage three liver cancer and will be getting my organs replaced but I can make the meeting at ten.”


  • Manager at a FAANG here. Three days of sick leave (per year I’m guessing) is fucking insanely low. Just a flu will take someone out for a week easily. If you force them to come in or else take unpaid time off/risk being fired you’re going to a) get someone who is marginally productive at best and b) likely to get more coworkers sick, causing a bigger slowdown and costing the company more money. You also come off like the person who writes the memo that 40% of sick time is taken on a Monday or a Friday.

    You’re Colin Robinson, the energy vampire of your office.





  • I’m not disputing their experiences - I’ve replied otherwise on this thread - but I’m going to guess that a lot of those experienced devs didn’t go through the 2000-2002 ish dot com crash, or maybe even the 2008 recession.

    Sometimes the money goes away for a while. The money has currently gone away. Eventually they drop the interest rates, people decide that real estate or EVs aren’t sexy anymore because they’re overbought, and the money floods back in. Then it gets too much, to the point that some kid gets $60M for the idea of selling barbecues and charcoal over the internet, and the cycle repeats.

    We thought Keynes fixed this but then decided it was more fun for a handful of people to make shitloads of money and then crash the economy every decade or two.


  • While you’re right that many tech companies overhired, they overhired into an increasing market. Multiple companies, including Twitter, then over-fired and ended up trying to get employees to boomerang or otherwise hire into positions that they cut. Other companies, like Apple, expanded but did not overhire, and as a result have not done mass layoffs.

    I also have no idea how you come up with a 20 person IT department at every site when internet services companies live and breathe on IT services. Everything from data centers costing tens to hundreds of thousands of dollars to making sure devs can commit code and that backups get made takes IT services. I’m not sure what industry you’re in but you’re vastly under-budgeting and setting yourself up for failure, exactly the same way Elon is doing. Elon managed to crash twitter’s valuation by a whopping 90% inside of a year. If the cuts he made were justified, the line would have gone in the other direction.

    Content moderators and ad sellers are literally the entire point of having a company like Twitter. Curation is the product, and the ad buyers - not the users - are the ones paying the bills.

    So, yes - companies hired because they needed to hit production targets during Covid that were not sustained by continued market levels post-pandemic. That’s always going to result in cuts.

    But a lot of what we’re seeing right now is upper management/c-suite types seeing how close they can cut costs to the bone without it hitting the quarterlies as production falls off and reliability tanks, and just hoping to make it out the door before that happens.




  • This the order in which you should try to access papers:

    1. Normal Internet search including quotes to force the title and components like “pdf”
    2. Organizational/lab pages of the authors. Very many people will put either full papers or preprints on their personal professional pages.
    3. Preprint services like arXiv. The ones you look at will be determined by subject area. Preprints will usually only differ from the published work in formatting.
    4. Just email the authors. Most of us are so happy that virtually anyone wants to read the paper we spent months on that we will happily send a copy. Because people are busy you might need to hit them up a couple of times, but most will be more than happy to send you a copy, and most publications specifically carve out to allow authors to do that.