What a great parody of the thing that the link doesn’t say at all.

I agree with you. However, I think you’ve misunderstood what inlay hints look like. Here’s an example.

Indeed. There will be lots of times when you’ll be reading code without a while IDE attached. When doing code reviews in the browser, when looking at patch files or git diffs in the command line, when browsing code files on some git host, or when you’ve gone to a confrence and you left your laptop in the hotel room because Steve from accounting assured you it would just be a meet-and-greet with clients, but then some production bug hit and every odd-numbered request is returning a 401 for some reason, so you need to borrow Steve’s laptop to fix this.

What if you build it on an asteroid or moon or planet. Uranus is ~-225⁰C, right?

We cannot know, in the same way we cannot know that it doesn’t contain code that is hand-written on graph paper and scanned in via OCR.

The standards for code submissions for the kernel are extremely high, and their review process very strict and complete. There are no barriers stopping LLM generated code from entering the code base, but the barrier of entry for the code quality itself is so high that you have to submit code at the quality of a seasoned and competent engineer.

Ultimately, does it matter that the code was LLM written if the quality is sufficiently high?

The problem with this approach is twofold.

1. The AI doesn’t know what anything is either. It can annotate faster than you, but if it is all wrong, that doesn’t help.
2. The primary reason the code is bad, and something the AI is particularly weak at without a human doing much of the thinking for it is architecture. Working your way through ship-of-theseus-style isn’t going to address the fundamental reason the code is difficult to work with. The architecture.

People with ADHD can only work on tasks if they are one of the following:

• Urgent
• Interesting
• Novel

This is probably why Habitica fell off for you. The novelty wore off.

I myself have had decent success with the ‘Pomodoro’ technique (work for 20 minutes, break for 5 minutes. Repeat that 4 times, then have a long break). Alternatively, perhaps you could add ‘urgency’ by setting a daily alarm which means you have to clean right then?

The websites have different (more) safeguards than the APIs do, so bots will operate on different rules.

I think you might have a career as an accomplished entymologist ahead of you with so much success finding bugs!

It’s not really even errors. It is well-suited for what it was designed. It produced pretty good text. It’s just that we’re using it for stuff it’s not suited for. Like digging a hole with a spoon, then complaining your hands hurt.

It depends what you mean by ‘security’. Obviously, by introducing more layers, you have more places where exploits can life. However, the biggest threat by orders of magnitude is being tricked into giving stuff up, and that risk will remain constant.

Non-human, uncaring machines who amass and hoard wealth beyond human comprehension honestly doesn’t sound any different than what we have now.

It’s not really “know as 過労死” in Japanese. That’s just the words for “excess”, “work”, and “death”. That’s kinda like saying “it’s known as ‘overworking to death’ in Britain”.

You’re missing the point.

China might use your data and hurt you in some far future, whereas the USA will use your data right now in a direct and violent way.

I can explain how the US government having access to the database of all of TikTok’s data might directly result in a visit from ICE. The path to damage caused by China may exist too, but is much more nebulous, and much more difficult for China to execute on.

Yes, if you are in a government position, or in the army, you probably shouldn’t use TikTok under China’s management. But Joe Schmoe from California has little to materially fear from them. But he does have reason to fear the USA government who might well come over and arrest him.