umbraroze

There’s two kinds of crypto scams: Ones that actually involve crypto and ones that don’t.

Vague, possibly impossible to implement promises about proposed future functionality are an integral part of the crypto sphere!

Damn, OneCoin was bad. Ruja Ignatova was the first crypto scammer I’ve seen talked about in national news and she was also made fun of in a news comedy show over here. A true scam pioneer.

Brief history of YAML:

“Oh no! All of these configuration file formats are complicated. I want to make things simpler!”

(Years go by)

“…I have made things more complicated, haven’t I?”

YAML is generally good if it’s used for what it was originally designed for (relatively short data files, e.g. configuration data). Problem is, people use it for so much more. (My personal favourite pain example: i18n stuff in Ruby on Rails. YAML language files work for small apps, but when the app grows, so does the pain.)

Error in Moderation

Could have been worse. Could have been an Error in Excess.

Technically, SQL is case-insensitive.

Practically, you want to capitalise the commands anyway.

It gives your code some gravitas. Always remember that when you’re writing SQL statements you’re speaking Ancient Words of Power.

Does that JavaScript framework that got invented 2 weeks ago by some snot-nosed kid need Words of Power? No. Does the database that has been chugging on for decades upon decades need Words of Power? Yes. Words of Power and all the due respect.

Scrivener is still the absolute best word processor for ginormous writing projects. There are FOSS projects that do some parts of it right, but fall far behind in the others. It’s particularly frustrating because my usual FOSS approach would be to use other tools that make up for the inadequacies, but Scrivener pretty much nails the “what to include and what to leave out” equation. It’s a great combo of a word processor, project management tool and a research/notes tool, all rolled into one.

/serious Well, yes, most APIs are meant for system-to-system interaction, that’s kind of a given. But since this particular API is clearly meant for human-to-system interaction, returning a human-readable response is adequate. Yes, a better design would probably allow the client to specify additional parameters about the desired response.

/back-to-jokes Yeah, well this kind of sums up most of my job applications. I send an application and the recruiting people are all like “OK”.

I have a Zyxel NAS server that just offers a SMB share. I’m just dumping my photos there under YYYY/MM/DD scheme, and converting all of my Nikon NEF files to DNG. (For importing photos to the NAS and generating backups, I have a PowerShell script and a PowerAutomate action. Also mild usage of Dropbox to transfer files from my cellphone.)

For actual management of photos, I use ACDSee Photo Studio Professional, and it just writes all tag information to the files themselves, so I can basically use any other software for photo management. For actual photo editing, I use DXO PhotoLab and Affinity Photo most of the time.