C was not my first programming language. At some point I figured that there is a lot of Open Source software written in C out there, and contributing would require to learn it.
If you are new to C you'll read a lot about dangerous macros, arrays and pointers, how you should handle dynamic memory allocation etc. All theses points are very important, but here is an attempt to sum up more general concepts that you are less likely to find in most C tutorials. If anything, it's a good summary of what I would have liked to read when learning C (maybe I did but forgot — there are some things you only learn by shooting yourself in the foot).
Programming is a lot about reading. You get to read documentation, tutorials, books and of course code. Since I started programming I've been eager to read and my bookshelf has now dozen of geeky books (programming books tends to be quite large).
While crawling in the documentation and books I found gems that I kept preciously in a dusty .quote file in my home folder (I guess everyone has that kind of file). When I find a good quote, I put it there.
Yesterday it was announced by Google that php.net has been compromised. Rasmus Lerdorf, who committed PHP, quickly declared that it was a "false positive" before starting to complain about Google's Webmaster Tools.
I guess that when you say "it's a false positive" when you're not sure and then proven wrong, it can be expected that people are gonna make fun of you.
I just wanted to link a cool 5 minutes comic about the "Gender theory" (in french) .
As you might have noticed, the view has changed a bit here :)
I am using Twitter Bootstrap daily at work and being able to use all its goodies while blogging was haunting me. So I wrote a Bootstrap based theme for Octopress: Octostrap3
Not too long ago (back in 2008) I wrote tagutil, a small CLI tool to display and edit music files tags. At the time I felt in need of something easy script without GUI, but most of all I wanted a tool with a complete support for Vorbis Comment.
While both Ogg/Vorbis and FLAC uses Vorbis Comment, libFLAC has the courtesy to provide a simple API to read and write them, where libogg/libvorbis only provide a way to read them. OK, It's not entierly true; it is possible to write them, it's just damn hard compared to libFLAC because you need a good understanding of Ogg/Vorbis's design.