They can both be bad.

One way in which automated drones might be considered bad, is (if) they cannot accept surrender - but are used in scenarios where human operators could.

"No quarter" is a war crime.

This is a much more difficult distinction to make than you're letting on. Cruise missiles offer no quarter, but manually operated drones might (though there is often no way to capture the opponents). The question is what is the difference between the two weapons systems...

Drones might hunt down enemies running away from the target site, while a missile would only destroy the target - and those not abandoning their post?

What a fun system we have set up and continue to be trapped in

In addition - the docker compose example doesn't set up any data volumes for the postgres instances - that might be considered a bug?

Then again, sharding on a single host probably isn't very useful anyway - but it might work with docker in swarm mode?

The docker compose example is just a demo. I don't know anyone who runs Postgres with docker compose / swarm in prod :) But yes, happy to add volumes so it seems more real.

Yep:

https://downdetector.ca/status/googlegemini/

Maybe take some inspiration from wap?:

https://en.wikipedia.org/wiki/Wireless_Application_Protocol

Although with supercomputers in wrist watches, I'm not sure we need a new standard - html and css works fine across devices - if used with some care?

Yes, I've used WAP on my Nokia phones. I would really like to bring something from the Symbian era, and covered J2ME in a series of posts from the days before: https://inavoyage.blogspot.com/2026/06/how-about-new-java-ba...

Also, https://en.wikipedia.org/wiki/Ajax_(programming)

I came across this as a Facebook memory today, and saw it had a fairly recent turn on hn a couple of years ago:

https://news.ycombinator.com/item?id=39358317

But clearly that was before LLMs captured the zeitgeist - I'd be curious to how people see it today - I'm sure a few people have parts of this (or equivalent) in their AGENT.md or similar?

I also wonder how the last part holds up:

> 80/15/5. Spend 80% of your time on low-risk/reasonable-payoff work. Spend 15% of your time on related high-risk/high-payoff work. Spend 5% of your time on things that tickle you, regardless of payoff. Teach the next generation to do your 80% job. By the time someone is ready to take over, one of your 15% experiments (or, less frequently, one of your 5% experiments) will have paid off and will become your new 80%. Repeat.

Also, reading that recent discussion on hn - it's remarkable how much LLMs and AI has changed the discourse in a short time.

While not trying to recreate the infamous dropbox comment - if you already have Claude code, are on Linux - can't Claude write a cronjob/systemd task that invokes itself for you?

I could write a program that does this of course, but interpreting the current state of Slack threads is not something a Python script will be able to do without involving another LLM. I automated and script what I need or want to automate and script already, but for things like this where understanding of language is useful, I leave it to the slop machine.

Things like "this is a holiday in country X but only for people living in province Y except for in town Z" are massive pain to script. Plus, if the issue tracker and source control automation were working correctly, I wouldn't need to read the status of both to get a good understanding of the situation. Any time scripting there should probably be spent (by someone else) on fixing the problem in the first place.

When Claude eventually doubles or triples the token cost to stop hemorrhaging money, I'm going to lose these scripts and I won't be upset about it in the least. But until then, my "somewhat understanding of context" script-but-not-really setup is proving quite useful.

I meant more like:

    0 8 * * 1-5 claude -p "Fetch my unread emails from the last 24 hours, identify urgent items, and provide a bulleted summary." >> ~/desktop/daily_email_summary.txt

(Courtesy of Gemini, not Claude code, as I'm on my phone).

Now, obviously - you might want something a little more elegant; but my point was that if you already grant Claude tool access to your email, slack etc - then it should be trivial to wrap it in a script, and run that from Cron.

I wouldn't do that; I don't trust Claude code with access to my mail (nor would I trust Claude desktop - but I don't use it anyway).

But, if you do trust Claude to read your slack and email, I don't see why Claude code couldn't do this for you almost out of the box?

So use RDP?

https://www.xrdp.org/

(Or x forwarding over ssh, or waypipie if you only need to access a gui application, not a desktop).

Interesting write up!

Have you been able to extract libraries or tools from this project yet? If so how was that experience?

That is, do you see yourself releasing a metric harness, or sub-projects that are equivalent of ActiveRecord, zod, or similar open source tooling that frequently originate in a large in-house project - and then is exported out as a stand-alone toll, utility, library or framework?

Because while ai can reimplement minor tools, it's utility entirely depends on the existence of solid tools, libraries and frameworks.

I'm using beeper - and it really lowers the mental overhead of tracking messages for me - I have some people on signal, some on messenger, some on sms, some use dms on discord.

It's great to have a single app that shows notifications and tracks conversations.

Much better than having to try and remember if my conversation with "Tom" was via sms or signal or something else; he might have a messenger account but not use the app - doesn't matter - I just open beeper and find the last conversation and continue from there.

Ed: I don't use beeper or messaging on desktop - so Franz is DOA for me.

Which is a shame - it looks like a solid product.

It's back up again - so far no comment on the blog:

https://blog.neocities.org/