"So you have experience with Angular. And what about JavaScript?"

If you can write an Angular App doesn’t mean that you can also write a plain JS app

@Sumafu this

@Sumafu that's true, but you do have at least a basic understanding of Javascript

@GXGOW Partially you're right, but at the same time not necessarily; when you start learning a language together with a framework it can be hard to differentiate between core language features and framework/library features, and how one builds on the other.

As dumb as it often sounds when someone talks about learning the fundamentals first, it's actually the better approach long term.

I had this issue with Java and IDEs once. When you never wrote (Java) code outside of an IDE you can be very dependent on it, as it handles all the imports, builds and classpath stuff for you and if you never did that by hand you're basically fucked if you're in a hurry.

Also it helps to appreciate how well-designed some package is and how it compares to other frameworks when you know how the long way around looks.

This is exactly why I still list CSS, HTML, Javascript on my resume.

Even though I have SCSS and Angular already on there.

HR keyword scanning and resume bots are real.

@deadlyRants this.

I feel grateful for having learned django/jinja templating language before learning angular. You get a much better sense of how Ajax/HTTP requests, and context objects work.