

There’s something to be said for consistency!


There’s something to be said for consistency!


What’s a little scope creep between friends?


Well, if we’re saving DB space, why not just use the generate_series function (assuming you’re running PostgreSQL…)?


Somebody used the wrong data type for the Hour column…


So can I…
It’s complicated.
This is definitely a decent starting point but not a complete solution, unfortunately. It’s not always cost-effective if you only want a few tracks from an album or need to import it to get it at all (or if it was a limited release it can be hard to find at all).
You forgot to set up a 302.
I avoided overtime like the plague since my employer didn’t like to deal with it (so if circumstances required me to work overtime my supervisor was pretty good about allowing me to take it as time in lieu the following week), but unfortunately there were definitely times where I had to log in on the weekend (the challenge of having customers that require support 7 days a week).
Apparently I’m off the end of the chart. My last workplace set up had:
I use Pi-hole, except that I originally retrofitted after setting up DNScrypt years ago to connect to Cisco OpenDNS. That’s not the only DNS server you can use with it, though, and it’s added more features since.
To use DNScrypt with Pi-hole on the same device, set DNScrypt to listen on 127.0.0.1:54 and point Pi-hole to that as the DNS server.
The only time I have ever had any trouble with this setup and DNS resolution is when the network is recovering from a power outage; there’s a race condition somewhere between the Pi and my modem/router that I’ve never found the time to pin down (given outages are so infrequent I just haven’t gotten around to it) and it’s easily resolved by rebooting the Pi.


Having worked with JavaScript, I understand the usefulness of a “less strict” equality comparison like this, but the coercion of objects still does my head in…
(And for the record, most of the time I did use strict equality).
Currently testing out Shiori. I have tried both it and Readeck on my Raspberry Pi 3B running 32-bit Raspbian ‘Bullseye’. From an installation and performance perspective, Shiori is easier: 32-bit binaries are available and its web interface is a bit more responsive. If you are not running a 64-bit version of the Raspberry Pi OS, you have to build Readeck yourself (which I successfully did).
The main attraction of Shiori over Readeck is that it has both a readable and archive view. The main downside for me is it lacks the read/unread feature of Readeck and Pocket (although that’s apparently something planned for future and in the meantime, it’s possible to workaround using tags).
Both have a browser extension to enable capturing pages that contain Javascript and do not gracefully degrade. Both also have an export-to-ebook function that may suit your e-reader.
Bottom line: if you have an RPi4 or later, then Readeck is probably want you want. If you’re running an older Pi, though, Shiori may be a better option.
Definitely #1. I’ve encountered #2 with a very specific IDE and #4 and #5 on occasion.
As the senior dev, please don’t.
We work in protoduction.
Nope, just inherited a colleague’s codebase when they left. It’s years later and I still haven’t sorted it all out.
As someone who has inherited code like that, I would like to strangle the first programmer in the comic.
If only it were so easy…