Struggling

Started a new job not super long ago with the intention of "learning new tech" and so I get my wish, I'm thrown into a project as the LEAD ENGINEER

And my junior dev proceeds to run circles around me and I know literally nothing about what is going on in this project aside from the architectural / feature planning discussions I've had with marketing/junior

I've been trying to learn vuejs for what seems like weeks and weeks and I'm just not "getting it" I come from a strong oop php background and this paradigm is using tons of tech I know basically nothing about. Every time I talk to junior I get super depressed cause he's speeding along and I'm still completely clueless.. what the FUCK do I do

Maybe go a step back. Before trying to understand HOW something works, first research WHAT problem it is even meant to solve. It's easier to understand an implementation if you know the objective.

In case of JS frameworks, it's all about state management.

@Fast-Nop state management, I have heard this term thrown around a lot. I imagine I should focus on that a bit. Thanks for the advice

@Fast-Nop Yeah once you know it’s reason to exist you’re gold

@anolis Let's go back to what was before such frameworks - the legendary jQuery spaghetti hell.

Imagine you have a combo box in your UI which has options A, B, and C. However, once the user has pressed a certain button three times, the combo box shall instead list "A, B, C, D".

Now what happens? You have your button object with a "pressed" counter, but now the button event handler needs to update some random other combo box.

Once you reach a certain complexity, everything is connected to everything else, and you get an intertangled web that is impossible to maintain.

Enter JS frameworks. The core idea is to decouple this mess again. Instead of having the setter logic in the button handler, the button gives the info to the framework, and e.g. via some declarative logic, it knows that it has to update the combo box.

The kicker: you write this declarative logic to express WHAT the logical connections are, not HOW to implement them.

@Fast-Nop that is brilliant!

@Fast-Nop wow, this is such simple advice I've even overlooked it. This would help me a lot in understanding my own new job role. Thanks!