Like there comes a time in every developer's life where we arrive at some hypothesis of writing our own code for a library, he scrawls some code implementing some features. Before we continue, I would like to analyse his mistakes. May be he thought that his work'd be superior as he is eliminating most of the unnecessary stuff the library provides (or) may be he didn't do enough research on what's likely to be the most necessary thing in the application (or) may be there's just this one small thing that isn't quite right in the library, so he wants to rewrite it from scratch. The truth is, he has done it, I've done it, and you likely have too. The next phase of his life would be the annoying part. He realizes, but slowly, that he is doing nothing but what is so called as "re-inventing the wheel" and whatever functionality he writes is already there under development for a significant amount of time, and the community that develops these things must have experienced something similar. He finds it funny that he wasn't the only one who fell into this ludicrous life.
Not a great scheme for an ending. I know. But some of you would've got the memo. :).
The advice section:
The long-evo idea about libraries is that these are developed in some remote part of the web and the community that develops these things is not available to approach by normal people. The idea, as certain as Heisenberg could be, is nothing but drivel.
Blah blah stuff
Don't get me wrong about writing your own libraries. It's completely possible ;) .