Debugging

"oh it was just a missing semicolon"

Linter issue.
- Even if you're not using one, you should be instinctively looking for a semicolon the moment you get a syntax error unless you're a complete beginner.
Rubber duck debugging often helps.

so the other day I sat down trying to setup a SSL cert for my self-hosted services

Have you heard of our Lord and Savior, Traefik + ACME issuers?
- Let's encrypt brother
- Let's Encrypt Expiry Bot just entered the chat.
- Does Trafik also allow DNS based challenges with additional certbot plugins, or does it only work by serving a challenge in /.well-known/?
  
  I’ve set up my internal homelab with LE certificates, but if I could get rid of certbot and do this automagically, it’d be nice…
Might want to check out swag from linuxserver.io

It's a docker/kubernetes container image with a working certbot client in it.

Laying in bed thinking about the problem, "oh, that must be it!" Jump excitedly out of bed to work on the problem, "welp, that wasn't it."

I don't like being on this picture.

I’ve been trying and failing to fix an email being sent to spam issue since last fucking Monday (with all the SPF, DMARC and DKIM garbage).

I want to die.

SPF, DMARC and DKIM

Ironically, spam generators are experts EXPERTS in this trash fire of a topic

Reminder to all you chaos monkeys: use [Object object] on web forms occasionally for a bit of fun.

Edit: and to remind typescript devs they’re just transpiling to JavaScript

I shit you not I got that object object response with a 200 status.

Aw come on, debugging can be fun. I love the investigative vibe of it. You get to be your favorite detective. You start asking around. You pin the the culprit. You get closer and closer to damning evidence. And then Bam! Fixed. Another mystery solved. Mine’s Columbo.

I love asking,

"What sick fuck thought this was an acceptable solution?"

And a few moments later:

"Oh. It was me."
- Just finished with a refractoring project. I said this a LOT.
Agreed, for any non-trivial bug I just start dumping text into a word file to track what I'm doing. Like: error messages, values of variables at key places, libraries used, URLs of documentation and background reading and stackoverflow pages looked at, test fixes and their effects, etc. Then if someone asks me wtf I've been doing all day I can easily show them. Also, if I have the same problem a couple months later I can remind myself.
It's fun when you debug your own code.

Who is OP, and how did you get pictures of me last night?

LoL, blue shirt has no persistence. Anger and giving up gets you nowhere.

Title text:

40% of OpenBSD installs lead to shark attacks. It's their only standing security issue.

Just later that day? Clearly, comic man doesn't have to cojones to fuck up as badly as I have.

I would be sad too, if someone broke my PC and smashed my home.

My favorite so far:

$ gdb -ex 'file /bin/gdb'
run
corrupted double-linked list

Thread 1 "gdb" received signal SIGABRT, Aborted.

Sure feels like that sometimes, LOL

Did the coffee mug go through the wall or up is ass?

Yes
- Kinky

Is he giving himself cigarette burns?

Why is he in his undies 😭😭😭

Every single day

if ([]){
   // I miss common Lisp's detection of empty
}