Debugging
Debugging
41 comments
-
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 Expiry Bot just entered the chat.
-
Let's encrypt brother
-
-
Might want to check out swag from linuxserver.io
It's a docker/kubernetes container image with a working certbot client in it.
-
-
"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.
-
-
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
-
-
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.
](https://www.explainxkcd.com/wiki/index.php/349:_Success)
[
::: spoiler Title text: 40% of OpenBSD installs lead to shark attacks. It's their only standing security issue. :::
-
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."
-
Sure feels like that sometimes, LOL
-
Is he giving himself cigarette burns?
-
Wow that's subtle. Good catch
-
-
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.
-
-
I would be sad too, if someone broke my PC and smashed my home.
-
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.
-
-
My friend just finished a couple solid days of debugging where there turned out to be a whole series of problems that looked like one bug, so even though he kept fixing things the app still kept not working. Finally hacked his way out of that jungle into the bright light of day.
-
Every single day
-
Just later that day? Clearly, comic man doesn't have to cojones to fuck up as badly as I have.
-
My favorite so far:
$ gdb -ex 'file /bin/gdb' run corrupted double-linked list Thread 1 "gdb" received signal SIGABRT, Aborted.
-
if ([]){ // I miss common Lisp's detection of empty }
-
Did the coffee mug go through the wall or up is ass?
-
Yes
-
Kinky
-
-
41 comments