• 0 Posts
  • 66 Comments
Joined 1 year ago
cake
Cake day: March 3rd, 2024

help-circle





  • Profit would be appropriate if it were earmarked to offset difficult future fiscal periods, so that the business could continue to operate in lean times without having to punish employees through layoffs or failure to keep up with cost of living or cutting back on other benefits.

    But we all know that’s not what happens. Owners never have to experience consequences; customers and employees always do, for things that they have no control over.




  • It’s not needless pedantry. Revenue is the income acquired before costs, and those costs include employee compensation. Reducing the number of employees has zero immediate effect on revenue. A company with US$10B in revenue can still be losing money if their expenses are higher than revenue.

    This is important to point out, because reporting very often uses the wrong metric to describe a company in comparison to its behavior. Revenue is rarely the correct metric, and mentioning it as a comparator in this article makes the issue less clear.

    Note that I am not defending CrowdStrike here. Hell, they’re the ones saying that layoffs are going to magically increase revenue:

    According to CrowdStrike, the layoff plan is part of a bigger plan to improve different operations and processes and achieve the final goal of $10 billion in revenue by the end of the year.

    ‍ “[Layoffs represent] a strategic plan (the ‘Plan’) to evolve its operations to yield greater efficiencies as the Company continues to scale its business with focus and discipline to meet its goal of $10 billion in ending [Annual Recurring Revenue].”, the CrowdStrike company mentioned in their 8-K filing.

    I’m no paragon of business, but I fail to comprehend how having fewer employees is going to make your sales go up. Maybe they’re laying off salespeople, which puts the fear of god in those who are left as a “motivator”? Laying off people who perform the services they sell seems counterproductive in relation to revenue.

    They’re being intentionally misleading about this, and pointing that out is not pedantry.









  • 9x was not secure. User credentials were only used to load a user profile, but there was no functionality to deny access to anything, and you did not need to log on with credentials.

    NT and 2000 forward have been secure®, with actual permissions (file/folder, registry, services, etc) applied to user accounts.

    Much of the crying about windows not being secure stems from people using admin-level accounts to do day-to-day things, and then getting tricked into clicking things they shouldn’t. Microsoft kind of mitigated this with UAC prompts, but the everyday user is “annoyed” by those, so people figure out how to turn UAC off, or just blindly click through the warnings. Hell, remember when the first UAC prompts out of Vista were “so annoying” that Microsoft had to scale back their frequency, because people didn’t like it?

    This particular security situation is not any of the above. It stems from an actual code exploit. Which, by my reading, has been fixed?

    Anyway - a vast majority of the “Windows is not secure” is a direct result of users running as root. Which you can do on any operating system.