The Developer Who Tried to Outsmart a Button

There was once a developer named Daniel who believed two things: Every problem had a logical solution. No button should take more than one click. He was wrong about the second one. Daniel worked in a quiet co-working space at the edge of the city. He wasn’t the loud type. No “10x developer” tweets. No dramatic keyboard smashing. Just headphones, a hoodie, and a browser tab count that would frighten normal people. He had been building a small productivity app in React for months. Not because it would make him rich. Not because investors were chasing him. But because of a button. A simple button labeled: “Start.” The feature sounded harmless. Click the button, start a session timer. That’s it. But Daniel wasn’t built for “that’s it.” The First Version The first version worked. It started the timer. It updated state. It rendered beautifully. But it felt… ordinary. So Daniel refactored it. He extracted the timer logic into a custom hook. Then he optimized re-renders. Then he introduced mem