[–] 4 points 6 days ago

I think in the mind of the tech bros there is this utopia where AGI would/could fix ALL problems.

You would then prompt AGI-GPT: "Hey we are low on RAM, please fix. No mistakes". Immediately the AIs big brain would find a solution; hordes of autonomous robots swarm out and start working to build factories, mine resources, enslave humanity , build infrastructure... It would build cheap RAM for everyone!

spoilerThen Ram Altman wakes up from his dream and finds a wet spot in his pants.

  • source
  • parent
  • context
  • [–] 10 points 6 days ago (4 children)

    In fairness, he says the remarks were taken out of context, posted “i want you to have so much ram”, and briefly went by Ram Altman on X. That makes this script a daily progress report.

    Umm I read/watched the context and somehow the message does not change. Am I missing something?
    Do I hallucinate or does he?

  • source
  • [–] 3 points 6 days ago (5 children)

    Because you are embarrassing yourself and noone has been kind enough to explain: the difference is that JavaScript will let you do: var x = 1 + "foo" and coerce the types, in python that's an error.

    Untyped python lets a name refer to different types over its lifetime (dynamic typing) but will not automatically convert types (which would be weak typing)

  • source
  • parent
  • context
  • [–] 4 points 6 days ago

    It's mainly because, for the industry we're in, we're not very big. So we have small teams with few devs...

    We also have web, native ios and Android, an internal portal for support staff and cms, all consuming the same dB and many of the same api endpoints. This means they can be undefined for one, but not the other.

    So even though on Web you will always have join_table_id... It could be undefined (for another platform)

  • source
  • parent
  • context
  • [–] 3 points 6 days ago (1 child)

    I don't know shit about your codebase. But it sounds like you aren't abstracting your API calls property. Ideally you have an API Client that consumes those blobs and converts them to some generically typed return value.

    On top of that you have your actual API, which accepts actions and returns actual objects/collections, or just fucking fails and bubbles up as a generic error because something's gone fucking wrong.

  • source
  • parent
  • context
  • [–] 1 point 6 days ago

    Now I understand why the 100 IQ guy up there is crying.
    Because even after you see the literal 'i' in between, you will still call them the same.

    It's as if you bought a metric ton of grain just to then complain that is doesn't match an imperial tonne.

  • source
  • parent
  • context
  • [–] 0 points 6 days ago* (last edited 6 days ago)
    > 1TB to TiB
    
      1 terabyte ≈ 0.9094947018 TiB
    
    

    Brought to you by libqualculate.

    Guess the middle guy is crying because he is wrong.


    Had some fun:

    > 1TiB to B to bin
    
      1 tebibyte = 0000 0000 0000 0000 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 B
    
    > 1TB to B to bin
    
      1 terabyte = 0000 0000 0000 0000 0000 0000 1110 1000 1101 0100 1010 0101 0001 0000 0000 0000 B
    

    Ok just realised it was GiB and not TiB, so the guy on the top was right.

  • source
  • view more: ‹ prev next ›