Ok, first of all I’m assuming you know what Redux is and already used it in one of your projects. Now, after we established that, let’s move on. I always prefer to be clear in my assumptions and intentions. It makes life much easier :)

Yeah, I know, another library. But that’s okay, we’ll go through all of them and we’ll find the best one for each project. Or at least this is something that we should do as responsible developers.

I’m using a lot of git features via CLI. Mainly it’s rebasing, committing and pushing new changes to the repository. I know that most editors have UI solutions for these commands, but I never liked it and honestly don’t see any reason to change my habits. Stubborn you say? Probably. Don’t know.

The whole logic of styled-components can be described in one “feature request”: “Let’s manage CSS in js alongside with component core code”. The logic behind it is sort of obvious - it will give us the dynamic of js inside of CSS and we’ll be able to treat styling as part of component code and not store it in a separate file. The idea is promising, now let’s see what are some of the edge cases. And why is that? Because nothing is ideal in the world.

“Let’s play a game” I will give you a link to a form that is designed against all UI and UX norms and you’ll need to fill it as fast as possible. You can’t imagine how hard it could be when the designer deliberately is going against all codes that the industry agrees upon.

“Rewriting almost always feels a lot more appealing then gradual refactoring, but remember, that you’re comparing reality to a fictitious concept.” Always rewrite EVERYTHING! Sometimes I have a feeling that there is a tradition, in the developers’ community, that whenever you arrive at a new workplace, one of the first things you’ll do is to say that all this old code should be rewritten. This is rarely the case, but traditional ways are hard to stop or be replaced by something else, right?

I have already written a post about mocking moment.js for tests. Today let’s talk about how to use mocks in a specific tests framework - Jest. Jest was developed by Facebook and was based on another tests library called Jasmine. It meant that Jest used widely popular test syntax and could be adapted very easily.

It would be a long journey. Really, there were 17 sections, each one included from 3 to 26 videos. Each video was from 3, up to 16 minutes. This all added up to a very long course. On the other hand, what did you expect? To learn the profession in one sitting? Sadly it’s not the case. Of course, even after that course, you wouldn’t, by any means, be a good product manager. What you would lack would be real-world experience, but at least you would have a good start if you were dedicated and…

Breadcrumbs can be displayed in different ways. Usually, this is solved in a naive way - if a user enters the page where a certain product is displayed, then he will see breadcrumbs from categories that are hierarchically dependent on each other. This is reasonably easy to implement because it is static information. The more complex requirement is to display a history of the changes, where we’ll see not only the previous pages but also the filters that have been applied to them.

Errors will occur no matter what, but I hope that’s not stopping you from writing code because it doesn’t matter if you stop - someone else will continue the tradition instead :) So the only proper solution is to be prepared and to handle errors in the right way.