Published

All published posts

2457 posts latest post 2026-04-19
Publishing rhythm
Apr 2026 | 40 posts

We f&#ing said @pype.dev, well f&#ing said. I think a lot of us are feeling this, we’ve pitched our brain into a bucket and we are no longer stretching it in the same way. We still work in similar ways of old, with new ways of turning off and saying yes a bunch of times. the best thing I can hope for is that as things get better we have fewer yes loops, and more architectural design debates and deep thoughts. But I fear deep thoughts are gone to the way of “research the leading 10 frameworks and pick the best one for this project.” and letting the clankers do the deep thinking. Its signing us up for a weird distopia.

I think a lot of us wish we could undo what has happened and go back to actually understanding what we are doing, but the world has changed, and if you are building average shit, like the average person, using models trained on average people doing average shit you cant keep up anymore.

I’m in step with @pype.dev here, I really want beads to work for me, but my systems for infra/platform work are all over the place, not one repo. I’m considering trying the BEADS_DIR env var but idk if it fits my workflow. For now, similar to @pype.dev, I am rocking my own home vibed solution that I’ve intentionally put little effort in and its working great and I expect it to be broken and not working with the latest harnesses and models within a few months anyways, cause there is no predicting this train.

oof, outage on the homelab during vacation, brutal. I can think of a couple of similar solutions to what @pype.dev has done to tailscale in, but I’m not sure that I could do this remotely. On one hand I’m so glad that cloudflared just takes care of certs on the other hand this really brings a gap in my understanding of what the heck I would do if it were broken.

An untested DR plan is not a DR plan.

An untested backup does not exist.

Vibe coding is going so far into the news sphere now that Adam Savage even weighs in with perspectives from someone who has built a life around building things with his hands, keeping up with new making techniques, discovering old techniques as they combine with new. He talks about 3d printing reviving his love of the pantograph as one automation technique eases the most difficult part of another.

Lets Land The Plane

Part of @steveyegge 's gastown/beads is a prompt "Lets land the plane". It's very straightforward forward and what any sane human would probably do before finishing work, except the last part. The "generate a handoff prompt for the next session" was not something I've put much thought into. But now that I juggle 6 sessions at a time and often end up with 20 sessions open because I don't want to close them and loose the last bit of context. This is what I need to keep from crippling my laptop memory from all of these stale sessions hanging around. ![](https://dropper.waylonwalker.com/file/b75a3a4d-679c-415d-9d14-231b0f75e0ff.webp) Taken from https://ianbull.com/posts/beads
View

I’ve been having issue with my keyboard disconnecting to my main desktop for awhile. Today I got a cheap bluetooh dongle in and am giving it a run this week to see how things go. The first step was to move it to the new adapter. I’ve never had multiple adapters installed so this was a new to me process.

I was able to do it all with the same keyboard, It did require some juggling between usb and bluetooth modes pluging and unplugging, two keyboards would be simpler to reason about.

I can’t be bothered to change my brain to think about this machine on a different zmk profile it is of absolute importance for it to remain on the same profile, otherwise this would be a simple bind to another empty profile.

I did it with bluetoothctl, I’m sure it could have been done with a gui like blueberry or blueman.

...

I love the level of thought that Jim has put into these changes and making sure that urls don’t change. I’ve got a big change in flight to my main site and this is one of the reasons that I’ve been sitting on it so long. I want to make sure urls arent broken, redirects work as they should, and there are no 404’s from existing urls. Currently the new version only exists on a separate deployement https://go.waylonwalker.com/

I also added the ability to “shuffle” between posts. This is mostly for myself. I like to randomly jump through notes I’ve published in the past for reoccurring inspiration

Love this idea and have it on my new site already as well, and have really enjoyed using it by pressing it a dozen or so times over the course of a few sessions. It highlights that I have too many posts like stars and thoughts and I should do some weighting to main posts. mine is at https://go.waylonwalker.com/random/

Does anyone think fast-code will continue to pay the same salary? The answer isn’t to switch your brain off during your McCode shift and write a poem after work. Your job will be replaced by a Banglasdeshi slop-shop if AI improves (which is inevitable, apparently). Possibly the same sweatshop that loomed my £3 T-shirt. The Luddites didn’t accept their fate so easily.

David has some good points here, but I’m feeling the opposite direction a bit. Execs have always liked keeping the PM’s and the people steering the ship close by and were willing to farm out more and more grunt work. It feels like we are in a weird phase where there used to be a big group of people paid to write code. A few of them are exceptionally good at it and will remain. There will be a need for these people everywhere. Somehow we still need people hand editing assembly code optimizations, fortran, and cobol today. Those industries largely moved on, but a few great ones remain. I think this fast-code slop factory is going to be a short forgotten time in history, but no one yet knows what’s next. We are all waiting to find out. Just with anything there is still value in doing it by hand and...

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.
View

Ping 38

When agents do the work its harder to recognize a dead end.
View

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.
View

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.
View

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.
View

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.
View

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.
View