We're all learning how to ship more side projects. If you're "in the bubble" it can feel like everyone is repo-maxxing. Shipping weekly. Spinning up agents to scaffold full apps overnight. New OSS dropped every Friday. The reality I see with most developers is much more normal: They have six or seven repos sitting in various states of half-attention. A side project from last year that still gets a
I watched 30 users talk to the same voice agent Same script. Same questions. The only thing I changed was the response latency: 300ms, 500ms, 800ms. At 300ms, people just talked. No awkward pauses, no confusion. One user didn't even realize it was an AI until I told her afterward. At 500ms, something shifted. Users started talking over the agent. They'd ask a question, wait half a second, then r
I have a confession: I used react-i18next for years and genuinely never questioned it. It worked. It was everywhere. Every project I joined during my internships at DNB had it set up. You install it, you configure it, you wrap your app in a provider, and you ship. Done. But then I started building more things on my own, projects where I got to choose the stack from scratch, and I started noticing
How intentional loading decisions keep your app fast at scale. Frontend performance is not a late-stage cleanup task. It’s not tech debt. It’s a set of decisions we make every day while we code — what we load, when we load it, and how we render it. The answer depends on the importance of the code, its size, and when the user actually needs it. Get that wrong, and the browser pays for everything
Is your website throwing 502 errors whenever an external API starts lagging? It is a common engineering grind where slow dependencies choke your server and kill your response times. The fix is not adding more resources. It is about changing how you handle work. Stop making users wait for external processes to finish. Offload heavy tasks to background jobs and queues. Distinguish between workers
Are you sure your server is performing at its peak? Understanding your server's capabilities is crucial for delivering a smooth user experience and preventing costly outages. This article will guide you through the essential tools and a practical methodology for benchmarking your server, ensuring it meets your application's demands. Before diving into the "how," let's solidify the "why." Benchmark
Exemplo mínimo de uso com Bun (baseado na documentação oficial) Aviso: Este exemplo é puramente acadêmico, baseado na documentação oficial do Next.js. Para um ambiente de produção real, ajustes adicionais de segurança, performance e monitoramento são necessários. 1 - Ajustar o next.config.ts para "Standalone": import type { NextConfig } from "next"; const nextConfig: NextConfig = { output: "