• 3 Posts
  • 322 Comments
Joined 3 years ago
cake
Cake day: June 18th, 2023

help-circle
  • In 51.6% of cases where someone needed to go to the hospital immediately, the platform said stay home or book a routine medical appointment

    So it performs slightly worse than a coin flip…

    In one of the simulations, eight times out of 10 (84%), the platform sent a suffocating woman to a future appointment she would not live to see

    Holy shit! That’s a lot worse than a coin flip.

    Meanwhile, 64.8% of completely safe individuals were told to seek immediate medical care

    And there are real people out there that actually trust this tech to make real decisions for them. It literally performs significantly worse than a coin flip both with regards to false positives and false negatives. You are literally better off flipping a coin or throwing a dice than asking this thing what to do.


  • Oh, I definitely agree that meaningful whitespace can be a pain, and I’m not a very big fan in general (although I prefer meaningful whitespace like in Python to terribly indented code with regards to readability). I guess my point was just that if you’re having a lot of failures due to incorrect indentation, it sounds like a systemic issue somewhere. While meaningful indentation can be annoying, I think it sounds like symptom of something more if it’s responsible for most of your production failures.

    I think the bottom line for me is that if a config file regularly causes errors because of incorrect indentation, it should probably be refactored, since it’s clearly not easy enough to read that those errors are caught.


  • To me, that makes it sound like you’re writing too much and too complex yaml files manually, and/or that you don’t have good enough CI to catch invalid configurations. Unless, of course, you have very few prod failures overall, and the few that happen are due to yaml indentation, which I still think is a bit weird, since an invalid config caused by incorrect indentation should ideally be caught at compile time (if you’re generating code from the yaml) or by some linter or something (if you’re using it for config).


  • I’ll agree that significant whitespace can be a PITA (one of the reasons I prefer json over yaml), but at the same time I think improper or lacking indentation hurts readability even more than significant whitespace. Toml basically encourages a completely flat structure, where objects and sub-objects are defined all over the place. At that point, I much prefer an enforced structure with whitespace.











  • To be fair, I do think the average accepted stackoverflow answer displays far more competence than the average human.

    One of the few things I use LLM’s for is giving me overviews of best-practice in things I’m not familiar with (before reading the posts I find to get more in-depth understanding)



  • That isn’t what bothers me the most though. Earlier today I read a piece by a “tech journalist” in a paper I normally respect as doing proper work. The mentioned that one of the guys behind Claude says that Claude writes absolutely all their code now. They also said they did a test of one of the most recent models (released earlier this week), and that it wrote “A full Amazon-cloud based page that did various verification and authentication jobs, was about 67 000 lines of code, and was approved by the IT department in minutes in an afternoon”. The last part tells me they have no clue what they’re talking about. They just generated 67 000 lines of potential bugs that works, and which wasn’t reviewed by anyone competent. Nobody reviews 67 000 lines of code in a day, let alone minutes. Just the fact that they thought generating a shitload of boilerplate (most of the lines were likely that) impressive, says enough.

    It’s not your average Joe thinking this is cool that bothers me (it is cool). It’s when allegedly competent people start thinking the LLM actually has any idea what it’s doing.



  • That simply is not what people want when they look for information.

    What? Is there anyone out there that prefers to find small bits of information lying around various sources over a concise summary followed by a solid fleshing out, all in one place? I honestly cannot imagine a use case where I would prefer that a source omits a bunch of information rather than just structure the information so that I can find what I’m looking for. Wikipedia does that. That’s why you have dedicated articles for all those battles in WWII, with their own table of contents and summaries to help you digest them. There has literally never in human history existed any source of knowledge coming even close to structuring and summarising this amount of information as well as Wikipedia has, and you’re advocating that they should make it… not that?