From currying to closures there are quite a number of special words used in JavaScript. These will not only help you increase your vocabulary but also better understand JavaScript. Special terms are normally found in documentation and technical articles. But some of them like closures are pretty standard things to know about. Knowing what the word itself means can help you know the concept it's named for better.
- What is your role and responsibilities in your current project?
- Find common elements from two arrays? Without using any Ruby operator and tell me how would you write a program?
- How to find an element from an array? How it internally works?
- How to sort ruby objects based on particular object? For ex: [@user1, @user2, @user3, @user4] - Then sort it by user's salary.
- Explain MVC?
- What is the use of moving controller code to model?
- Tell me the internal flow of execution when I call some method? For ex: @object.some_method
- Computer Science: Offers in-depth resources for learning and improving your skills with computer science, programming, algorithms, data structures, and more.
- Operating Systems: Covers operating systems and their tools.
- Web Development: Offers abundant resources for topics like browsers, CSS, DOM, HTML, JavaScript, Node.js, PHP, and Python. It contains many different manuals, tools, libraries, shortcuts, and more.
This may be simple, but it allows to start a conversation between two strangers involved into the same craft.
Classes are a blue-print, they may hold data, likely they hold methods; classes are directly connected with an idea of objects, because object is an instance of a class. As objects are first-class citizens in Ruby, there is a main, root class Object, and all classes are inherited from this root entity. Modules, generally, are a tool for mix-ins and they provide something we call a namespace. Modules cannot be initialised the way we can do this with classes, but they provide a multiple inheritance.
# Basic example | |
siege -t60s -c20 -d10 'http://robertomurray.co.uk/' | |
# Basic auth; | |
auth=$(echo -n 'username:password' | openssl base64) | |
siege -t60s -c20 -d10 --header="Authorization:Basic $auth" 'https://staging.a-hostname.co.uk/' |
var EventEmitter = (function() { | |
var cache = new WeakMap(); | |
function EventEmitter() { | |
cache.set( this, {} ); | |
} | |
EventEmitter.prototype = { | |
#A curated list of great resources for the job search
###General Advice:
- How to ace an algorithms interview
- The Coding Interview
- List of great resources on resumes, negotiations, and more
- I'm a huge believer in the ability of good questions to change the tenor of an interview.
- How to interview your interviewers
Here are seven JavaScript concepts you must understand before you go into your next JavaScript job interview:
-
Prototypes - JavaScript is a prototype-based language. Even more, it's a delegation-based system, which means that each object has a prototype chain. When you try to access a property on an object, and that property is not found, JavaScript looks at the object's prototype. The prototype is a delegate object, which means that the property lookup is delegated to the prototype object. That object, in turn, may have its own prototype. The search continues up the prototype chain until it reaches the root prototype, which is usually Object.prototype. The best feature of this system is that many object instances can share the same methods on a prototype object, which conserves memory and enables easy code reuse. To assign a prototype to a new object, you can use
Object.create(prototypeObject)
. Prototypal OO is the first course being offered in the "Learn JavaScript" series. -
Functional Programming