Does a programmer need to reinvent the wheel?

Question

Programming

Do you think a programmer needs to reinvent the wheel?
Is it necessary to create what has already been created?

spoiler

Сегодня с моим товарищем произошел диалог, который утверждал что настоящий программист создаёт всё сам, на то он и программист, а библиотеками пользоваться и обезьяна сможет. Но каковы реалии?
Допустим, вы работаете над веб-проектом и заказчику необходим на сайт слайдер. Как в таком случае логичнее поступить? Создавать своё, или же сэкономить время и подключить библиотеку? Заказчику ведь чаще всего без разницы, главное чтобы работало.

Answer 1

A real programmer creates everything himself with the help of libraries.

Answer 2

You can create a bicycle for educational purposes. Another option, if we need something simple and it is easier to duplicate it than to drag an additional library into a project that has a lot of other things.
By default, it is better to use the prepared one, if it is available and convenient in this case. It has already been tested and the people have walked the rake and know the paths. And not only the people in your office, but also beyond.

Answer 3

There are training bikes. You made it to understand how it all works. I myself wrote a neural network a couple of months ago, just to understand the method of back propagation of an error ... The grid worked very slow, but it worked. But here we are talking about making, seeing and throwing away.
And there are also industrial bicycles. And you need to know one thing about them - they need to be lubricated regularly. You always want to do it - it's usually interesting. Moreover, it often solves the problem better than the available solutions. But:
1. It will take you time, and much more than you think at first glance. I admire those guys who know how to correctly calculate the time until they get a really working product, and not just a prototype. But among programmers, I have not seen such people.
2. Third-party tools and libraries, in parallel to which you have started to develop. They will be able to do better, faster, support the latest versions of the OS and the products you work with. In order to stay on an equal footing with them and not bite your elbows later that your creation can’t do anything compared to them today, you will have to spend time on this very bike in the future. And in the case of compatibility issues, this is already a vital necessity. You made an importer with Excel, and the Excel format took and changed - update the importer, otherwise your entire product will not work, this importer uses it.
With all this I want to say that bicycles can be made, but with the understanding that making a bicycle is like having fish (or giving birth to a child, if you like) - here you need to understand your responsibility for the subsequent fate of this bike of yours, and that in itself without your constant participation, he will not survive;
Although the creation of a bicycle for web projects is already the 3rd case. In the realities of Russian site building, this is a bicycle for sale with subsequent slaughter. Made it and forgot. The site will die on its own in 2-3 years, along with the bike. Will be replaced by a new site made from scratch. So there is already minimal responsibility for the bike - do it for your health, cross out the second problem.
The first will remain - you will lose time. And for sites, this often leads to disaster. The average customer of a website is ready to spend money on a subject that is only enough for 3-4 working days of wages for a web developer. To do everything and everywhere from scratch under such a condition becomes an unaffordable luxury.
In this business, either those who specialize in very large and serious projects survive (only for this you need to have a name and a good staff), or those who assemble the site as a constructor within a couple of days.