Something I wish I had done earlier on in my programming career . . .
Or, perhaps it's more a function of the library in the city I happen to live, is that the library will often order books that you recommend. When a book comes out, related to something new that I've been hearing about in the field of web development or programming, I recommend it to the library for them to purchase and check out. They've never turned down one of my requests, but there's a caveat:
Sometimes actually getting the book into my hands can take a while. It's great that I can request books ( as well as DVDs and other materials ), but the book I most recently requested, Practical Django Projects, has really taken a great deal of time. I requested it clear back in June. I just noticed today, ( as I can check my account with the library via the web ) that the book was finally checked out to me. The funny thing is that the library actually received the book and had a status of "Newly Acquired" a few weeks after I requested it. So, it actually sat in limbo for almost three months. Just two weeks ago I finally saw the status change to "In Processing" meaning that they were preparing it for checkout.
While this method is less costly in terms of money than going out and buying technical books, the opportunity cost can be quite expensive. However, I guess at the end of the day you have to decide which is more important. Do you want to buy technical books that you may or may not end up using for a while and then transfer to the shelf never to be used again, or can you put off certain things you want to read more about?
I started using Django about six months ago and I really like the framework. While the online documentation is pretty good I've been looking for some pratical examples that can help me expand and try out some more advanced techniques. The reviews have been a bit mixed on the book, but I'm going to give it a shot and see what happens. Sometimes, when the reviews are mixed on books like these, it's better to try before you buy. I've sunk a bunch of dough into tech books that sometimes I wish I had back in my pocket.
Or, perhaps it's more a function of the library in the city I happen to live, is that the library will often order books that you recommend. When a book comes out, related to something new that I've been hearing about in the field of web development or programming, I recommend it to the library for them to purchase and check out. They've never turned down one of my requests, but there's a caveat:
Sometimes actually getting the book into my hands can take a while. It's great that I can request books ( as well as DVDs and other materials ), but the book I most recently requested, Practical Django Projects, has really taken a great deal of time. I requested it clear back in June. I just noticed today, ( as I can check my account with the library via the web ) that the book was finally checked out to me. The funny thing is that the library actually received the book and had a status of "Newly Acquired" a few weeks after I requested it. So, it actually sat in limbo for almost three months. Just two weeks ago I finally saw the status change to "In Processing" meaning that they were preparing it for checkout.
While this method is less costly in terms of money than going out and buying technical books, the opportunity cost can be quite expensive. However, I guess at the end of the day you have to decide which is more important. Do you want to buy technical books that you may or may not end up using for a while and then transfer to the shelf never to be used again, or can you put off certain things you want to read more about?
I started using Django about six months ago and I really like the framework. While the online documentation is pretty good I've been looking for some pratical examples that can help me expand and try out some more advanced techniques. The reviews have been a bit mixed on the book, but I'm going to give it a shot and see what happens. Sometimes, when the reviews are mixed on books like these, it's better to try before you buy. I've sunk a bunch of dough into tech books that sometimes I wish I had back in my pocket.


