Is it useful to “bike” in programming for a long time (and in general)?

Anton R.2019-09-28 11:12:12

IT education

Anton R., 2019-09-28 11:12:12

For some reason, when learning to program (the web in particular), it is advised to sit down on some frameworks, libraries, etc. as soon as possible, although I notice that I learn everything much better when I do everything from scratch, for example, authorization, loading data, files, sessions- cookies and everything else - that is, when you invent your own “bicycles”, everything becomes much clearer. And how do you calculate, is it better to “bike” longer or go straight into battle?

Answer the question

In order to leave comments, you need to log in

12 answer(s)

Moskus, 2019-09-28
@anton_reut

When giving advice, make sure you and the audience of that advice have the same goal. Because “start using frameworks as soon as possible” is if the task is to start slapping the product and getting money as soon as possible. And if the task is to learn how to program, frameworks have nothing to do with it.

Northern Lights, 2019-09-29
@php666

The industry ate itself and drove it into a collapse.
Frameworks that were supposed to provide some relief are now monstrous mechanisms.
Soon the vacancies will be not just a "PL programmer", but a "PL programmer for the Framework"
Everything is going to that.
Do not confuse this statement with libraries.

sim3x, 2019-09-28
@sim3x

It is useful to cycle rarely, but deeply (rewrite the framework, api, sorting, driver, ...)
For yourself

McBernar, 2019-09-28
@McBernar

Yes, I often write bicycles too. True, now the level of abstraction is great has become higher, but still.
This is a good practice, with the experience of commercial development you will sooner or later leave this, because the result here and now will be more important, but at the first stage it will perfectly boost the understanding of programming in general. At least you won't have stupid questions on Toaster - "how to add a method to a class in Laravel" or something like that.

Sanes, 2019-09-28
@Sanes

If that makes you feel better, then continue. Some find it easier to go the other way.
In any case, the result will be demanded from you.

OnYourLips, 2019-09-28
@OnYourLips

Bicycles make learning comfortable. You learn something slowly, there is a solid chance to get completely stuck in development. But you are in a comfort zone , keep everything under control.
Using someone else's normal code allows you to learn effectively. You gain experience much faster, develop faster, reach a normal salary earlier.
Bicycles are inefficient but comfortable. If you do not have the task of making money and you do not see the pleasure in self-development - choose bicycles.

Alex-1917, 2019-09-28
@alex-1917

yes, useful.
a little life hack from our team:

spoiler

на два порядке продуктивнее не изучать кусками фреймворк, как тут некоторые насоветовали, а просто тупо погуглить

Antonio Solo, 2019-09-28
@solotony

For some reason, when learning programming (web in particular), they advise you to sit down on some frameworks as soon as possible,

bad advice. When learning to program, you need to learn how to program yourself. That's why
cycling . but "in battle" (that is, when you are already engaged in custom development), you already use frameworks with might and main

Andrey Titov, 2019-09-29
@titov_andrei

Each time imagine that you are at the workplace and at the end of the day, week, month you need to report to the authorities (or the customer) about what has been done to get paid and to your project colleagues about what has been done to his progress.
If after that you still have time for bicycles, then continue pedaling with a clear conscience and a high level of motivation.

Vladimir Solntsev, 2019-09-29
@vladdimir

Libraries and frameworks not only save time. We have already written above that they make it possible to think at a higher level of abstraction. I want to join this opinion and add that frameworks and libraries are usually developed not on the knee, but on the basis of patterns and good practices.
And in order to use these tools well, you still have to get to know these practices and patterns one way or another. To understand how to use a previously unfamiliar tool correctly and effectively, you need to go beyond your own habitual thinking to some extent, and therefore grow qualitatively.
When cycling, a person remains within the framework of habitual thinking, he certainly learns new things, but this is already quantitative growth. More knowledge, but within the framework of familiar experience.
It cannot be said that one is good and the other is bad. We can say that for pumping skills it is useful to do both.