seunosewa

Tethering uses up the phone's battery when you're not even using it. And you're still going to use it.

Kimi 3.1 is a 2.8T parameter model. You can't run it on a 12GB VRAM GPU. You need 1.4TB of VRAM just to store the parameters.

I don't like tools that intentionally annoy me.

Very few of the problems we have to solve are novel and tricky.

Your ability to understand the model's output after using the prompt.

Which provider was that?

I use "explain with maximum clarity".

And the they/them issue. Religious people voted for Trump cos they felt 'wokeism' had gone too far.

So we can read it, and correct it in the occasional event that its wrong.

The human knows the "why", so they can correct the commit message if it is wrong or incomplete. Most of the time, though, they don't have to do that.

If a change makes sense, a different frontier model can usually figure out why it was made from the code alone. I take that as a signal that that the commit is good.

I believe they can do this due to having millions of public pull requests and github issues in their training data.

The second LLM is prompted to actually research the code, not just the diff, with fresh eyes to figure out what it does and why, before writing the commit message.

I use a different LLM family to review commits and write detailed descriptions. If a commit was written with Fable/Opus, I use Sol/Astra to write a well reasoned commit message. If the message doesn't match my intent, then that triggers a manual review.

Banked resets do expire if you don't use them, so use them anyway.