-
Prime on Big A they make a really great mix. I really like primes perspective on the layoffs here. Adding in an ops perspecive a bit here. Maybe inspiring a full level post. infra, ops, sre roles are incentivised to keep uptime, that is your goal in these roles. Idk how it works on big products, its probably more greased, higher stakes, more well thoguht out, more well discussed. In my role for many small internal applications developers constantly use my platform different and find new edge cases that we never expected to hit. Depending on my week I’m either the team blocker and I’m fighting fires all week making sure new releases are getting out and stay running while everything is breaking, or I’m tending to the fire lanes, predicting the new edges, looking at previous outages and asking myself how do we never see this category of failure again. I think AI is really good a enabling both of these. I think you can probably run a leaner team with AI on the latter half. AI is really good at implementing things consitent (if you are careful) and fast. But when shit hits the fan, you still need the people who know the systems to get things back up quickly and prevent a cascade o...
Publishing rhythm
-
What a great way to start a Wednesday morning with a fresh brand new tiny desk concert with the Foo Fighters. The killed it, love the classics.
Hollow Knight Theme Scaffold
Alternate markata-go shell with 9-slice panels, textured surfaces, and palette-driven chrome.
agents are never done
Agentic coding has this nice trick of letting you bang out a project in an
afternoon, something complex that would have take some real time to implement,
not just some rounding error that can slip right in between the jira board.
Then it will be perpetually never done. There will always be bugs and thorns
rear their head up, new features no one ever thought of, and now no one really
has to think much about beyond having the idea.
This part of software engineering has always been here, its the root of the
never complete 200 side projects. But now it feels like fuel has been poured
on the fire, like we can get more done than ever. But we are tricking
ourselves, these projects will never be “done”. There’s always more to add.
Without feeling any of the pain of implementing it yourself, why not just keep
adding new features forever. This is the mentality that is crushing me right now.
It pulls at your token anxiety like crazy. You look at the usage board and you
are almost cooked so y...
-
I havent used windows in years at this point, but I feel this on the products I am forced to use for work. Basic features are not right, kinda work most of the time. New features, ai integrations, new skin/design, but still teams can’t use my system mic appropriately yet every other app does.
Also feel this computers have not got significantly better since around getting ssds. Yes they are better, but not at the same rate of being obsolete every two years. I hope we hit local model land and it flips this a bit, not in quite the obsolete every two years range, but some new hardware actually lets you do meaningful more new things.
How to Install Silksong mods on the Steam Deck
Having a tough time with Hollow Knight: Silksong? These mods will help.
Long Play Tech · longplaytech.com [1]
Really good tutorial for how to mod silksong on the steam deck. We just did this on my son’s steam deck. I’d add a reccomendation to map ~ to a back button like L4. I think this guy was docked with a keyboard.
References:
[1]: https://longplaytech.com/posts/how-to-install-silksong-mods-on-the-steam-deck/
Building For The Future
This afternoon, we sent the following email to our global team. One of our core values at Cloudflare is transparency, and we believe it
The Cloudflare Blog · blog.cloudflare.com [1]
Full salary for the rest of the year after being let go. As much as this sucks as much as the job market sucks. It’s good to see that these companies laying off huge numbers during good times are trying to take care of those they brought on.
References:
[1]: https://blog.cloudflare.com/building-for-the-future/
Programming Sucks
stilldrinking.org [1]
Absolutely incredible, will fill some notes later
References:
[1]: https://www.stilldrinking.org/programming-sucks
Programming Still Sucks. — Writing
Sorry Peter. — I'm at a birthday party, and while most people here also work in tech, there's always a Guy with a Real Job. You know, a physical job, building some or other thing people need. And...
stvn.sh [1]
Absolute banger of a post, this is the time we are living in. Explain “are you afraid AI is going to take your job” to a non tech blue collar worker. Broken over promises, greed, and projects mismanaged by leadership who has no idea what the day to day work actually does and how critical it is.
I’m not quite in Sara’s position, but I feel something shielded by half of this working deep inside of a non tech part of a non tech company leading a very small rag tag team with get shit done attitude.
But I feel it, I see colleagues hit by these blasts.b I get clipped with shrapnel from some of the largest blasts. But nothing as significant as I see many others hit with
References:
[1]: https://www.stvn.sh/writing/programming-still-sucks-fqffhyp
I just learned that forgejo has a push to create repo feature and it is a gamechanger. Upon first try it didn’t work, with just a couple of environment variables I was up and running with push to create.
notify.wayl.one on main is 📦 v0.1.62 v3.14.4 NO PYTHON VENV SET USING SYSTEM NVIM
❯ git remote add origin https://git.waylonwalker.com/waylon/notify.wayl.one
notify.wayl.one on main is 📦 v0.1.62 v3.14.4 NO PYTHON VENV SET USING SYSTEM NVIM
❯ git push
remote: Push to create is not enabled for users.
fatal: unable to access 'https://git.waylonwalker.com/waylon/notify.wayl.one/': The requested URL returned error: 403
So I added the following environment variables.
Author: Waylon S. Walker <[email protected]>
Date: Wed May 6 21:56:53 2026 -0500
enable push to create
diff --git a/k8s/forgejo/deployment.yaml b/k8s/forgejo/deployment.yaml
index d77daab..9346763 100644
--- a/k8s/forgejo/deployment.yaml
+++ b/k8s/forgejo/deployment.yaml
@@ -91,6 +91,10 @@ spec:
value: "0.0.0.0"
- name: FORGEJO__server__HTTP_PORT
value: "3000"
+ - name: FORGEJO__repository__ENABLE_PUSH_CREATE_USER
+ value: "true"
+ - name: FORGEJO__repository__ENABLE_PUSH_CREATE_ORG
+ value: "true"
- name: FORGEJO__database__DB_TYPE
value: postgres
- name: FORGEJO__database__HOST
https://github.com/WaylonWalker/homelab-argo/commit/b2e953bc12
Tried again, and it just worked!
notify.wayl.one on main is 📦 v0.1.62 v3.14.4 NO PYTHON VENV SET USING SYSTEM NVIM
❯ git push
Enumerating objects: 171, done.
Counting objects: 100% (171/171), done.
Delta compression using up to 12 threads
Compressing objects: 100% (169/169), done.
Writing objects: 100% (171/171), 176.22 KiB | 16.02 MiB/s, done.
Total 171 (delta 99), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (99/99), done.
To https://git.waylonwalker.com/waylon/notify.wayl.one
* [new branch] main -> main
nless is a seriously sick tui for exploring streaming data. It makes it seriously simple to pivot (U), drill in (Enter), sort (s). It leave breadcrumbs as you go and you can press q to back out.
Play with your kubernetes events. Ya, my homelab is far from perfect, dont judge.
kubectl get events -A -w | uvx --from nothing-less nless
[1]Ghostty Is Leaving GitHub
Mitchell Hashimoto · mitchellh.com [1]Found on HN: [1]discussion [2]
The GitHub tears post. I feel it, maybe not as much as @mitchelh, but I feel it.
References:
[1]: https://mitchellh.com/writing/ghostty-leaving-github
[2]: https://news.ycombinator.com/item?id=47939579