How to train layout designers when you yourself are a little more experienced than a junior?

Question

JavaScript

Good day.
There was such a situation that I (a short-term layout designer) had to somehow train and train two beginner layout designers. They have very, very little experience (2-3 pages), and I have no experience in teaching people.
Trainees can now close small combat missions, but their methods of solving most often do not suit me. But they are embarrassed to ask questions and I have to walk around and peck them with questions, "how is it? Is everything working out? Are there any incomprehensible moments?" and most often they begin to clarify something, I explain everything in detail and show with examples and they listen, but it seems to me that this is not enough and it is not very effective.
I myself studied in practice and in my free time I watched a bunch of videos with layout, to understand the whole process. Now the resources that I studied with are very outdated, and such training may not be suitable for everyone.
Share your experience:
1) how did you level up?
2) How were people trained?
3) what should be emphasized in teaching layout and a small amount of js?
4) perhaps share resources for a deeper study of layout?

Answer 1

How did you progress?

Lots and lots of experiments with the aim not to "learn how to solve typical problems", but rather "play with the tools and see what happens". This approach gives a more complete picture of what is happening. Well, Google / documentation / articles as needed.
Methods depend on the availability of time and the initial level of the trainees. In general, to develop an understanding of CSS, it's good to "draw" on it. Roughly speaking, one self-portrait or a little animal , made independently from start to finish, will give experience like a dozen landings. In such sandboxes, the concentration of tricky layout tasks is many times higher than on regular sites, and learning goes faster. Well, just cool things turn out, you can add elements of the game with buns for success. In recent years, this topic has become very popular on CodePen in the form of daily mental workouts.
Regarding methodologies and good practices, it is necessary to explain, answering the question "why" first of all. Stupid pressure by authority (I'm right - you're wrong, my decision is good - yours is not) will lead nowhere. With the question "how" - send to the documentation, so that they read it themselves and at the same time grab something else along the way. If you chew everything, they will not learn to work independently. It is useful to teach them to ask questions . If you see that it doesn’t work out at all, then you can already suggest and show. If possible, you need to automate the verification of the actions of the interns so that they immediately see their jambs, without waiting for the mentor to come. I just made a selection of useful things here just the other day , there are tools for this.
Communication must be established without fail so that everyone has the opportunity to ask and is not afraid to do so. There is more about psychology here - you need not only to determine the time and method of communication so that you do not interfere, and you can quickly get an answer, but also be sure to watch your language so as not to be "too toxic" (everyone constantly forgets about this). And remember - everyone makes mistakes, your mistakes should become instructive examples, there is no need to hide or be ashamed of them. It is useful to have a meeting at the end of the week "only for interns" and analyze what interesting things happened during the week, so that they see the full picture, learn from each other's mistakes and share the experience among themselves already - you explained something to one, he at the end of the week - the rest (and when you explain, you yourself understand better).

Answer 2

1) practice, googling, hardcore
2) almost the same. + at the beginning he explained what was where and what was with what. My main trick was that I always explained in comparisons, well, it came to people. They quickly understood 3) point 4) the html and css
reference is not entirely clear . But they will be needed when the jun already understands how html pages are built in general and will use these links as a reference to peek