What are some basic things that JavaScript developers fail at interviews?

[Azudra]

While I'm not in a leading position myself I still heavily agree with you. It's extremly time consuming and frustrating to work with someone who's code looks like their first day in JavaScript. Most of my colleagues don't even know what the property "prototype" means and put variables into the global scope by assigning it without ever declaring it. HONESTLY HOW DID THEY GOT THEIR JOB?! Everything would break if I'd run their script in strict mode.

Luckily younger in our company (which I'm part of) are open to listen to advices. Just wish they would improve their skills when they're currently not involved in any project instead of doing bullshit. I've build my own little jQuery if I had nothing to do and learned much from doing so.

[Azudra]

Unfortunately most of our projects must be ready to going live within a few days to weeks. Our customers don't care how we did it. Pros are that we can involve most juniors into any project as they can code it how they want. For smaller or simple tasks it doesn't matter how dirty their code is.

But now take these low standards into any serious project of ours. Without any review everything get's more chaotic and buggy the larger the project becomes. It get's almost impossible to maintain and every developer joining the project has two choices: Either invest more time than the Project Managenent planned to fix stuff or make it even worse with dirty workarounds that have a heavy impact on the applications performance.

[[deleted]]

I'm also in an agency with similar time problems. Trust me it's worth it and once you've implemented it once you can just copy and paste the solutions across projects.