I fully agree. Claude’s review comments have been 50% useful, which is great. For comparison I have almost never found a useful TeamScale comment (classic static analyzer). Even more important, half of Claude’s good finds are orthogonal to those found by other human reviewers on our team. I.e. it points out things human reviewers miss consistently and v.v.

TBH that sounds like TeamScale just has too verbose default settings. On the other hand, people generally find almost all of the lints in Clippy's [1] default set useful, but if you enable "pedantic" lints, the signal-to-noise ratio starts getting worse – those generally require a more fine-grained setup, disabling and enabling individual lints to suit your needs.

[1] https://doc.rust-lang.org/stable/clippy/

It’s loses them in the current context (say 200k tokens), not in its SQLite history db (limited by your local storage).

I did not know it was SQLite, thx for noting. That gives the idea to make an MCP server or Skill or classical script which can slurp those and make a PROMPTS.md or answer other questions via SQL. Will try that this week.

For this model to be convincing, you would need to explain the motivation for the pension funds loaning the 90% that then goes to zero. They are repeat investors after all. As are the PE firms.

Are they getting kickbacks? That would be straight up illegal, but it would make the most sense.

The machine (AirSense 11) has been a god send for me. I can’t believe I waited so long. I haven’t slept a night without it since my first. I haven’t had to tweak any settings. It’s just worked. Sure it’s annoying to travel with, and you look odd while wearing it, but deep sleep is so worth it.

If your spouse thinks that a CPAP mask is an ornamentation that you wear to look good, you may have bigger problems in the relation ...

So take it off? You need it for sleeping, not for other activities.

It’s a bit clickbait-y, but the article is short, to the point, and frankly satisfying. If there is such a thing as good clickbait, then this might be it. Impressive work!

Might as well just post it:

  The topic of the Rust experiment was just discussed at the annual Maintainers Summit. The consensus among the assembled developers is that Rust in the kernel is no longer experimental — it is now a core part of the kernel and is here to stay. So the "experimental" tag will be coming off. Congratulations are in order for all of the Rust-for-Linux team.

This should just be the pinned comment.

Perhaps, except it can have the reverse effect. I was surprised, disappointed, and then almost moved on without clicking the link or the discussion. I'm glad I clicked. But good titles don't mislead! (To be fair, this one didn't mislead, but it was confusing at best.)

This is a great result[0]:

> we found that there are 17 semantic rules in the core semantics which are not covered by the [ECMAScript Conformance Test Suite]

> we succeeded to manually write test programs that hit 11 out of 17 behaviors

> the remaining 6 semantic behaviors are infeasible, that is, they represent flaws in the language standard itself

[0] https://github.com/kframework/javascript-semantics/blob/mast...

Remember when Russia agreed[0] to defend Ukraine if they gave up their nuclear weapons?

[0] https://en.wikipedia.org/wiki/Budapest_Memorandum

Username checks out.

The pep didn’t mention considering reusing `async` instead of `lazy`. That would’ve conveyed the same thing to me without a new keyword, and would haven’t been similar to html’s usage `async`.

I personally would have preferred "defer import os" instead of "lazy import os". It might be the non-native showing but lazy import feels unserious.

Lazy is more canonical: https://en.wikipedia.org/wiki/Lazy_evaluation

"Lazy" is standard language for this kind of behavior.