React code is full of hooks noise for state, references, memoization and effects and makes it hard to quickly scan a file and understand the main concepts because they are dominated by the lifecycle concerns. Something I started doing recently, after I [discovered this article](https://dev.to/decks...

Hey everyone! Wanted to share a performance optimization that made a huge difference in our paint-by-numbers canvas app built with React + PixiJS. **The problem:** We needed to show number labels (1-24) on thousands of pixels to guide users which color to paint. The naive approach was HTML divs...

I'm working on a tool to help my frontend team. They often struggle to style their 'Loading Skeletons' because the local API returns data instantly, and they can't test 'Error Toasts' because the API never fails. Currently, they hardcode delays in the fetch request or use MSW (Mock Service Worker),...

There is a lot of incoherency and grammatical mistakes that can be found in the docs; there are also logical mistakes that aren't being fixed. For example, the docs mention that setValue() will not create a new value if the field name is incorrect. See for yourself. The method will not create a new...

I’ve been getting into front-end recently and keep hearing a lot about Astro for content-heavy sites. Some people say it’s the future because of its performance and simplicity, while others think it’s just another hype framework that will fade away. Is Astro actually worth picking up in 2025, or sh...

I picked up an old side project recently to practice frontend and figured I would tune the bundle while I was at it. At first I did all the usual things. Played with code splitting and lazy loading, tweaked some images, nudged a few settings in the bundler. The numbers moved a little, then stopped. ...

When did things change? I started working with front-end development during the heyday of JSP and PHP, and although there aren't many pleasant memories from that time, as front-end development has become more and more popular, things have actually gotten more annoying....

Hey everyone, I've been using utility-class CSS frameworks for a few years now and love the DX. But I started noticing something on larger projects: pages with lots of components were feeling sluggish, especially on mobile. After digging into Chrome DevTools, I found the culprit wasn't bundle size ...

I somehow completely missed that modern browsers ship a **Web Speech API**. You can do text-to-speech (and speech recognition) with *no libraries*, just a few lines of JavaScript. No keys, no SDKs, no backend. What surprised me: * It’s supported in Chrome and Safari * Latency is basically instant...