Published

All published posts

2534 posts latest post 2026-06-10 simple view
Publishing rhythm
May 2026 | 57 posts

I don't want someone else running my agents

I don't want to review the pr, I dont want to fight the mass of changes clobbered across the codebase. I want to own my platform. With everything changing with agents writing more code than I can imagine in a day work looks different now. I still want to work with real people. I want to collaborate on ideas. I want someone to bounce ideas off with. I want someone else in the war room with me on launch day, or when the whole thing goes down. But I don't them slopping in my sandbox, if someone is going to be stirring the slop in my product I want it to be me. Work is feeling different now. New lines need to be drawn in new directions. Expectations are changing, the way work is completed is changing, and we are all here trying to figure out what this looks like moving forward.
⭐ mohebifar tooscut
Looking for inspiration? tooscut [1] by mohebifar [2]. Professional video editing, right in your browser. Made with Rust, WebGPU, WASM, and Tanstack Start. References: [1]: https://github.com/mohebifar/tooscut [2]: https://github.com/mohebifar

Ping 38

When agents do the work its harder to recognize a dead end.
⭐ kraanzu smassh
I like kraanzu’s [1] project smassh [2]. Smassh your Keyboard, TUI Edition References: [1]: https://github.com/kraanzu [2]: https://github.com/kraanzu/smassh
⭐ KittenML KittenTTS
I’m really excited about KittenTTS [1], an amazing project by KittenML [2]. It’s worth exploring! State-of-the-art TTS model under 25MB 😻 References: [1]: https://github.com/KittenML/KittenTTS [2]: https://github.com/KittenML

Learning to agent

All we are hearing lately is Agents are the future, something flipped around NOV 2025 with opus 4.5. It turned snake oil into action. It changed programmers will be replaced in 6 months to now. Not all of them, but probably most of us who are not extraordinary. If you fall into the camp of folks not adopting, I got no issues with that. No one is twisting your arm, well maybe your boss or cto is, thats on them. I don't mean to say this is the future as in, get in or get left behind. I mean it as this is where your other engineers probably are, the junior to mid level engineers are here. If you are not trying to meet them where they are how are you going to lead them.

Studio Ghibli Images in the Wild

I just stumbled into an image in my org chart of someone who clearly turned themself into a Studio Ghibli character in chatgpt during the small window of time that it seemed to do this for everything. Its clearly the aesthetic that It would do by default for that week, then would not do it whatsoever. I'd link it, but its from an org chart. I mostly found it interesting how we now have these recognizable artifacts from specific moments in time.

Ping 36

I feel like there's an inevitable phase to every ai/agentic worked feature/epic where you have to get in and chat with it 2025 style (except it actually works and doesn't turn your project to shit). Planning is great, planning out epics for full orchestrator's to churn for hours on is amazing, but it always leaves me with a handful of thorns multiplied by complexity level of things that I can shout a list of 6 items at a time that it can one shot. I haven't seen anyone put a name to this phase yet, so I'm going to call it the UAT phase for now and it seems like a very necessary part of the SDLC. It was important before, but feels more so now as engineers distance themselves from the implementation.

Research, Plan, Implement

I heard this term yesterday, and I think a lot of people are missing out on step 1. It's important to experiment with agents and learn what they can do well and what they cant, this changes every couple of weeks at this point. You might be spending hours planning something that could have been implemented right away, or maybe wasted time planning something that needed more research, more context engineering. Agents start fresh every session, they cant remember what you asked them to do 5 minutes ago in the other session, getting the right tokens in session is critical.
dot dockerenv
Today I learned that docker creates an empty /.dockerenv file to indicate that you are running in a docker container. Other runtimes like podman commonly use /run/.containerenv. kubernetes uses neither of these, the most common way to detect if you are running in kubernetes is to check for the presence of the KUBERNETES_SERVICE_HOST environment variable. There will also be a directory at /var/run/secrets/kubernetes.io/serviceaccount that contains the service account credentials if you are running in kubernetes.

Context Poisoning Was There All Along

I wrote some code by hand on Sunday. Sat down with my son and started building out a game in pygame from scratch. We went to google, we searched how to do something, we copy and pasted from the docs. Not because we are dumb, but because we cant remember some aspects of the pygame api. Now that these patterns are established we no longer have to google them, we simply grep our codebase and replicate the pattern. Easy right? It's funny that it took ai to coin the term `context poisoning` even though it was there all along.
⭐ tobi qmd
If you’re into interesting projects, don’t miss out on qmd [1], created by tobi [2]. mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local References: [1]: https://github.com/tobi/qmd [2]: https://github.com/tobi
⭐ ratdoux OrcaSlicer-FullSpectrum
Looking for inspiration? OrcaSlicer-FullSpectrum [1] by ratdoux [2]. G-code generator for Snapmaker U1 with Full Spectrum layer blending References: [1]: https://github.com/ratdoux/OrcaSlicer-FullSpectrum [2]: https://github.com/ratdoux

Agents cannot replace the thinking, they only amplify it

Agents cannot replace the thinking, they only amplify it. If you set the agents off in the wrong direction that's where they will go. They will sprint there faster than you can go. This is ok, its one of their advantages, they can give you signal quick. Remember if they are off in the wrong direction more research and planning is needed, and maybe a little bit more thinking on your end to steer them in the right direction.
Almost Cheesed It To Port Aquelite
Its A Trap
Collection Party Balloon
Collection L Bracket
Wyatt Hits The Gap
💭 ten year computer alexwlchan.net
Dreaming of a ten-year computer – alexwlchan alexwlchan.net [1] Great gusto here from someone looking to fill landfills less. Get more use from what they paid for. Dodge some tough times in the hardware industry. I’m going to argue that the 10 year computer is not one bit crazy right now. No idea what the future entails, if local llms get good enough to really get so useful they feel required this could easily change. One issue I had with the post as they are looking to get a machine for the next 10 years is they were so focused on themself that they missed the point. They were so focused on buying something that would work for them for 10 years that they bought something brand new rather than thinking about the bigger issue of how do we get hardware to last 10+ years. Some factor of this involves giving our devices a second life. Two things went wrong here. First it appears they they have a perfectly good imac with a broken screen. I know nothing about apple/imac, assuming that the screen is toast and unrepairable, I know you can ssh into a mac this feels like good potential for server hardware. Next they purchased a brand new mac mini. Hardware has been good for a long time,...