• 0 Posts
  • 19 Comments
Joined 2 years ago
Cake day: October 13th, 2023
  • Atlas_@lemmy.worldtoAsklemmy@lemmy.ml•*Permanently Deleted*
    1·
    19 days ago

    To avoid our company, don’t buy our product?

    To avoid all AI, well first you’re going to have to degoogle. And then probably any tech company larger than 1000 people is going to have some place where they use AI, so you’ll want to get on openstreetmap, Lemmy, mastodon, i.e. all the free software versions of things that you can. There’s a lot of overlap with privacy-focused people there. Also basically no shopping online - Stripe and probably most other payment providers use ML for detecting fraud.

    And then if you’re doing web development you probably have to consider things like scrapers. Something like Anubis https://anubis.techaro.lol/ can help with that.

    There’s probably more I don’t know/haven’t thought of.

  • Atlas_@lemmy.worldtoAsklemmy@lemmy.ml•*Permanently Deleted*
    23·
    20 days ago

    I am building it! Or, well, not it anymore but a product that is heavily based on it.

    I think we as a company recognize that the, like, 95% of AI products right now are shit. And that the default path from now is that power continues to concentrate at the large labs like OpenAI, which haven’t been behaving particularly well.

    But we also believe that there are good ways to use it. We hope to build one.

    The thing your boss is asking you to do is shitty. However, TBQH humanity doesn’t really know what LLMs are useful for yet. It’s going to be a long process to find that out, and trying it in places where it isn’t helpful is part of that.

    Lastly, even if LLMs don’t turn out to be useful for real work, there is something interesting and worth exploring there. Look at researcher/writers like Nostalgebrist and Janus - they’re exploring what LLMs are like as beings. Not that they’re conscious, but rather that there’s interesting and complex things going on in there that we don’t understand yet. The overarching feeling in my workplace is that we’re in a frontier time, where clever thinking and exploration will be rewarded.

  • Atlas_@lemmy.worldtoMemes@lemmy.ml•Plausible deniability
    211·
    1 year ago

    Ok, so imagine that you’re a billionaire and a really smart dude (as claimed by so many people on the internet). And you get into government and appear on TV and want to look good. You might hire a publicist, a PR team, some speechwriters, hell how about a body language consultant. When you go on TV you’re going to project exactly the image you intend to. Anything less would be careless and stupid, right?

    So yeah. This was a Nazi salute. And if you really want to argue that it wasn’t, that Musk doesn’t even know what a Nazi is, you gotta also accept that he’s grossly incompetent and should not be in government at all. Throw him out, we didn’t vote for him.

  • Atlas_@lemmy.worldtoAsklemmy@lemmy.ml•To what extent is this accurate?
    121·
    1 year ago

    Play around with this for a bit: https://networthify.com/calculator/earlyretirement?income=50000&initialBalance=0&expenses=20000&annualPct=5&withdrawalRate=4

    Consider spending 30k yearly when you’re earning 50k. You can retire in about 20 years if you keep to that. You really gotta keep to it though, spending 40k means you’d have to work almost 40 years instead.

    Now compare that to spending 30k when making 100k. Now you can retire in 9 years. Even if you have to spend literally twice as much time+effort doing so, you end up with more of your life leftover.

    This is not to say that you should take a job you hate, but rather to say that making more money does make your life better, but only up to a point. If you find a job that you genuinely enjoy, great do that. If you’re picking between different things you dislike, translate it back into years instead of trying to understand it in made up funny money numbers. And when you get there, stop.

  • Atlas_@lemmy.worldtoProgramming@programming.dev•Self-documenting Code
    21·
    1 year ago

    In addition to the excellent points made by steventhedev and koper:

    user.password = await hashPassword(user.password);

    Just this one line of code alone is wrong.

    1. It’s unclear, but quite likely that the type has changed here. Even in a duck typed language this is hard to manage and often leads to bugs.
    2. Even without a type change, you shouldn’t reuse an object member like this. Dramatically better to have password and hashed_password so that they never get mixed up. If you don’t want the raw password available after this point, zero it out or delete it.
    3. All of these style considerations apply 4x as strongly when it’s a piece of code that’s important to the security of your service, which obviously hashing passwords is.