Archive

All published posts

2440 posts latest post 2026-04-21
Publishing rhythm
Apr 2026 | 41 posts
Wyatt's First Printed Cosplay Scales
Wyatt printed these sick scales today and they came out so good on first try, luckily Rhiannon already had the fabric for him and he was able to follow his passion on this project while the spark was lit.
Wreath Of Purity Acquired
By completing Broodfeast Wish you acquire the Longclaw giving you a longer range attack.
Seekers Soul
Goal The Great
Updating The Arch Iso
Wyatt is working on a new arch install and it blew up, time to update the live image.

Social Media is dead

Social Media is dead, interest media killed it long ago. I no longer feel like I'm connecting to people, creating community, having fun, learning. I feel like I'm being shoveled slop from the slop machine, I'm sure mostly create by well intentioned people just trying to make it in the world, trying to make their mark, trying to make something of themselves. The algos long lost the idea of subs and likes, and transitioned to how long you will pause on a topic. What used to be a series of recognizable faces, names, avatars, each with their own personality that I could come to learn and know who was just trollin, who was serious, is now mostly unrecognizable. Platforms have changed and fractured communities people went separate ways, not all the same ways. No one community is like it used to be, and its hard to find.
View

/carry/

I try to keep a pretty light every day carry, but it never works out, keyfobs and headphone cases end up causing more bulk than I’d like, but My EDC is no where near the bulk I had as a kid with my cargo pants decked out with everything I could possibly need.

I hold no attachment to anything in my EDC. Nothing on my person has sentimental value. Anything I carry can be lost, stolen, or destroyed at any point in time. I pick things of sufficient usable, utilitarian, quality sufficient to work. No extra fluff.

Photo taken March 2023

...

3 min read

Where Is The Tech Industry Going

Agents suck Get left behind if you don't use them Burn out if you use them too much The software world has been flipped upside down seemingly overnight. Slow at first, then all at once. It started with auto complete, to chat, to, ide integrations, to agents that would f&!^ over your repo more than it would help. Up till this point we are just little bit better and more specific than copy paste from Stack Overflow. Then in Nov 2025 models learned how to effectively use tools and do what you ask of them, sometimes more, sometimes less, but generally for the basic shit most of us make its a net positive with each iteration. Our techniques for managing work need to change. Our expectations need to change. Burnout for a lot of folks is coming.
View

Is Compaction The Issue

I saw today in work chat something along the lines of "we need bigger context windows" "compaction times are holding us back". Maybe I'm just blessed with the lack of lord jira, maybe juggle too many projects at once and they are all pretty much done when I get back. Maybe I do more long running specs and spend time making good plans that it does not matter. Anyways the point I'm getting to is that if you think that compaction is your main issue slowing you down, and 10x this if you are a manager thinking this is what is slowing down your team you **need** to look at your workflow. Not because it sucks. Not only because it could be better. Because you are signing yourself and your team up for burnout if you are sitting there watching these things run like waiting for paint to dry and firing more prompts at them as soon as they are done. It feels easy. It feels like you are going fast. Its eating more brainpower than you think, and its not getting you to your destination any faster.
View

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

If you’re into interesting projects, don’t miss out on qmd, created by tobi.

mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local

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.
View
Almost Cheesed It To Port Aquelite
Its A Trap
Collection Party Balloon
Collection L Bracket
Wyatt Hits The Gap

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, there is no need to buy new right now, especially now. I haven’t bought a new machine in years and most of my hardware is second hand cobbled together stuff, and has no issues. I’ve got one machine thats 16 years old, 2 machines at 9 years, one at 8 years. To get here they need to be repairable, designed to last, and probably no run windows as they will release something that renders them too slow or require new hardware for security that wont work.

Very interesting takes from @thdxr in this interview. A lot has been hashed out by others all over the place, but a hot take here is that code quality is higher than ever right now. Codebases are becoming more consistent than ever. If you are not starting with a good consistent base from the start you are poising your context and doomed to fail and have all the common failures of ai written code. He still reads almost every PR, and will read all of the code eventually. There are a few cases where reading the PR is not worthwhile only when its low stakes, knows that good patterns have been established and followed. He argues that someone needs to be the expert of the code and of the product still and fears that too many people not looking at prs will fail companies.

Thinking about ai productivity again

Thinking about AI productivity again. It's allowing massive amounts of work to get done, to levels that humans cannot physically type out in some cases. But not all of this work is necessarily high value work. Right now I'm working on one of the biggest PRs to an internal cli library. Probably the largest PR I've ever done professionally. It touches all of the cli, refactors every command, reaches into the business logic layers to drive deeper separation. I reaches into the common layers to drive consistency. It ensures that every command (50 or so) has similar flags, supports --plain, --no-color. It specs out contracts to ensure that data goes out stdout, any extra goes out stderr. This makes everything unix pipe friendly. There was quite a bit of research and prep that went in, that turns out to already be distilled down into clig.dev. The point is that this is all good work. It will make the product consistent, repeatable, expected, and most of all boring. Most of the time, it wi...
View
Dummy13 On A Skateboard
Tonight Wyatt gave me a dummy13 that he printed, assembled, and posed all on his own. He's printed quite a few of these in the past, and none came to this level of completion. I'm so proud of him. This one was a near flawless build with only a few mistakes, that I'd argue were poor design, small vertical pins. More importantly he was able to problem solve and use resin to fix these mistakes.
Groal The Great Fail 1
Groal The Great Fail 2

Kids are leaving the party early, not drinking, cant watch netflix without the laptop open. They are leaving the party early to check on their agents. I get it, that feeling that you need to eek out one more prompt, keep your agents running. if they arent running what are you even doing. If not you 6 others are ready to pass you up. The timeline to be first has shrunk to nothing but unachievable.

It’s wild how much of a hit Google took from killing reader, almost any time I hear about killedbygoogle, reader is the top of the list. Its the thing that we all remember being really good and the incumbants just did not match up. Somehow we are here 13 years later still bitching about it, despite it only having a 6 year run. You should probably get an rss reader, and follow some incredible people that make feeds. Most sites that produce content have the ability to subscribe over rss. Unlike @pluralistic.net, I dont read in my reader. My reader is just a list of links out to the web and I typically read it how the author intended on their site. I nod a long to Cory’s enshitified internet just as much as the next guy, I love text based interfaces, I despise the bloat that js has brought on. But I don’t believe all js is bad, I don’t turn it off, even though he has me questioning this now. News sites kinda suck, we can agree there, but its rare that a small indie web creator has fully enshitified their site with js. I don’t buy that. Sub to the feeds.

Did you even like to code?

Here's something I've been wrestling with lately. I keep hearing people come to the realization that they never liked coding, they thought they did, but secretly hated it the whole time. I dont think I've ever kidded myself about this. I like building things. I like having an idea and see it come to life. Just because I like the end product more, and that coding really was a means to an end, something I will never do again in the same capacity that I have in the past, does not mean I did not enjoy the art of solving problems by typing syntax into a file to tell a computer how to solve a problem.
View