In the morning I pushed md2tweets to
GitHub. This program is a
companion to tumblelog.
It reads the Markdown input file of tumblelog and outputs tweets
separated by a % character; the input format of
tweetfile, a program to
post to Twitter at random.
I run md2tweets each time after I run tumblelog via a
Makefile. The
tweetfile program is called several times a day via cron on MacOS.
I do a lot of web scraping in my spare time, and have been chasing down different formats and code snippets to make a large amount of network requests locally, with controls for rate limiting and error handling.
I’ve gone through a few generations - I’ll use this post to catalogue where I started and what I’m doing now.
Source: Writing fast async HTTP requests in Python, an article by JonLuca De Caro.
I used to think that I didn’t need comments if I wrote self-documenting code. However, I have realized that I do write comments, and that I find them really useful. To see how many comments I write, and what kind they are, I wrote a script to analyze my git commits from the last six years. In total, seven percent of my committed lines contained a comment. This blog post has details on what constitutes good and bad comments, as well as more statistics from my script.
Source: On Comments in Code, an article by Henrik Warne.