Most of my programming is for personal reasons. I don't hold myself to productivity quotas and I've always preferred to write software entirely by myself, so I've never been a big user of libraries. Libraries certainly have their benefits, and a well-built library can be a major time saver and headache preventative, but I've always preferred to develop my own code in my own way whenever possible. (This hands-on-everything approach is for my programming only; I'm CERTAINLY not that way in regards to my car or my house!)
In regards to creating libraries for general consumption: um, well.... Many times in the past I've started putting together various libraries for personal use, but in many cases evolving goals & feature creep made many of them unwieldy to use, while in other cases my needs & approach had changed and functions that were just fine for one project needed to be heavily reworked for another.
So while I MIGHT use a well-crafted library, at least in the initial stages of program development, I am by nature biased against pre-packaged code libraries, except for those that come with a compiler.
In regards to creating libraries for general consumption: um, well.... Many times in the past I've started putting together various libraries for personal use, but in many cases evolving goals & feature creep made many of them unwieldy to use, while in other cases my needs & approach had changed and functions that were just fine for one project needed to be heavily reworked for another.
So while I MIGHT use a well-crafted library, at least in the initial stages of program development, I am by nature biased against pre-packaged code libraries, except for those that come with a compiler.