{"channel":"atacama","content":"the Trakaido stats server is in the Atacama repo largely by accident.\r\n\r\n <<< 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. >>>\r\n\r\n----\r\n\r\nin 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)\r\n\r\n----\r\n\r\nThere is much talk about whether LLMs prefer a monorepo or microservices.\r\n\r\nThe answer is, generally, << it doesn't matter >>. You can run an LLM across multiple Git repositories.\r\n\r\nHaving 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.\r\n\r\n----\r\n\r\n <<< 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. >>>","created_at":"2026-01-28T15:42:25.228556","id":737,"llm_annotations":{},"parent_id":null,"processed_content":"

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

\n

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. \ud83d\udca1 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.

\n
\n

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

\n
\n

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

\n

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

\n

Having the iOS and web \ud83d\udd25 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.\r

\n
\n

As far as the \"Ralph Wiggum\" / \"Gas Town\" philosophy \u2699\ufe0f 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.

","quotes":[],"subject":"thoughts on the Trakaido API"}