It’s that time of the year when everyone is sharing love and gif(t)s with their closest ones. Such a pitty that I can only send you a browser cookie and not a real one; instead, I will share four React patterns that I would like you to take home and start using at the beginning of the next year.

New year, new pledges and new React patterns; every week until New Year’s Eve, I will reveal one React pattern that every React developer should know.

If you came across a problem (read challenge) while writing React components and if I faced the same problem as you, then it’s very likely that we’ve solved it in a similar way. Thus, we have a common software problem that we can solve using the same pattern. We can give it a name, describe it and share with other developers so that they can speed up their development process by using an already proven pattern; and this is what we call design patterns. …

It’s that time of the year when everyone is sharing love and gif(t)s with their closest ones. Such a pitty that I can only send you a browser cookie and not a real one; instead, I will share four React patterns that I would like you to take home and start using at the beginning of the next year.

New year, new pledges and new React patterns; every week until New Year’s Eve, I will reveal one React pattern that every React developer should know.

If you came across a problem (read challenge) while writing React components and if I faced the same problem as you, then it’s very likely that we’ve solved it in a similar way. Thus, we have a common software problem that we can solve using the same pattern. We can give it a name, describe it and share with other developers so that they can speed up their development process by using an already proven pattern; and this is what we call design patterns. …

It’s that time of the year when everyone is sharing love and gif(t)s with their closest ones. Such a pitty that I can only send you a browser cookie and not a real one; instead, I will share four React patterns that I would like you to take home and start using at the beginning of the next year.

New year, new pledges and new React patterns; every week until New Year’s Eve, I will reveal one React pattern that every React developer should know.

If you came across a problem (read challenge) while writing React components and if I faced the same problem as you, then it’s very likely that we’ve solved it in a similar way. Thus, we have a common software problem that we can solve using the same pattern. We can give it a name, describe it and share with other developers so that they can speed up their development process by using an already proven pattern; and this is what we call design patterns. …

Have you ever opened a project and left traumatised because you saw an incomprehensible and unmaintainable JavaScript code that you don’t want to touch even with an isolated rod? Because if you touch it, everything could crash just like one big Jenga block.

JavaScript is easy to pick up and start with coding but it is even easier to do it in a wrong way. For small projects, low quality code will not present high risk for a company but if a project gets bigger you will end up with a technical debt that will wade every deadline and eventually swallow you up. No one would ever want to touch this kind of code. …

When React came out I was really amazed with its easiness of use and learning curve. When I first started learning React I wasn’t aware of the fact that React is just a library and not a fully fledged framework. I wasn’t aware that I would need to make all decisions about architecture and what exactly I would need to use in order to solve some common tasks. Other frameworks would give you solutions and architecture out of the box which is not the case with React lib. …

So far, I’ve participated in seven different Hackathons — four national and three international. Some of them were successful and some were not. But, even in the latter ones, I’ve learned many different tips and tricks that helped me perform better and led me to wins too. Even though my insights may not be too useful for Hackathon-experienced devs, I believe they might be useful for those who have just began their Hackathon adventure.

Through this list, I will consolidate all the things I wish someone had told me before my first Hackathon. Tips & tricks given in this article are related to the software-oriented Hackathon. Before we dive into tips & tricks I need to say one thing — I don’t regret taking part in any of those hackathons, no matter of the results. Even if we didn’t win, I’ve gained invaluable experience and motivation for further learning and advancement. …