Writing code for the Web sometimes feels a little magical in that developers write a sequence of characters and like magic, those characters turn into concrete images, words, and actions within a browser. Understanding the technology can help developers better tune their craft as programmers.
- ? Understanding V8’s Bytecode — Franziska Hinkelmann
Okay, so technically for the computer everything goes down to 1s and 0s. It does not operate with digits or characters or strings, it uses only binary digits (bits). The short version of this explanation is that everything is stored in binary form. Then the computer uses encodings such as UTF-8 to map the saved bit combinations to characters, digits or different symbols (the ELI5 version).
- ? Programming with JS: Bitwise Operations — Alexander Kondov
- ? What’s the Document Object Model, and why you should know how to use it — Leonardo Maldonado
- ? ES6 Classes — Nathaniel Foster
- ? Basic Inheritance with Object.create — Joshua Clanton
Even if you don’t know what functional programming is you’ve probably been using map, filter and reduce just because they’re so incredibly useful and make your code stink less by allowing you to write cleaner logic.
So many of our bugs are rooted in IO related, data mutation, side effect bearing code. These creep up all over our code base—from things like accepting user inputs, receiving an unexpected response via an http call, or writing to the file system. Unfortunately, this is a harsh reality that we should grow accustomed to dealing with. Or is it?