
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

ALT On the left, there are two examples of markdown code: > **Note** > This is a note > **Warning** > This is a warning On the right, it shows how GitHub renders it in the document preview. They're regular blockquote. But the "Note" word is blue with an info icon on the left. The "Warning" word is yellow with a warning icon.






































