Answer the question
In order to leave comments, you need to log in
Guys, a question for those who know how to do it better: first study the theory and then code when it is firmly entrenched in the head, or immediately start coding? (Html/css/js)?
At the moment I'm looking at someone else's code, doing it on someone else's code, googling incomprehensible tags and markup ... intuition tells me: SOMETHING WRONG!
Answer the question
In order to leave comments, you need to log in
I personally study any language, any framework, any technology like this:
1) A task is set
2) Ready-made solutions are found for the task
3) Problems and places I don’t understand are googled
4) Something is being written, maybe a fifth wheel, maybe another bike, but it works
5) Wrote item 4, comprehended. Googled for similar solutions. At this step, the correct words (terms, library names) for Google already appear in my
head
. I actively used the algorithm above when I learned Ruby after PHP.
Theory and practice should always go hand in hand.
Learned something - apply immediately.
1. You need to master the theoretical base, so that you know what tags, properties, and so on are in general.
2. A task is set.
3. In the process of solving the problem, incomprehensible moments are googled.
Steps 2 and 3 are repeated until we get the required amount of experience.
4. Profit!
The problem of many beginners on the toaster is that they start coding without familiarizing themselves with the subject area. Without reading a book on the language and its capabilities, they fill up the toaster with simple questions that are in books. Take a book on layout, preferably a fresh year of release, and read it while typing examples in the editor. And thoughtless copy-paste generates questions with shitcode, which you have to understand in order to help.
Google based on the current step of the task you need.
(it's not just for html/css/js)
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question