Catch up on past deep dives into production-grade React, Node.js, and AI systems.
Today we read many success stories but there're many unsuccessful ones from which we can learn a lot. That's the purpose of today's articles - to share part of my (un)successful stories and learnings.
And why change and speed matter in today's world and competition.
In this article, I will share my opinion on how to structure your next Node.js project. In the past, I’ve worked on various projects both with Node.js and other technologies. A well-structured project is crucial for the developer experience (DE), scalability and maintainability of the application, testing, and much more.
The way how software companies work has changed. A new need has emerged — the need for T-shaped Developers.
I will walk you through my journey of migrating a React SPA from Bootstrap to Tailwind CSS. I will discuss the pros and cons of the architectural strategies considered during the migration. Then, I will move to the execution of the picked strategy and share some learned lessons throughout the whole experience.
Many software developers do not think a lot before picking either Bootstrap or Tailwind CSS. They go with Bootstrap when Tailwind CSS is more appropriate or vice versa. However, picking the right tool and technology for solving a problem is crucial.