All Posts

If something weird is happening, you want to know everything that's going on on a server, as fast as possible. At these times, you will be very happy to have a simple alias `wtf` installed that you can type immediately after logging into a server, and see all that it's busy with.

> "Simplicity is prerequisite for reliability." [Edsger W. Dijkstra](https://www.cs.utexas.edu/users/EWD/transcriptions/EWD04xx/EWD498.html) As our experience grows, we learn from past mistakes and discover what's truly important in reliable systems. When designing systems, simplicity is an often heard mantra, but it isn't getting applied nearly as much as spoken of. I'm guilty of this too. I think it's mainly because engineers love to, well, engineer :) and will naturally try to [outsmart problems by throwing more tech at it](https://teddziuba.com/2010/12/the-3-basic-tools-of-systems-engineering.html).

This article in 50 words: I used to prefer spaces vs tabs, now I don't care so much, think it's more important that you can easily switch on a per-project basis. Have some thoughts on how conventions should be established, and I'll demonstrate bash code that can convert your codebase to a new standard.

I recently bought a NAS so my data is safe & available, with the benefit of being low power / noise / heat. I've considered Netgear, QNAP, but decided to go for a Synology as it was affordable, still had a big community, decent reviews & Time Machine support.

The Synology ships with a Download Station but it's not remotely as advanced as [SABnzbd](https://sabnzbd.org/). What I mostly miss is automatic par & unpacking of its downloads. Here's how to fix that.