Do you really need a plugin for that?
- Event status
- November 30, -0001 - 00:00
In this session we attack a common problem of frontend development - the plugin/framework/addon/bootstrap/etc overload. It seems in very many cases everyone on the team forgot to ask this vital question:
Do we really need that?
The result of the plug'n'paste-based strategy is often a generic UI, multiple design compromises and typically much poorer performance. And you didn't learn anything new, which suck more than all the other reasons combined. Now, I for one thought we had finally escaped the assembly line, but maybe I am wrong?
Ok, so it allows you to get started really fast – but it also very frequently has the downside of not fitting your needs exactly – or being bloated in ways you never imagined possible. Before you are done tweaking the tool to fit your needs, you have ended up spending more time frustrated, than it would have taken you to write optimized custom code.
Writing custom code expands your skills, so in many cases it is in both yours and your client's best interest to skip (some of) the plugins.
I'll talk a little bit and then we'll all talk. One at the time. And there's room for all opinions. It's going to be fun.
Free for everyone.
- think.dk - old