Check out basecamp [1] and their project fizzy [2].
Kanban as it should be. Not as it has been.
References:
[1]: https://github.com/basecamp
[2]: https://github.com/basecamp/fizzy
Publishing rhythm
-
What a heart breaking video to listen to. I’m trying to do a better job of being positive right now. I’m trying to look at the world in what I have control over (not much more than my attitude about it). AI is killing so much right now I’m trying to look at it as the good tools the engineers made it to be. Ownership is dying around every goddamn corner. Hats off to Edison, this guy gets it. We need more companies like this taking a stand for the average person who wants to make it out there.
-
What a great campfire story Casey stumbled into. Whether any of this is true few will ever know, but its very reasonable that a race condition and a stalled job to apply configuration caused by someone who left the company 10 years ago caused an outage. I find it hilarious that they call this guy he answers, yup I still know the password, but how do I know you’re legit, I’m not just handing out the password. Casey did a stand up job telling this story.
-
Linus is Techbrophobic [1] like the rest of us. This is such an unexpectedly mild take from him. I expected some threat to the mother of the vibe coder, but he gave a pretty great middle of the road take. The industry sucks, it smells off, we know a lot wrong with it, it feels like theres a lot more wrong than we know. But the tools that its making are really good when used in the right ways. They are not a replacement for anything, they are assistive. They can lift someone from not knowing how to code to making a small webapp for their use. Someone who wants to write backend and give them a decent front end, someone who whats to write front end and give them a decent backend.
Great take from someone with more experience than most can ever dream of having, worth a listen.
References:
[1]: /techbrophobic/
gpus are awesome and I need one for Bambu Studio to be usable in a
distrobox. Adding the --nvidia flag to distrobox create bind mounts the
nvidia /dev/ devices and sets up the necessary environment variables. Once
we are in there are a couple of packages to install to make it work.
distrobox create --name bambu-studio --image archlinux:latest --nvidia
distrobox enter bambu-studio
sudo pacman -S nvidia-utils lib32-nvidia-utils vulkan-icd-loader
nvidia-smi
glxinfo | gprep OpenGL
sudo pacman -Syu --needed base-devel git
git clone https://aur.archlinux.org/paru-bin.git
cd paru-bin
makepkg -si
paru -S bambustudio-bin
bambu-studio
distrobox-export --app bambu-studio
Check out garbage-day.nvim [1] by Zeioth [2]. It’s a well-crafted project with great potential.
Garbage collector that stops inactive LSP clients to free RAM
References:
[1]: https://github.com/Zeioth/garbage-day.nvim
[2]: https://github.com/Zeioth
snow-fall Web Component—zachleat.com
A post by Zach Leatherman (zachleat)
Zach Leatherman · zachleat.com [1]
This is a very fun way to add some whimsy to your site, added it to mine immediately when I saw it. This is what digital gardens are for, Fun, entertainment, and self-exxpression.
References:
[1]: https://www.zachleat.com/web/snow-fall/
-
This ball vise Idea is incredible and I want one. Its a heavy workholding unit that can accept a variety of tools and manipulate things to a lot of angles while working on them. This looks really good for painting miniatures soldering or generally working on small 3d printed parts that I do.
Git
Git is a version control system for tracking changes in source code during software development. In the beginning there were many, some were licensed. As...
git worktrees are needed
git worktrees are goated, and must be leaned on moving forward.
The Wrong Reasons To Run Kubernetes In Your Homelab
Running kubernetes in your homelab [1] is complex, time consuming, there are almost
no docs to help you (homelab focused docs for things you want to install), and
nothing is copy paste. You have to make everything happen yourself.
The Wrong Reasons To Run Kubernetes In Your Homelab # [2]
- I run compose and think kubernetes is the next logical step
- Techno Tim runs it
- I heard it’s what cool kids do
- Kubernetes BTW
- Talos Linux looks cool
- I found a cool helm chart on GitHub
- I need scale
There are also The Right Reasons To Run Kubernetes In Your Homelab [3].
I run compose and think kubernetes is the next logical step # [4]
No it’s not. It’s much different than running docker, compose, swarm. It’s
meant for scale, it’s complex, it’s made for enterprise, not your local
development or your homelab. It can do these things, it can do them quite
well, but it’s not the target audience.
Techno Tim runs it # [5]
I heard it’s what cool kids do
You need to rethink who the ...
my home row
My home row layout. It's not quite home row mods.
https://dropper.waylonwalker.com/file/fd74f80e-ff5e-4548-8419-bd407144bb6c.excalidraw
I got the kubernetes in my basement autism
What flavor of autism did you guys get, I got the kind where I run kubernetes in my basement.
https://www.youtube.com/shorts/5Cac-cf5MOE
The k3s system-upgrade controller is a fantastic tool for upgrading k3s automatically. It has done a fantastic job for me every time I’ve used it. Today I ran it on a cluster that needed to upgrade several minors and I learned that the controller does not pick up on changes to the channel url if you change from minor to minor.
The solution I came up with was to name the plan with the version it supports. Then on each patch upgrade, change both the plan name and the channel. I use gitops with argocd, it automcatically cleaned up old plans, created new plans, and the system-upgrade-controller picked up the plan and started applying immediately.
# Server plan
apiVersion: upgrade.cattle.io/v1
kind: Plan
metadata:
name: server-plan-v1.33 # <- This is important if you want to change the channel name
namespace: system-upgrade
spec:
concurrency: 1
cordon: true
nodeSelector:
matchExpressions:
- key: node-role.kubernetes.io/control-plane
operator: In
values:
- "true"
serviceAccountName: system-upgrade
upgrade:
image: rancher/k3s-upgrade
channel: https://update.k3s.io/v1-release/channels/v1.33
---
# Agent plan
apiVersion: upgrade.cattle.io/v1
kind: Plan
metadata:
name: agent-plan-v1.33 # <- This is important if you want to change the channel name
namespace: system-upgrade
spec:
concurrency: 1
cordon: true
nodeSelector:
matchExpressions:
- key: node-role.kubernetes.io/control-plane
operator: DoesNotExist
prepare:
args:
- prepare
- server-plan
image: rancher/k3s-upgrade
serviceAccountName: system-upgrade
upgrade:
image: rancher/k3s-upgrade
channel: https://update.k3s.io/v1-release/channels/v1.33
I’d love to see a better way if you have a way to upgrade through minors, or manually control the minor of your cluster let me know.
Deleting Code for Performance
The one where I clean up an asynchronous mess.
dbushell.com · dbushell.com [1]
I did not realize that David’s site was built on a homegrown Static Site Generator. As someone who also does this myself I appreciate the effort. I build my site on markata [2]. It started as a project to learn a set of tools and has become a project that I depend on everywhere and cant put down. It’s a great tool, but you probably shouldn’t use it. Anyways, I feel this really shows on David’s site. His site is filled with custom features that make it very unique, one off, and always a pleasure to read.
References:
[1]: https://dbushell.com/2025/12/04/deleting-code-for-performance/
[2]: /markata/