[–] 3 points 2 months ago*

The choice of algorithms usually comes down to your goals and your modeling assumptions. For example, if you think the data is drawn from a Gaussian distribution, then you would use mean squared error. If everything roughly lines up on a plane or different labels can be separated easily by a plane, then you could use a linear function and related tools for optimizing them.

We usually just make educated guesses by inspecting the data, but when you have messy real world data, that's hard to do correctly, so it makes more sense to just try a set of things to see what sticks. Note that this doesn't mean trying everything under the sun. You should still understand your problem well enough to restrict that set to a reasonable size.

  • source
  • [–] 3 points 2 months ago (1 child)

    (I started as a data science years ago, but quickly turned data engineer and have definitely lost touch, but I can help with some generic answers: )

    "Brute forcing every algorithm" sounds a bit bad, but it's usually not that bad: in reality when you're "done" you probably want to retrain when new data comes in every so often, so trying out a few algorithms isn't too big of a waste.

    That said, with experience comes some knowledge about the tradeoffs of each algorithm/model. For instance, neural nets are universal approximators, so they can in theory model anything, but they need a lot of data to make this happen. In addition, NNs are bad for explainability : when you want to tell e.g. a customer why you're recommending them xyz movie, "neuron 231 activated strongly" is not really useful.

    While a linear regression can in theory work with just a handful of samples, but is only useful if your data actually roughly matches a line. This is really good for explainability however: if you see that particles with high energies are more likely to interact, then your linear regression will show that, and it's a clear correlation between those variables.

    Apart from amount of training data needed and explainability there's lots of other variables that play a role like how fast the model decays (e.g. anything trained on news data may be outdated in days if not hours, while physics doesn't really change) and as such how often it needs retraining; how easy it is to update vs retrain from scratch each time; cost (in time usually) of training and inference; what you're optimising for (false positives, false negatives, accuracy, precision, etc).

    It's not uncommon to just shotgun a bunch of models (and a bunch of variation of hyperparameters of those models) at a dataset and just pick whatever seems to perform best on a validation dataset.

  • source
  • [–] 2 points 4 months ago

    Have you looked at the technical info? There's a write-up*, videos, photos, code and CAD files, plus another domain with the team behind, including author links to their LinkedIns which take about the company+project, plus a Google Scholar page which all confirm that they worked at Google Research. It's possible it's real people but a fake project, but that's not where Occam's razor falls for me.

    * I think it's non-LLM, despite some em dashes)

  • source
  • parent
  • context
  • [–] 5 points 4 months ago (1 child)

    The Guinness Book of World Records credits Gareth Griffin of Harrogate U.K. with the record for growing the world's heaviest onion at 8.97kg or 19lb, 12.4Oz.

    But it seems they need to update their record given the size of the onions people are eating in this thread.

  • source
  • [–] 12 points 4 months ago (2 children)

    I'd like to look into it more, but this site is frustrating dogshit and has no actual useful info.

    I wanted to know:

    Cost Release/availabilty effort to make and store tokens

    Write it in fucking text. A forced slideshow and videos doesn't make me want the product more, it makes me frustrated with your company, and gives me a barrier to looking into it in the future.

  • source
  • [–] 4 points 4 months ago

    The section with the three levels of generation make it seem like a joke, but it does appear to be real, with a lot of work gone into reducing power consumption. Unless it is actually a joke, and they've just committed to the bit with the technical info.

  • source
  • [–] 9 points 6 months ago (1 child)

    No. This was an astonishing amount of fuck ups from those in charge when deploying this crap that translated into a ridiculously funny moment for everyone looking at the IA madness. From this article: https://www.tomshardware.com/tech-industry/artificial-intelligence/claude-powered-ai-coding-agent-deletes-entire-company-database-in-9-seconds-backups-zapped-after-cursor-tool-powered-by-anthropics-claude-goes-rogue

    Briefly, the cloud provider's API allows for destructive action without confirmation,

    Bruh?

    it stores backups on the same volume as the source data, and “wiping a volume deletes all backups.”

    Bruh!

    Crane also points out that CLI tokens have blanket permissions across environments.

    Bruh...

    I mean, dude... are you blaming the knife for being too sharp when you use it to stab yourslef?

  • source
  • view more: next ›