Oh Erica…
Here’s the lastest shiny object to consume all of my time.
Think planner mixed with post-its, online.
Oh Erica…
Here’s the lastest shiny object to consume all of my time.
Think planner mixed with post-its, online.
At work I’m integrating a library from our new corporate overlords into an existing application. I use 5 (count ‘em, 5) functions from the library. In order to work, the library, which I’ll call libsink, requires between 10-20 other libraries, most of which appear to have nothing to do with the purpose of libsink I am using. This, to use a technical term, smells bad.
I probably wouldn’t care so much if I hadn’t discovered a symbol collision between the libraries on which our application is newly dependent and another library (libgoo) we use. Two different functions, two different libraries, with different semantics, but the same signature — meaning libsink will happily try to use the function from libgoo. Unfortunately, this results in a core dump when the application unloads.
So, if you’re writing libraries (especially in C, where there is only a global namespace):
I plan to keep a running tab of books I’ve read in 2006 here. Why? Some sick vanity, probably.
Started, but did not complete: Mother of Storms, John Barnes
Read to date, in (roughly) reverse chronologicial order: