Something I hadn't really thought about is that is to learn and grow, you NEED to struggle. It needs to be hard, to truly learn something. This is why making mistakes is the best way to learn.

When my son asks ChatGPT to write him a program, it will happily oblige. While we can walk through that program line by line and I can explain him how it works, he's not going to learn much from it.

For him to learn, he has to give it a shot himself. Get a syntax error, read that error precisely, understand it (and not feed it back to ChatGPT) and then fix it. Then get another error, read it and fix it. Rinse and repeat.

Making things as easy as possible is not (always) the goal.

However I can highly recommend the FreeOTP+ fork which has some other nice features, but crucially, saves and loads data correctly.

inotifywait --monitor --recursive ~/.config

"How to interpret FFT output" is the aerospace version of "How to center a div"

This time it's #Debian with #Docker. I used to avoid containers, preferring to run services directly instead. But setting up backups made me appreciate the separation between the application data in image and persistent state in mounted volumes. The final piece that convinced me is the ability to self-host my own container registry with @forgejo@floss.social

I'm doing the initial setup through #Ansible (learned from @notthebee@tilde.zone), but specific applications are managed via dockge. The ambition to do every adjustment through playbooks burns out really fast when working with a single instance.

Oddly tempted to try to switch to #Vim (realistically @neovim ) again for code editing. And switching on vim mode in @silverbulletmd

Trigger: the realization that anything not purely open source (like VS Code) eventually #enshittifies

Writing a single bash script that turns a clean #Debian install into an opinionated #selfhosted setup (the one that I use myself) with:

* #Docker
* #dockge as web UI for managing docker-compose stacks
* @tailscale setup to expose deployed services with TSDProxy as separate TS domains
* Restic for data backups

Anybody interested?

This is what #FOSS promises to be, and it does feel nice to actually do it.

I did enjoy the ease of setup of TkInter, and compatibility with Matplotlib, but I was missing the simplicity of immediate mode libraries. In trying to emulate these, now a few callbacks trigger "given this dataclass with state, the widgets should look like this".
The micro-management gremlin is whining that it's repeating useless work, but more importantly the window is complete and I can go on with the experiment.

Alt...

Screenshot of a basic graphical application with settings, showing plots of generated signal to its side.

Thanks @grunfink@comam.es for the #snac server, @stefano@bsd.cafe for the blog posts that pointed me to it, @voron@snac.nya.pub for the theme and @manton@manton.org for motivating me with your book

Czyniąc cokolwiek, człowiek prawie nigdy nie wie, co właściwie czyni – w każdym razie nie wie do końca.