Today at RC I gave a 10-minute talk about blogging myths. I might turn it into a blog post later, but for now I’ll just post the slides.
“blogging myths” slides
The myths are:
- you need to be original
- you need to be an expert
- posts need to be 100% correct
- good bloggers don’t write bad posts
- you need to explain every concept
- page views matter
Here’s a link to the slides on speakerdeck, though the aspect ratio there is broken for some reason as I’m writing this.
debug by adding print statements to a library’s code
I was debugging with someone today and I was reminded of one of my favourite debugging techniques!
Sometimes when I’m debugging, I’m using a library, and I’m getting an error, and I have NO IDEA why and all the Googling in the world just does not tell me anything useful.
When this happens, I like to:
- grep the library’s code for the function/class I’m trying to use (or the error I’m getting)
- add extra print statements to the library to give me more information
- figure out the bug
- remove the print statements
This works really well with Ruby / Node / Python / Go – anywhere where it’s
normal to have a directory like
node_modules with all the code for all your
dependencies where you can easily edit & rerun the code.
Occasionally doing this helps me find a bug in the library, but 90% of the time the problem is with my code and it just helps me understand how the library is actually supposed to work.