The science behind the language plateau and my experience as a polyglot with it — I was recently interviewed by 🔘 Paulius Juodis for The Ink Well podcast and, during our conversation, we addressed the plateau effect. This is a very common phenomenon when learning a language. …

Be reminded about how bad your coding skills are every time your app raises an error — WARNING: This article has been moved to my company’s blog at writech.run. Donato Rimenti did it again! If you are not familiar with him, he is the developer behind the React PokeDom and GomorraSQL projects. The first one allows you to catch Pokédom hidden in the DOM of a web…

The forgotten language spoken by only a few thousand people (including me) — I was recently interviewed by 🔘 Paulius Juodis for The Ink Well podcast and, during our chat, I was asked what my native languages are. As you can probably tell from my name, one is Italian, but only a few people know that I am also a native speaker of…

Wait! You’re telling me I should say that I’m fluent in JavaScript? — I was recently interviewed by 🔘 Paulius Juodis for The Ink Well podcast and while chatting about language learning, he asked me a very interesting question: “Should programming languages be considered actual languages?” As a software engineer and a language learner — or in other words as a person who…

Stop random crashes in your Node.js server — One of the most annoying things in web development is to see your application crash for no apparent reason. If you have a Node.js backend that uses Express as ORM, you may have come across what seem to be random crashes. If you take a look at the logs, you…

Introducing a next-generation testing system based on artificial intelligence — Imagine being part of a software testing team whose goal is to ensure the quality of a web application. The team spends countless hours crafting end-to-end tests with technologies such as Selenium. As the project grows, the number of test scripts required increases exponentially, leading to an overwhelming amount of…

Addressing one of the most common errors of i18next in TypeScript — When dealing with i18next in TypeScript, you may have dealt with some type issues. These are pretty common because the t() function can return null, leading to some problems with variables that accept the undefined value. Here, you will learn why the error occurs and how to fix it! …

Understanding the differences between the three types of npm dependencies — If you ever dealt with npm, you must have noticed that package.json accepts different types of dependencies. Take a look at the following example: { "name": "my-app", "version": "1.0.0", "description": "Sample project", "dependencies": { "lodash": "4.17.21" }, "devDependencies": { "jest": "^27.0.6", "eslint": "8.43.0" }, "peerDependencies": { "react": "^18.0.0" } }

When dealing with Next.js middleware or headers in the next.config.js, you might stumble across the “source parse failed for route” error message. That is a common issue that occurs when you are not defining matcher or source values correctly. Let’s dig into this Next.js …