I’m making the accompanying suspicions about the inquiry
Previous implies that these are things that someone is relied upon to know before taking the activity. Learning the subtleties of an organization’s innovation stack, style guide and designing way of thinking are immensely significant, however you shouldn’t be relied upon to realize them ahead of time, and by and large doing so is incomprehensible.
Explicit information implies that these are things that you can learn with some exertion and study. They ought not be general classifications like “security”, “structure”, or “server-side improvement”. They ought to be things you know or ability to do, not things you “have involvement in”. Also, they ought to be explicit enough that someone can feel good saying they comprehend the point or don’t. A large portion of the things I list beneath are subjects, however I attempt to spread out a particular arrangement of things that you would need to know to get it.
The most contrast among progress and disappointment implies that these are the things that are truly going to have any kind of effect in how viable you are at understanding and finishing the work doled out to you. There are numerous such things, and their significance will shift situationally, so this is only my informed interpretation of a generalists list.
You should know the center language
You ought to comprehend async code
You ought to get settled with at any rate one lot of engineer instruments
You ought to be alright with fundamental structure undertakings
At the point when I talk structure, I mean both the nuts and bolts of actualizing a visual plan with HTML and CSS3, and enough of a comprehension of plan fundamentals to make a basic UI that looks alright and isn’t confounding. That last prerequisite is harder than you’d might suspect. Configuration is hard and for the most part symmetrical to the arrangement of abilities most people get while figuring out how to code. For learning structure hypothesis, I’d suggest finding a straightforward asset on visual plan first like White Space isn’t Your Enemy, and in a perfect world enhancing that with a more UX centered asset like Don’t Make Me Think. The down to earth side of HTML/CSS is least demanding to get with understanding. In case you’re utilizing devtools you can perceive what others are doing with CSS and change and investigate utilizing the components board. Also, there are heaps of good online assets for finding out about CSS and HTML punctuation like MDN for API data or CSS-Tricks for thoughts, instructional exercises and staying aware of new stuff.