Well, yeah - that never happens. You do tech debt cleanup “as you go”. Slip in a few tickets to cleanup specific things and have a policy to update code that is touched when adding features / fixing bugs.

It needs to be a continual cleaning process. That’s why it’s called debt - the longer you let it go un-paid the harder it is to do.

Terraform, ansible and kubernetes (microk8s).

K8s in particular has been a huge change to simplifying my network despite the complexities involved and the initial learning curve. Deploying and updating services is much easier now.

It’s not GitHub. It’s Microsoft. Never forget that.

Not even close.

So going back to the title, what to study? Maybe some specific book? Private classes/courses?

Networking. If you want to understand the reasoning behind things this is where you start. A good foundation in tcp/ip, the 7 layer network stack, as well as basic network protocols (dns, dhcp, http, etc.) will go a long way toward helping you troubleshoot when things go wrong.

Maybe throw in some operating systems study as well for when you start to use docker.

mandatory reviews on code before merging (PR) with mandatory fixes.

This one. Open PR, review by at least one peer, address concerns, merge.

Code review is not punishment - it’s part of your job. You should be willing and able to provide meaningful feedback to your peers. It also gives the team an opportunity to see how other people write code and to agree on norms and standards.

You’re talking a lot of storage - it might be worth investing in some low-end server hardware. A Dell tower or something, maybe one off eBay if you’re looking to cut costs.

I picked up a PowerEdge T110II a long time ago and it’s been… flawless. Just a simple server with a 4x4TB RAID5. No hardware problems (aside from occasional disk failures over the years), easy to manage. It costs a bit more - but server hardware is often just more reliable and for a NAS that’s job #1. This server just runs.

I just upgraded the memory in it to 32GB for ~$100USD. Before that it had 8GB. I needed more for restic doing backups. I probably could have gotten away with 16GB but I figured I’d max it out for that price.

Wow, this question takes me back to like the 00’s when laptops had battery life measured in minutes.

How about “no”.

This week - Apache Airflow setup to automate running backups (replacing cron).

I love how you came up with a completely different scenario to answer “yes” to .

Doubt

You willing to go to jail then? Or just asking others to do so?

Probably because it’s not illegal.

When you open and read files from a program the OS (kernel) will typically cache part or all of those files in memory. This is to speed up subsequent reads of that file since disk access is slow.

“preload” seems to be making use of that feature.

The kernel maintains this cache and evicts (unloads) things from it as needed. You don’t need to worry about it.

Gonna make provisioning servers a lot more interesting…

Their community still a cespool?

Man, what’s up with Linux filesystem developers?

Compared to checks notes reinstalling an entirely different distro???

Jesus the cli phobia here is ridiculous.

While learning about all the Linux stuff I came to know about desktops, and I felt like, if I wanted to ever use a different one, yes, it could be installed the hard way, but I would rather have a distro that can be installed with my desired desktop by default, and the one that got my attention was KDE.

‘sudo apt install kde-full’ is “the hard way”?