ALT title: reread the error message After I've read the error message, I sometimes run into one of these 2 problems: 1. misreading the message person (thinking): ok, it says the error is in file X spoiler: it actually said file Y 2. disregarding what the message is saying person (thinking): well, the message says X, but that's impossible... spoiler: it was possible Rereading the message can feel pointless ("I already read it!!") but it's fast and it can REALLY help.

ALT a debugging manifesto 1. inspect, don't squash try to fix the bug (crossed out) understand what happened (yes, smiley faces and stars) 2. check your assumptions person (thinking): "wait, how do I know that's true?" 3. being stuck is temporary person (thinking): "I will never figure this out!" ... 2 minutes later.... person (thinking): "well, I haven't tried X..." 4. don't go it alone person (speaking to other person): "hey, have you seen this problem before?" 5. trust nobody and nothing person (thinking): this library can't be buggy... OR CAN IT??? 6. there's always a reason computer: "computers are always logical, even when it doesn't feel that way" 7. build your toolkit person (holding toolkit): "wow, the CSS inspector makes debugging SO MUCH EASIER" 8. it can be an adventure person (talking, with cute bug next to them): "you wouldn't BELIEVE the weird bug I found" by @b0rk @omarieclaire, more like this at https://wizardzines.com