Do you know the meaning of the 12 most common acronyms and terminology in software development?
The easiest way to fail an interview is by not knowing the lingo for the industry you are applying for. If you are a software developer you better know the terminology. Not just for programming interviews but also so you can understand what project managers and others in your field are talking about.
This video concisely defines many of the common terms used in the software programming career. You can buy books defining some of these but you don't need that much information. Here's just the basics so you can talk intelligently, get that job, and communicate with your co-workers properly.
https://youtu.be/Nb-oAmF8t4k
(video updated 4/20/21)
"Javascript is an asynchronous language" - if you truly want to make a video about this topic, I suggest you inform yourself better.
This comment has been voted down. Click to show.
I think his point was more that it might not be a good idea to start teaching something unless you have at least a basic understanding of the concept, otherwise you can be spreading misinformation or guide other people on the wrong path.
This comment was deleted a year ago.
This video has a few mistakes.
This comment has been voted down. Click to show.
"synchronous" is misspelled in multiple parts of it. When speaking you refer to the U in CRUD as "Edit". Additionally, synchronous vs asynchronous as a classification of language doesn't really make sense. JS is as synchronous as PHP.
Thanks for pointing out the typos. I had hired a video editor and should have proofed their work more carefully!
I've requested the video-edit file and once I receive it I'll correct those issues.
While you are technically correct that JS processes commands in synchronous order, the fact is the results from the calls may be returned out of the expected order. Thus JavaScript is often referred to as having asynchronous processing. However you are correct that it is not an "asynchronous language".
But they aren't, they are always returned in order, but the result of applying a function (JS doesn't have "commands") might be a promise, which means something important. The way you are describing it is not, IMO, a helpful clarification. Pretty much all languages support this.
that was fun.