Links from June 2026
Linus Tovalds speaks to 3d printing and increased linux commits & security disclosures due to AI.
AI is a great tool, but it’s a tool. When I see people saying 99% of our code is written by AI … 100% of their code is written by compilers, but they never say that. AI is … not changing the fundamentals. …people will use AI to generate the code that the compilers use to generate the code that the assemblers then use to generate the machine code. This is revolutionary in the same sense that we’ve seen revolutions before. AI is great, but AI is not changing programming.
Open urls from WSL using this xdg-open drop-in replacement.
I have rage quit integrating worktrees into my agentic orchestration at least three times. It’s a promising idea, having many agents work on the same repo, but is non-trivial to do and different for every repo.
For now I’m sticking to 2-3 agents on the same repo, in different areas of the codebase. Model seems to handle the other work going on, tho, Opus 4.8 appears more curious about it than others.
Really pleased to see others like Isaac Dedini experimenting the area - a great post on why “just use worktrees” is nonsense.
This is agent orchestration, but Loop Engineering is for sure a better term. My notes:
- I don’t have a requirement for scheduled tasks as yet
- Worktrees are close to impossible
- I use
assistfor skills & cli-wrapping, though I do use Claude connectors - Sub-agents - no thanks, i’ll make the deterministic thing (assist) control the non-deterministic thing (claude).
- State/memory - this is
assist backlog