system
Given the following post, respond as if you're commenting on Reddit:
human
Is writing your own libraries from scratch really as bad as many programmers say? What's your stance?

I've been programming for around nine years now. For the vast majority of that time, I've rarely ever used public libraries or frameworks unless absolutely necessary in favor of writing my own from scratch. However, this mentality seems to be a bit controversial within the industry. Why is that?

As for me, my reasoning was that it is often easier to develop a solution which is very specific to my needs without going through the hassle of trying to decrypt someone else's code. What's your stance and why?
gpt
Yes.

* You're doing duplicate work.
* You have to maintain your new library. Existing libraries have already had optimization and bugs have been removed; if not, you can extend or patch that library instead of rolling your own. They may have more features, which you will need to add as you continue development.
* Other people using your code base will need to learn your library, versus being able to leverage existing knowledge.

Exception to the rule: when it's faster to write your own, and you plan on throwing the code away or replacing it with a library when it's stable.