I used to have that mentality. I don't want to derail this thread too much, but I will say a couple of things:
- If you want to make the libraries all yourself, go ahead. Nobody's stopping you. It's a good learning experience, plus you will know how things work, so it's easier to find internal errors (
when you make them
).
- If you do use a library, make sure it's thoroughly tested and it fits your style. If it doesn't fit your style (i.e. under_scored vs. camelCased) then this will lead to lots of confusion. If you can't find one that fits your style, make your own.
- Making your own library isn't a bad thing. It just takes a lot of time to do all of them. Doing a couple of them can be really helpful, especially if the existing ones don't really make sense to you/work the way you want them to.
One example I should point to is my own default game template: I started working on it in the summer with almost no external libraries. Now, several months later, I've wiped most all of my custom files (save a few) and implemented libraries that are much faster and bug free than my own.
TLDR: If you want to make your own libraries, it can be very helpful, but not time-efficient or practical.