30 posts

Some teams encourage new ideas. The other ones tend to bury any initiative. Let’s think:

1. What kind of teams made you enjoy sharing your concepts?
   What kind of teams discouraged you from doing this?
2. Why?

Let's take a fresh look onto the traditional "hard skills"-vs.-"soft skills" division.

A story of a really annoying bug.
Spoiler: reproducible only on production builds; locally works well 🤡

The color is fun. But smart color is way more fun. How to work with color in smart way in JS? How to translate from human language into RGB/HSL or vice versa?

So we finished previous part with the reference to the code of the demo (GitHub page). It’s fully working version. But let’s recreate it from scratch.

This is my presentation for the Next Build-2018.
Demo code on GitHub.

The instance of Array (under the hood: the Array.prototype) provides a bunch of methods for handling its content in functional way. Almost any array method can be substituted with another one.
Why? ― because JavaScript is so JavaScript.

Despite of we can, it doesn’t mean we have to. So let’s take a deeper look at array methods and decide what’s the proper use case for each of them.

There is one trick with Promises that might lead to nasty consequences: you might lose the async job. How it happens and how to avoid it?

Promises provide a pretty nice interface for async programming in Javascript.