In the blockchain world, you must have heard about “Web 2.0” and “Web 3.0” frequently.But what do Web 2.0 and Web 3.0 mean? Which one is better? For us to make any sense of what we mean by “Web 3.0”, we need to rewind to Web 1.0 and start there.
Functional programming is one of the most powerful ways to learn how to write clean and scalable code. I truly believe every software developer could benefit with a little bit of foundational knowledge in functional programming.
Anyone who has embarked on this journey to learn how to code has came across this question. Your first thought might have been to google it. Next thing you know, you realize that the internet is filled with lots of good opinions. Too many good opinions.
Imperative vs. Declarative. Pure vs. Impure. Static vs. Dynamic.Terminology like this is sprinkled throughout programming blog posts, conference talks, papers, and text books. But don’t be turned off by this jargon. Let’s jump right in and break some of these concepts down...
The first programming languages I learned were JavaScript and Python, both of which are dynamically-typed languages. But my foray into static types have added a whole new dimension to how I think about programming.
Static types offer many benefits when writing programs. Let’s explore a few of them.
As a JavaScript developer, you can code all day long without encountering any static types. So why bother learning about them?Well it turns out learning types isn’t just an exercise in mind-expansion. If you’re willing to invest some time in learning about static types’ advantages, disadvantages, and use cases, it could help your programming immensely.
You’ve probably heard the expression “easy to reason about” enough times to make your ears bleed. The first time I heard this expression, I had no idea what the person meant by it. Does it mean functions that are easy to understand? Does it mean functions that work properly? Does it mean functions that are easy to analyze?
Internationalization is a big problem. If you want your application to make a worldwide impact, you have to deal with language barriers. Unfortunately, the road from “Your funds will arrive by July 7th” to “Vos fonds arriveront le 7 Juillet” is far from simple. Before your application can succeed outside the English-speaking world...
Closures are a fundamental JavaScript concept that every serious programmer should know inside-out. The Internet is packed with great explanations of “what” closures are, but few deep-dives into the “why” side of things. I find that understanding the internals ultimately gives developers a stronger grasp of their tools...
On a high level, module bundling is simply the process of stitching together a group of modules (and their dependencies) into a single file (or group of files) in the correct order. As with all aspects of web development, the devil is in the details. :) Why bundle modules at all?
If you’re a newcomer to JavaScript, jargon like “module bundlers vs. module loaders,” “Webpack vs. Browserify” and “AMD vs. CommonJS” can quickly become overwhelming. The JavaScript module system may be intimidating, but understanding it is vital for web developers.
There comes a time in every developer’s life when jQuery welcomes her into its dark underworld. That point when her code does gymnastics on the page, but collapses to a tangled mess underneath. You could hit the wall with this anywhere in your career. “Is this the norm?” you ask yourself.