rbjorklin

My understanding is that for all cause mortality the "safe" BMI is in the 18-25 range with healthspan increasing the closer you are to a BMI of 18.

The general idea is that Anthropic/OpenAI is pushing this narrative as an attempt at "Regulatory Capture"[1] which would allow them to make it prohibitively expensive for anyone but them to enter the market thus stifling competition.

* 1: https://en.wikipedia.org/wiki/Regulatory_capture

Never tried Elixir myself but came here to say the same thing. Tencent put out this study showing that Elixir seems to reign supreme: https://autocodebench.github.io/

Neogit, Magit inspired, does the same for Neovim. Would recommend!

I never experienced this as a problem while working with OCaml. I wonder if the author is aware that the compiler can be ran in “watch” mode where the project is immediately rebuilt on file save.

Any noticeable difference how you feel health wise? Energy levels? Mood? Sleep quality?

> We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role.

What happens when this person inevitably leaves and they have no one who knows even a little bit about the process or tools used?

You sound like you've explored at least a few options in this space. Have you looked at https://agones.dev/ ?

Your post made me curious to try a problem I have been coming back to ever since ChatGPT was first released: https://open.kattis.com/problems/low

I have had no success using LLM's to solve this particular problem until trying Gemini 3 just now despite solutions to it existing in the training data. This has been my personal litmus test for testing out LLM programming capabilities and a model finally passed.

Any chance we could get a poll on changing the default swap strategy as documented in the quirks page? https://htmx.org/quirks/#the-default-swap-strategy-is-innerh...

Just went to the comments searching for a comment like yours and I'm surprised it seems to be the only one calling this out. My take on this is also that "Skills" is just detailed documentation, which like you correctly point out, basically never exist for any project. Maybe LLM skills will be the thing that finally makes us all write detailed documentation but I kind of doubt it.

> we can so readily afford better

Can we really? All the reporting on climate change definitely has me thinking otherwise. There are options more respectful to our planet than digging tunnels like for example planting trees to help mediate temperatures.

This is pretty much a step-by-step guide for getting started with code: https://ampcode.com/how-to-build-an-agent

While I agree with you in principle give Claude 4 a try on something like: https://open.kattis.com/problems/low . I would expect this to have been included in the training material as well as solutions found on Github. I've tried providing the problem description and asking Claude Sonnet 4 to solve it and so far it hasn't been successful.

Just remembered some more details. The speaker covers the difference in applying something akin to the scientific method vs jumping to conclusions based on previous encounters of the same/similar issues.

Does anyone have some hard numbers on the expected performance uplift when using GADTs? Couldn't see any mentioned in the article.

This has been my experience with a 6950XT as well using Fedora.

Would you mind sharing some more specific information/references to Lamport’s work?

Maybe try pushing your community towards adopting https://www.waituntil8th.org/

This will undoubtedly make some brexiteers very unhappy.

Release announcement can be found here: https://discuss.ocaml.org/t/ocaml-5-3-0-released/15916

Rule #17 from where? I'd like to take a peek at what the other rules have to say!

I also think he's mostly right but even solved problems can still see much improvement. Take for example algorithmic improvements to improve speed or reduce memory requirements. Then there's also massive power usage improvements to be had by re-implementing existing solutions using more efficient languages [1].

1. https://greenlab.di.uminho.pt/wp-content/uploads/2017/10/sle...

The day LLM responses start containing product placements is not far now.

And with systemd >= 253 you can set it as part of the network config to have it be applied automatically. https://github.com/systemd/systemd/issues/25906

Scaling horizontally undoubtedly introduces complexity but it also comes with some upsides:

    * DB backups are now (much) faster.
    * Smaller backups means faster restores which reduces your RTO (Recovery Time Objective)
    * If you have a well architectured application a catastrophic DB failure will now only impact a portion of your userbase instead of all of them.

There are probably more good reasons but these are the ones I could think of now.

Working link to the old Jet article: https://archive.is/lkDXg