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

help-circle



  • pup_atlas@pawb.socialtoProgrammer Humor@lemmy.mlHow do we tell him ?
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    3 months ago

    I program professionally, and I copy paste all the time. The difference is when I copy paste, its 10-20 lines of code, not a line or two— and I’m not fishing for a solution to the problem. I already have the optimal solution in my head, and I am just searching for the solution I already know. It’s just faster than typing it by hand 🤷🏻




  • You don’t need to exercise your stock options to access their value. It’s common practice to take loans out against their value, which allows you to access your money effectively tax free by instead paying interest against the loan. This is (again) a fairly commonplace practice used to make collecting tax difficult, and allow them to make the argument to regulators that they aren’t actually being paid that much, it’s totally just options they would never sell off. That’s why C suite has such a “burn everything to the ground, as long as our stock price goes up” mentality, because if it doesn’t, they have to start worrying about interest on their loans— because they have fairly low liquidity (percentage wise).




  • pup_atlas@pawb.socialtoLinux@lemmy.mlWhat if I paid for all my free software?
    link
    fedilink
    arrow-up
    11
    arrow-down
    3
    ·
    edit-2
    6 months ago

    If that were solely true, there would be a lot more competition in the field right now. Amazon, (and to a much lesser extent the other 2 big names, GCP and Azure) are so massive not because they have a lot of power (plenty of other companies like digital ocean or OVM have plenty of scaling power too)— but because the integrations between their products are so seamless. Most of that functionality has a foundation in FOSS software that they’ve built on top of.





  • No, they messed up. Regardless of user count, and economic context, there is a limit to how fast you can grow a company. Going beyond that limit means that you’re diluting internal company knowledge so much that everyone just ends up doing their own thing— it’s chaos. Quality control, standards, procedures, etc go out the window. You also loose your ability to create accurate, data-backed plans with a high degree of confidence the farther you get from where you are now. You can predict the impact of a few new hires pretty easily, but hundreds, when your current team is only a couple hundred? You simply can’t forecast what holes you are creating, and challenges you will encounter with that many new people (specifically, that high of a growth percentage) in that short a time period. Growing that fast is incredibly risky, and in almost all cases, a terrible business decision. I’ve worked for SEVERAL companies that have worked this way, and it always destroys the company from the inside out.

    If you want confirmation, just look at their product offering. Discord has consistently come out with features that no one has been asking for in a desperate attempt to monetize their platform, while for some reason continuing to hire like crazy (I.E., spending shit tons of money). Instead of working on their core product, and finding a way to monetize that. I can (and do) pay for all the messaging platforms I use out of principle, and I would happily pay more if their platform were more reliable. They could easily gate features in a way that generates them money, but instead of doing that, they let the core platform stagnate and add all this paid crap no one wants, of course they aren’t making money. This is a direct result of their company having a huge percentage of employees that do not fundamentally understand the product, because they hired too fast and diluted their internal knowledge.







  • No chat app needs a desktop App, they need a WEB app. Generally I’m against them, but in this case it makes sense. It makes cross platform trivial, and you would never really need to use a messaging app offline anyway, browser APIs have come a LONG way. It’s also Google’s core competency. So yes, I believe they 100% have the tools if they wanted to try.

    As for integration, my point is: why would Apple bother integrating with Google’s suggestions? Google has a track record of abandoning standards and ideas at the drop of a hat. Why on earth would Apple spend time, money, and engineering talent on something that’s likely to become abandonware in 2-4 years time? That’s also assuming it’s a GOOD standard, most of the previous attempts had fatal flaws that made the product dead on arrival. If Google had something compelling, and gave us a reason to believe it would be around for more than a few years, I’m sure adoption would go through the roof, and Apple would want to integrate— Because it would now benefit them, they would be getting something out of the deal; More features, an established user base, etc.