These small dopamine hits
Some tasks are a slow grind, like simmering a big meal that takes hours to come together. Others are quick and satisfying—tiny fixes that deliver an instant hit of progress, like a little dopamine boost to keep you going.
Geoffrey Dhuyvetters
🌶️ Death by a 1000 tweaks: the absurdity of maintaining your own UI library
The best products aren’t built by obsessing over pixels but by delivering real value. Without a clear UI framework, teams drown in design tweaks instead of shipping features.
There is a time and place for everything: managed services vs DIY
Should you avoid managed services to prevent lock-in? Maybe. However, spending months reinventing infrastructure instead of shipping features is a bigger risk. Balance is key. Know the trade-offs, understand the costs, and make decisions based on your reality.
Learning from OSS: legacyBehaviour property on Next.js 's Link component
Ever introduced a breaking change and instantly regretted it? Components evolve, but forcing users into painful refactors isn’t ideal. Next.js tackled this with a legacyBehaviour flag—letting devs opt out of the new behavior while they migrate at their own pace.
Bridging the gap: how front-end engineers can help shape product development in smaller teams
In small teams, front-end engineers can bridge gaps in product clarity by refining goals, collaborating effectively, and using flexible tools to deliver features efficiently.
Introducing URL: The Zero-Dependency, Framework-Agnostic State Manager
Say hello to URL 🚀 We’re excited to introduce URL, a zero-dependency, framework-agnostic solution that simplifies state management for modern web development. No installs. No complex tools. Just pure simplicity.
Beyond junior and senior labels: Push and Pull developers
Labels like "junior" and "senior" often fail to capture a developer's true value. True impact comes from initiative, ownership, and proactive contribution—not just years of experience. We value "pull developers" who actively seek improvement, ensuring the product's success beyond assigned tasks.
On being an "expert"
Being an expert isn't about always having answers. It's about balancing confidence and humility, knowing when to admit you don't know, and valuing collaboration. True expertise grows through listening, learning, and contributing meaningfully, not just knowing everything.
Caching routes, components and functions with "use cache" in Next.js 15 (canary)
"use cache" is an experimental Next.js 15 Canary feature and may change. In this tutorial, we explore "use cache" for caching, covering fetching and inserting comments with Drizzle to reduce database calls and improve performance while maintaining control.
Instant feedback using the useOptimistic hook in React
Implement optimistic updates in React with the useOptimistic hook for instant UI feedback. This technique enhances user experience by updating the interface immediately while the server processes actions in the background, creating a faster and more responsive app.
Crossing boundaries: Handling data mutations in client components
Discover how to efficiently mutate data in client components using server actions in Next.js. Learn to handle form submissions with React’s evolving hooks like useActionState, eliminate the need for API endpoints, and streamline client-server interactions for faster, more responsive applications.
Crossing boundaries: Passing server data to client components in React
Learn how to optimize performance by fetching data server-side without blocking the page render. This guide explores passing promises to React client components and resolving them asynchronously using Suspense, ensuring a smoother, faster user experience.
“Fake” e2e tests with react-testing-library
How to run fake e2e tests using react-testing-librabry? Here's a quick tutorial on how to speed up your feedback loop when working in front end applications.
Tech debt & refactoring an old front-end codebase: a field manual
Improve your front-end project's performance and maintainability with our guide to refactoring a codebase. Learn about tackling technical debt, assessing your code, planning a strategy, and exploring refactoring techniques.
Why you don't need estimates
How should you estimate your work? Are estimations needed when developing software? What is the value of estimations? What is an alternative to estimating work?