The latest articles on DEV Community by Shiojee Singh (@shiojee). https://dev.to/shiojee 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%2F4069029%2Ffe38fa1d-f8c2-4a30-8552-d829829780f2.png https://dev.to/shiojee en Shiojee Singh Sat, 08 Aug 2026 16:33:07 +0000 https://dev.to/shiojee/what-i-wish-i-knew-before-starting-my-developer-journey-1lmo https://dev.to/shiojee/what-i-wish-i-knew-before-starting-my-developer-journey-1lmo <p>When I first started learning about development, I thought becoming a good developer meant knowing as many programming concepts, frameworks, and tools as possible.</p> <p>Over time, I realized it’s not really about knowing everything.</p> <p>It’s about being willing to learn, experiment, break things, get stuck, and try again.</p> <p>Here are a few things I wish I had understood earlier:</p> <p>You don’t need to know everything before building something.<br> Getting stuck doesn’t mean you’re bad at coding—it means you’re learning.<br> Documentation is one of your best resources.<br> Small projects can teach you more than endless tutorials.<br> Reading and understanding other developers’ code is incredibly valuable.<br> Consistency beats trying to learn everything at once.<br> Sharing what you learn can help both you and someone else.</p> <p>There’s always another framework, language, library, or tool to learn. The goal isn’t to catch up with everything—it’s to keep moving forward.</p> <p>I’m still learning, experimenting, and figuring things out myself. And that’s probably the best part of being a developer.</p> ai webdev productivity career