He’d watched tutorials. He’d copy-pasted from Stack Overflow. Nothing worked. He was a fraud in a hoodie.
At the bottom of his "About" page, in tiny, almost invisible grey text, Leo added a line:
The parentheses. He’d added parentheses. He was calling the function when the component rendered, not passing the reference for the click event. React wasn't broken. His attention was. andrew mead react course
Leo followed along. He added the button. He wired the function. But when he clicked, nothing happened. The array of options stubbornly remained. He rewatched the video. He checked his syntax. He even typed Andrew’s code character for character. Nothing.
Six months later, Leo pushed "Task Atlas" to production. It wasn't perfect, but it worked. The map panned smoothly, the gig cards updated in real-time, and the state, for once, was a quiet, predictable river. He’d watched tutorials
Leo’s cursor blinked on a blank App.js file. Outside his window, the city was a grid of sleepy lights, but inside his apartment, the only glow came from his monitor. He was stuck. His side project, "Task Atlas," a beautifully interactive map for freelance gigs, had a bug that felt personal. The state was a tangled mess, updates lagged, and components re-rendered like a stuttering engine.
Then came the chapter that broke him: "Indecision App – The Remove All Button." He was a fraud in a hoodie
For the next three weeks, Leo didn't just watch. He built . He set up Webpack and Babel by hand, line by line, understanding the skeleton before the skin. He learned that state wasn't a mystery—it was just data waiting for a trigger. He grappled with setState() , feeling the click of comprehension when a button finally updated the UI without a full page refresh.