The latest articles on DEV Community by Binary Journal (@binaryjournal). https://dev.to/binaryjournal https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4027458%2F716a08b8-d1ec-4da5-b190-3371ca9f56e2.png https://dev.to/binaryjournal en Binary Journal Mon, 13 Jul 2026 15:03:55 +0000 https://dev.to/binaryjournal/the-day-i-stopped-learning-frameworks-and-started-learning-engineering-fnf https://dev.to/binaryjournal/the-day-i-stopped-learning-frameworks-and-started-learning-engineering-fnf <h1> The More I Learn, the Less I Google Frameworks </h1> <p>A few years ago, every new framework felt overwhelming.</p> <p>React.<br> Vue.<br> Svelte.<br> Next.js.<br> Nuxt.<br> Remix...</p> <p>It never seemed to end.</p> <p>Then I realized something.</p> <p>The framework wasn't the hard part.</p> <p>The hard part was understanding the ideas behind it.</p> <p>Routing.<br> State management.<br> Rendering.<br> HTTP.<br> Caching.<br> Databases.<br> Concurrency.</p> <p>Once those concepts clicked, learning a new framework became surprisingly fast.</p> <p>Frameworks are different.</p> <p>The problems they solve usually aren't.</p> <p>That's why I spend less time asking:</p> <blockquote> <p>"Which framework should I learn next?"</p> </blockquote> <p>And more time asking:</p> <blockquote> <p>"What problem is this framework trying to solve?"</p> </blockquote> <p>That question has saved me hundreds of hours.</p> <p>Has there been one programming concept that suddenly made everything else easier?</p> softwareengineering webdev programming career