Building custom website and web-based data management systems for more than two decades.
Throughout my career I've worked with many nationally recognizable brands. My software continues to be a heavily used mission-critical part of their development and marketing strategies.
(Details Available by Request)
Writing performance-driven clean code is something I pride myself on. Enabled within my development environment is a strict EsLinter, ensuring syntax that is consistent, optimized, and as easy to navigate as possible.
If a developer can't quickly scan a file and see what it's doing, the code is needlessly complex. Via small and concise comments, my modules are extremely well documented. This makes application maintenance much more efficient when dealing with a larger codebase.
Having built advanced spreadsheet applications, I can tell you that performance is greatly affected by poor coding practices.
There are two things I focus on when building an application. Maintaining the integrity of the data, and processing that data as quickly as possible.
Saving 20ms by limiting the scope of a DOM search seems a little overkill. Repeat that for 20k cells in a spreadsheet and you'll appreciate how quickly it adds up.
Frameworks like jQuery and Bootstrap have flooded the industry with "Developers". If someone tells you they use jQuery, ask them why. It's not a bad thing, just make sure they can explain the reasoning.
For transparency, I occasionally use jQuery. I use it because the Ajax methods are pretty decent. Do I need it? No, not at all. However, it's often included in my applications as a third-party dependency. I prefer a Vanilla.js approach when it's an option.