NostraDavid

Source: BaalBuddy

He’s pretty gooood!

weird dude who writes raw HTML

Eyy, that’s me! Good excercise to learn actual HTML, instead of directly trying to jump into <insert random JS framework> and getting confused on what’s what.

Anyway, I ended up switching to Hugo as a static site generator, because it was too damn hard to keep all my <header>, <nav> and <main> aligned for all my HTML files.

Now I can just write a markdown file as an article, or switch back to raw HTML if I so need (like rewriting Alan Turing’s paper " On computable numbers" in HTML because I can’t use TTS on the PDFs I found; I still haven’t finished writing it, because I am now reading E. F. Codd’s papers on the Relational Model, which is pretty wild how we already figured that shit out in the 1970s!)

Learn some proper English, you cappie

It’s Saturday Night Live. It’s an American Humour* channel by the corpos.

* the cringy type of humour - I do not understand why people like it. Oh well.

1 Season, 15 Episodes; Mr Bean is Eternal.

I just learned the Faroe Islands is connecting all their islands (Exploring New Road Tunnels and Power Generation in Faroese Islands). Even to islands that only have 500 people living there.

I don’t see why the USA couldn’t increase its railway (hell, you can learn from Japan if it needs to be earthquake resistant) starting today.

lol you beat me to it: https://i.imgur.com/0h892RM.png

Within the context of the meme it’s a guy with a mug and an exploitable sign on his table. Nothing more.

This shit sounds pretty tiring, IMO :/

Oh, oh, oh! I got one not mentioned yet:

ELK.

Well, not the whole of the ELK stack (Elastic, Logstash and Kibana, though the full stack size is much larger nowadays), but their watchers. A watcher is a piece of JSON with some search specifications on when to trigger and send an alert to email/slack/teams/whatever. We’re basically abusing it as an alerting system, and generally it works… Fine… Presuming Filebeat actually ingests our logs (which is partially our fault, as there’s a fix, but it takes too damn long to drag 3 teams along to implement what needs implementing to fix that problem).

Anyway, the problem is not the watcher itself, even though it is painful (heh) to learn the structure. It’s “Painless”, the JVM-based scripting language available in a watcher. It’s anything but. It is SO painful to write code, inside of a JSON object, making sure everything is exactly as it should be, having to use the DevTools in Kibana to try and trigger it, wait to see what enormous error comes out while praying it works. No IDE, no nothing. Ah, I lied. It does have Syntax Highlighting, for non-Painless code, IIRC…

Oh, having to dig information out of the data you get is super unintuitive too.

At least the UI/Kibana is good, and Elastic is pretty good too. Fuck Filebeat though. And Painless.

The background noise surpression of Teams is peak quality (vs Webex and Slack, though Webex is somewhat good)…

Did you check the calender in Teams? Not to be confused with the calender in Outlook, which may or may not overlap.

I’m pretty sure you can disable the bleeps and bloops people are complaining about - get a tool, then don’t spend any time to learn it and then suffer using it.

Look at mr fancy, with his interface that can search through topics - we’re just flying by the top of our head >_>

At least we were smart enough to just generate a CloudEvent and jam it into a KafkaMessage before sending it, so that’s pretty standard.

We just use it as a messaging bus - we’re not sending “big data” through Kafka. We tried, failed, and immediately gave up, lmao. Now we just save data on HDFS and send where we stored said file (effectively a “claim-check pattern”, if you’re into design patterns)