I was reading Crafting Interpreters. After adding function calls and stack frames, i tested my implementation with the Fibonacci script at the end of the chapter
I spent about 2 hours debugging my call stack, and even tested the script in Python
Oh, I love this one, it’s very silly. I find it oddly grounding when I discover that the cause of a problem was me being silly, because I’m already aware that I am prone to foolish errors (as all humans are); when I discover that an unfathomable computer error is actually my fault, it feels like everything is right with the world
I’m in this picture and I don’t like it. Yesterday I was trying to debug my reverse proxy setup for a new app and why it wouldn’t work.
Well, if you configure it to route shinyNewApp.example.com to your app, but then always access sihnyNewApp.example.com with your browser…
I was reading Crafting Interpreters. After adding function calls and stack frames, i tested my implementation with the Fibonacci script at the end of the chapter
I spent about 2 hours debugging my call stack, and even tested the script in Python
Only to realize that Fib(3) is indeed 2
Oh, I love this one, it’s very silly. I find it oddly grounding when I discover that the cause of a problem was me being silly, because I’m already aware that I am prone to foolish errors (as all humans are); when I discover that an unfathomable computer error is actually my fault, it feels like everything is right with the world
Great book btw
That happens so often that checking for spelling is the first thing I do now when something goes wrong.
Yep, or go proofread some JSON…
Or check formatting in yaml
Fucking yaml…
I’m ashamed to admit how many times a basic english spell checker in my IDE has saved my bacon.
I just have a spell checker enabled in vscode
So helpful for dynamic languages that can’t detect undeclared variables (looking at you JS)
Yeah, spell checker is the winning move here.
Been there. Blamed the DNS, but turns out that I didn’t know how to type customername.tld