I've been in the habit of pushing my claude-speak to codex to improve legibility, but only if I think someone is going to read it.

- https://andreaciulu.com/ - https://www.rooperainisto.com/

You might feel differently, but I feel intention and effort being communicated here.

For those either outside computer culture, or those within who might view "craft" as virtue, automating that craft is an affront.

Right now, the "automators" (pro-AI) folks seem to be pushing that culture onto the "crafters" and naturally getting pushback.

With that said, I don't disagree with the article. Don't use more word when few work.

1) is an impossible and unproductive attitude, and

2) fails to recognize the important contribution to evolution, genetic diversity, and our immune systems that viruses introduced, not to mention the possible beneficial applications that could exist by understanding it.

Rejecting something without nuance makes you more vulnerable down the road because it prevents you from building an effective immunity. Engaging with it is the only productive way to mitigate its downsides and promote its benefits.

It honestly seems good enough that it might cannibalize Macbook Air sales.

My current goto for desktop apps is Tauri, which give us a rust backend and TS fronted (usually React). Local ML features can be easily loaded as a python sidecar. Production bundling can be a little challenging but it seems to work well so far.

Sidenote: Golang is also an amazing language for LLM use, I generally do most of my "infra" stuff in Golang over Rust, but either work fine most of the time.

I'm looking into how to structure my work to run some autonomous-safe jobs overnight to take advantage of it.

My main goal is to maximize my subscription token usage while trying to comply with the rules, but its not clear where the line is for automation so I feel like I need to be clever.

- regular development (most token use): all interactive claude mode, standard use case

- automated background development: experimenting with claude routines (first-class feature, on subscription)

- personal non-nanoclaw claude automations (claude -p): uses subscription token, but only called as needed (generally just fix something if something in my homelab infra goes does down, its set up to not fire on an exact cron time)

- other LLM based automations: usually openrouter API key, cheap models as needed

- nanoclaw: all API key based, but since its expensive I keep usage mostly minimal and try to defer anything heavyweight to one of the other automation strategies (nanoclaw mainly just connects my homelab infra with telegram)

For context: I have additional automation with scripts set up on the mini, some of them call LLMs to do things like summarizing today's news.

I have other automations that are agentic and just run "claude -p" (mainly just checks status of other jobs and fixes them automatically). Agentic automations are great because they can handle unexpected situations (at the cost of predictability). They're all sandboxed and we have control over tools for the most part. Any files it would write to are typically git-controlled so we have change records and rollback built in.

Nanoclaw acts as an agentic layer but combines it with the communication layer over telegram to make it interactive.

I use it to go through my centralized task list (currently beads in my main 'wiki' monorepo), give me nudges for todos, I can also send it pictures of say, food and it will fetch a recipe and sort it into the wiki via a general "inbox" skill (claude has it as well). Every day at 12:30 it will give me a mini "standup" of all my personal projects and todos, and once in a while will give me some thoughts based on my interests.

Its set up to do appropriate tasks with local models to keep token costs down, so far it doesn't seem to cost more than $10-20/mo, it would use less if I didn't drive it with sonnet.

I'm still experimenting with it, and trying to go slow, one thing at a time. I don't give it access to anything super sensitive yet, and try to keep it observable.

I literally did this 12 years ago based on this reasoning, its good you're trying to counter that with the next generation.

With that said, I do wish there was more discourse around systemic issues rather than the usual finger-pointing towards rival social groups. Unfortunately I feel like our language gets in the way, systems issues are more abstract, but "bad people" are more visceral and easy to talk about.

It doesn't solve the problem of general LLM dependency (at the end of the day we gotta keep our brains sharp), but any LLM-based workflows aren't all of a sudden put at risk if we set up something that depends on it.