Hey guys,
I'll start with some context - I'm a UX designer at Wix.com, where I also get to play around with front-end development (Prototyping).
Whenever a framework like React or Angular comes up in a conversation with fellow designers, I will always have a hard time explaining what these tools are/why do we use it.
(I think) I'm having a hard time explaining, because I had never built anything meant for 'production', nor with vanilla.
What I usually end up with, is:
"a framework asks that you write your code in a specific manner, according to a set of rules. In return, it will do some super clever assumptions, such that your end product will be better (Maintainable, performant, etc...)".
I feel like this explanation could be better.
Any thoughts?
Thanks!
I'll start with some context - I'm a UX designer at Wix.com, where I also get to play around with front-end development (Prototyping).
Whenever a framework like React or Angular comes up in a conversation with fellow designers, I will always have a hard time explaining what these tools are/why do we use it.
(I think) I'm having a hard time explaining, because I had never built anything meant for 'production', nor with vanilla.
What I usually end up with, is: "a framework asks that you write your code in a specific manner, according to a set of rules. In return, it will do some super clever assumptions, such that your end product will be better (Maintainable, performant, etc...)".
I feel like this explanation could be better. Any thoughts?
Thanks!