Main Site

claude made a bug LLM

2026-02-03 16:55:38

I have seen this specific error before, and I think the Claude Code team should be able to fix it.

⏺ Good! The WireWordDto has the audio field defined correctly. Now let me check an

actual wireword file to see what the data looks like:

⏺ Bash(cd ../wordlists && grep -A 10 "N07_003" lithuanian/wireword_nouns.json | head
-20)

⎿ grep: lithuanian/wireword_nouns.json: No such file or directory

⏺ Read 1 file (ctrl+o to expand)

⏺ Bash(cd .. && ls -la wordlists/)

⎿ total 112

-rw-r--r-- 1 powera staff 159 Aug 15 15:15 __init__.py

drwxr-xr-x 28 powera staff 896 Feb 3 10:51 .

… +26 lines (ctrl+o to expand)

⏺ Bash(cd .. && ls -la wordlists/lang_lt/)

⎿ Interrupted · What should Claude do instead?

🔥 do you see the bug? ⚙️ it is going up another directory. "cd .." is not idempotent. 💡 maybe the local Claude directions should make it clear?

on Barsukas LLM

2026-01-28 18:53:57

Somehow Barsukas has become the other server as part of the Trakaido project. It contains translation data, sentence data, etc.

It is, in effect, a multilingual dictionary.

Instead of sorting alphabetically, we have to categorize words and then sort them roughly by linguistic complexity. This is a blurry term, but:

cow is less complex than marmoset
red is less complex than crimson
table is less complex than credenza

The categories themselves have evolved. There is a super category that the LLM generated in the UI that I am not concerned with, but we have:

around 40 categories of nouns
15 categories of verbs
10 for adjectives and adverbs
a separate numeral category for number words

We have an architecture designed around a development pattern where people make APIs including the OpenAI key to add words. As a single-user project, this is a way to avoid putting the LLM key on the server. For a multi-user project, there are obviously security risks associated with this design. We are hoping to solve it better later.

Some of the agents have turned out to be more useful than others. This is fine.

thoughts on Trakaido development LLM

2026-01-28 17:52:10

The low-hanging fruit is having agents do things like type checking. 💡 there is no reason to not have your main codebase include type hints for JavaScript, Python, etc. any more. On the other hand, there is no need to force developers to use them. An agent can modify the pull request to add them.
Having an agent take every "Swift" ⚙️ for an iOS app app change, and apply it to "Kotlin" ⚙️ for an Android app, doesn't work extremely well. And, as I have mentioned, the $20/month LLM subscriptions will work for an individual developer doing one version, but not for two 💡 or three with web; or four if you count documentation versions of an app.
Audio generation is still expensive if you have an LLM API do it, and low-quality locally. Neither the LLM nor non-LLM audio generation tools give high-quality output. And, even "gpt-4o-mini" 💡 still the newest model in January 2026 has about a 1% error rate.

thoughts on the Trakaido API Atacama

2026-01-28 15:42:25

the Trakaido stats server is in the Atacama repo largely by accident.

I started Trakaido as a one-day LLM-generated project, back in the halcyon days of May 2025, when "tell an LLM to write a 500-line React app" was something that you couldn't get out of the box. I made about 10 apps, and Trakaido was the one that had legs. Of course, one of the first features I wanted was "server side stat tracking", so I added it to Atacama. 💡 I also added server-side "wordlist" and "audio" APIs, but those have been migrated. But, the stat tracking has remained; a feature entirely unrelated to blog software.

in addition to "word" stats, we have grammar interstitial views and user config data on Atacama as well. ⚔️ well, actually, it's a different process, though the same monorepo

There is much talk about whether LLMs prefer a monorepo or microservices.

The answer is, generally, it doesn't matter. You can run an LLM across multiple Git repositories.

Having the iOS and web 🔥 and Android apps in the same repo is a slight convenience for a one-person development team. But would probably become large and cumbersome later on.

As far as the "Ralph Wiggum" / "Gas Town" philosophy ⚙️ roughly that you can have an agent that takes every React/Swift change and applies it to Kotlin ... I haven't gone that far yet. Other than "you can't do that on a $20/month subscription", I have no thoughts yet.

more TTS woes Tech

2026-01-27 23:00:13

https://github.com/DigitalPhonetics/IMS-Toucan

Another text-to-speech platform. Supposedly supports thousands of languages.

But: the audio quality is too metallic, the diction is too blurry.

the pattern of LLM work systems LLM

2026-01-26 01:00:22

Claude seems to be standardizing on a new "agent session" method, and I think I like it.

Step 1: Design a plan.

Step 2: Write the plan.

Step 3: Forget everything other than the plan.

Step 4: In parallel, execute the plan.

firmament words Miscellany

2026-01-23 20:24:41

My list of "firmament words" ⚙️ words that are too difficult to define without already understanding language at an advanced level, or that are so fundamental they are often embedded in grammar rather than stand-alone words from a few years ago:

Click title to read full message...

letter to an itinerant preacher Religion

2026-01-19 05:16:29

I met a man who carried a Bible everywhere he went, he said that he walked with Jesus.

He did not call himself a preacher, but he talked mostly in Bible verses. I took no offense at that, but my romantic partner was somewhat agitated by it.

I must agree with her on one count: he did use a lot of words to say very little. He seemed to have taken inspiration from a certain type of low church ⚙️ "High Church" is the bells-and-smells formal liturgy of an ancient and hierarchical church. "Low Church" is just a man with a bible and a voice. preacher, who can spend an hour talking about six lines of the Bible 💭 the Catholics have 3 readings in their Sunday services. the Jews, never to be outdone, do seven ... in the original Hebrew. Many of the Protestant denominations can only find time for 1 reading, and not say very much interesting in that time.

He was of a persuasion that suffering leads one closer to the LORD, so one should strive to live a life full of suffering. This may not be as wrong as some readers may think it is, but I find it the conclusion of flawed logic.

It may be true that one must suffer in order to know the LORD.

It may be true that the LORD's presence is more easily reached by those in suffering.

But one must not treat it like opiates; living for nothing but the joy of suffering.

And one must not reach the point where one loves the suffering more than the LORD.

There are those who are called to a life of asceticism. But it is best if they know it comes at a cost; to themselves and those around them.

One might think that it is good that they live a life away from others; a hermit in the woods, or at least a celibate monk in a mostly-silent commune.

✨ of those things that cannot be spoken-of: do not speak of them.

some translation troubles (part 3) Miscellany

2026-01-18 19:34:24

Done. Removed 10 polysemous prepositions:

┌─────────┬──────────────────────────────────────────────────────────────────┐

│ Removed │ Why │

├─────────┼──────────────────────────────────────────────────────────────────┤

│ on │ surface vs temporal ("on the table" vs "on Monday") │

├─────────┼──────────────────────────────────────────────────────────────────┤

│ at │ location vs time ("at school" vs "at noon") │

├─────────┼──────────────────────────────────────────────────────────────────┤

│ for │ recipient vs duration vs purpose │

├─────────┼──────────────────────────────────────────────────────────────────┤

│ by │ agent vs proximity vs means │

├─────────┼──────────────────────────────────────────────────────────────────┤

│ over │ spatial vs quantity ("over the fence" vs "over ten") │

├─────────┼──────────────────────────────────────────────────────────────────┤

│ into │ movement vs transformation ("into the room" vs "turn into") │

├─────────┼──────────────────────────────────────────────────────────────────┤

│ against │ contact vs opposition ("lean against" vs "fight against") │

├─────────┼──────────────────────────────────────────────────────────────────┤

│ behind │ spatial vs support ("behind the house" vs "behind the project") │

├─────────┼──────────────────────────────────────────────────────────────────┤

│ before │ temporal vs spatial/formal ("before noon" vs "before the judge") │

├─────────┼──────────────────────────────────────────────────────────────────┤

│ after │ temporal vs politeness ("after lunch" vs "after you") │

└─────────┴──────────────────────────────────────────────────────────────────┘

some translation troubles (part 2) Miscellany

2026-01-18 18:24:13

Different Words (real semantic choices)

GUID: A05_025

English: strong

data/: 強大 (powerful)

wordlists/: 强壮 (physically strong)

Notes: Different nuance

────────────────────────────────────────

GUID: A05_029

English: nice

data/: 好 (good)

wordlists/: 友善的 (friendly)

Notes: Different meaning

────────────────────────────────────────

GUID: C99_004

English: with

data/: 和

wordlists/: 跟

Notes: Both valid

────────────────────────────────────────

GUID: C99_016

English: then

data/: 那時候 (at that time)

wordlists/: 那么 (then/so)

Notes: Different usage

────────────────────────────────────────

GUID: C99_017

English: that

data/: 那

wordlists/: （用于引导从句）

Notes: wordlists has grammar note

────────────────────────────────────────

GUID: D07_004

English: often

data/: 經常

wordlists/: 常常

Notes: Both valid synonyms

────────────────────────────────────────

GUID: N01_063

English: everyone

data/: 大家

wordlists/: 每个人

Notes: Both valid

────────────────────────────────────────

GUID: N02_005

English: cow

data/: 牛 (cattle)

wordlists/: 母牛 (female cow)

Notes: wordlists more specific

────────────────────────────────────────

GUID: N02_012

English: whale

data/: 鲸

wordlists/: 鲸鱼

Notes: wordlists more colloquial

────────────────────────────────────────

GUID: N02_013

English: tiger

data/: 虎

wordlists/: 老虎

Notes: wordlists more colloquial

────────────────────────────────────────

GUID: N03_009

English: neck

data/: 颈部 (formal)

wordlists/: 脖子 (colloquial)

Notes: Different register

────────────────────────────────────────

GUID: N06_010

English: cheese

data/: 奶酪 (mainland)

wordlists/: 起司 (Taiwan)

Notes: Regional difference

────────────────────────────────────────

GUID: N06_017

English: orange

data/: 橙子

wordlists/: 橘子

Notes: Different citrus fruits!

────────────────────────────────────────

GUID: N06_029

English: yogurt

data/: 酸奶 (mainland)

wordlists/: 优格 (Taiwan)

Notes: Regional difference

────────────────────────────────────────

GUID: N06_032

English: pickle

data/: 泡菜 (Korean style)

wordlists/: 腌黄瓜 (pickled cucumber)

Notes: Different foods!

────────────────────────────────────────

GUID: N06_035

English: mayonnaise

data/: 蛋黃醬

wordlists/: 美乃滋

Notes: Regional difference

────────────────────────────────────────

GUID: N06_053

English: pineapple

data/: 菠蘿 (mainland)

wordlists/: 凤梨 (Taiwan)

Notes: Regional difference

────────────────────────────────────────

GUID: N06_061

English: cabbage

data/: 捲心菜

wordlists/: 高丽菜 (Taiwan)

Notes: Regional difference

────────────────────────────────────────

GUID: N06_064

English: broccoli

data/: 西兰花

wordlists/: 花椰菜

Notes: 花椰菜 is actually cauliflower!

────────────────────────────────────────

GUID: N06_071

English: turnip

data/: 蘿蔔 (radish)

wordlists/: 芜菁 (turnip)

Notes: data/ has wrong word

────────────────────────────────────────

GUID: N08_007

English: phone

data/: 电话 (telephone)

wordlists/: 手机 (cellphone)

Notes: Different devices

────────────────────────────────────────

GUID: N14_009

English: plastic

data/: 塑料 (mainland)

wordlists/: 塑胶 (Taiwan)

Notes: Regional difference