Wait, Lidarr also has broken metadata search?

Lidarr does an alright job of it.

The backlog is fantastic! Great explanations and examples of manufacturing and design choices.

You could step up a level and use btop! More numbers!

So many come out of school with Matlab experience. I get them started with python. They brush me off. Then the license server goes down. Welcome to open source grasshopper! I should make a meme about this and put on my door…

I have to take a breath whenever I find an F77 file. Prepare for a lack of objects!

I prefer dockge for putting all of my compositions in one place.

Let me know if you hit issues. It was a very thrown together thing that is very lacking in customization without hacking python logic together.

I duct taped together some API calls and a config file to get some smart playlist features. I find it very helpful for the slow pace I listen to some podcasts. I have it set up to put daily and weekly episodes first and then serials. Super niche , but it’s just how I like to listen to my podcasts. https://github.com/TunaLobster/PyAutoABSPlaylist

I think that is just wildly amazing that printer drivers in Linux so often just work. I plugged in a wireless printer the other day and the hardest part was connecting it to the network. Once that was done BOOM Ubuntu found it and I could print. Those driver maintainers are doing a great job!

Like mDNS?

The blue sponges that ate for non stick are softer than the normal green ones. The rough side of the blue ones are safe for non stick assuming your aren’t giving it everything you’ve got.

These ones:

I dive into Fortran77 code regularly. Sweet mother of Neptune! All caps and such short variable names!

Hello!

I keep a set of notes for each day. I have 2 journals. One for work and one for the rest of life. I use the same system in both. I took the Bullet Journal system of notation and added a few more to handle some edge cases that I encounter occasionally. The system works with any size of journal or pad of paper. I often drop sketches and diagrams in the middle of meeting notes. Actions get carried from day to day. Walk up requests get written down. I know when something was handed off to someone else. I like it! Totally not for everyone though. I skip the monthly and future planning parts. I would probably use that part if I was doing schedule management. Rapid logging is the part that I use all the freaking time.

https://www.tinyrayofsunshine.com/blog/bullet-journal-guide

Notes for small code projects/my network set up get tossed into .txt files. Eh. It gets the job done and there is only one place that file can be and it is the most up to date. Assuming I updated after the last changes. Which is a coin toss when things are busy. Comments in the code are a far more common way for me to keep track of what is happening.

I think the other aspect is the easy to follow discussion threads. IMO it’s the cleanest way to show and follow branching discussions.

Proxmox can be a bit of a bear to setup. The documentation is not very approachable for new users. It uses a lot of terms without definition which is a deadly sin of technical writing IMO. Guides for getting an Ubuntu Server VM setup vary wildly and often recommend outdated settings.

I’m totally on board with using it though. It eliminates the need to start from scratch when migrating to newer hardware.

Set up your favorite Linux server distro and then go ham on setting up docker (dockge is a great tool to introduce compose).

You’re completely overthinking it. I keep white separate. Colors get their own basket. Denim goes in a separate piles after it really smells (it honestly shouldn’t be washed very much). Towels get their own load due to shedding. Sheets sometimes go in with the colors.

I do everything on cold. I use the plainest of plain detergent. If there’s a smell in polyester or nylon clothes I’ll put in some Clorox 2.

Dryer on low or medium until mostly dry. I’ve got a fancy one with a moisture sensor that actually works so I let that determine how long. Usually 25-30 minutes.

Citation: https://www.nytimes.com/wirecutter/reviews/wirecutter-show-podcast-20240821-better-laundry-secret/

Assuming your mean in the US. Depends on the state.

Then you ask questions about what the past person could possibly have been thinking. You wonder what logic path brought them to create the code this way. You check git blame. It was you.