JS be fun!

Testing is one of most misunderstood things in software development. I've seen this many times and this poor understanding of testing often affects negatively on projects. Let's see common flaws: Lack of unit tests and proper discipline around code acceptance - I worked for game company and we had games that were tested only by QA. And there were bugs. Every morning I logged into daily standup and almost everyday half of standup were "what is going from in which version of game" we had many similar games, catered and modified for different countries (regulations etc.) and seasons (e.g. Halloween edition). Moreover programmers ignored bugs during development and delayed fixing them. Testing the implementation. It's common mistake to tests directly everything. People often conflate two things: 100% testing coverage creating separate unit test for every class/function/method Many things can (and should) be tested indirectly. Testin...

JavaScript landscape seems very different now than it looked few years ago. There's ton of new bundlers/build tools. Esbuild, Vite for example. Build tools are now written partially in Rust or Go. How do you start React projects? Back in times there was Create React App. But who needs it? Starting app with Next.js is much simpler and more comfortable. I see also that Vite is popular. And managing state? Back in the day there was Redux... but it just seems too much of a hassle now, when you have functional component with hooks. Local state FTW! And when you need go global, there's React context. Managing state libraries are still used though. And Redux is used too, but it lost it's monopoly. There's many libraries which are used right now. And there libraries like ReactQuery that also manage fetching data. Something that was fucked up in Redux projects (not fault of Redux per se, but its ecosystem) When we talking about fetching data... I've got impression ...