When I first started learning HTML and CSS, I believed I understood web development quite well. I could follow tutorials, recreate designs, and build simple webpages. At that stage, it felt like I had learned enough to move forward confidently.
However, after taking a long break from coding, I returned and realized something important: knowing syntax is very different from truly understanding development.
I knew how to write HTML and CSS, but I did not fully understand how real projects were structured, how developers approached problem-solving, or how different technologies worked together in practical applications.
Instead of only watching tutorials again, I decided to focus on building projects consistently.
I started creating both small and larger projects using HTML, CSS, and JavaScript. After completing nearly 40 to 50 projects, I began to understand development in a much deeper way. Concepts that once seemed confusing gradually became clearer through practice and experimentation.
During this process, I learned:
=> how layouts behave across different screen sizes
=> how JavaScript interacts with the DOM
=> how APIs connect frontend applications with backend services
=> how debugging improves problem-solving skills
=> how project structure and clean code matter in real-world development
One of the most important changes in my learning journey came from exploring github(https://github.com/Nikita-05112000) more actively. I started studying open-source repositories, observing how experienced developers organized their code, and understanding how collaborative development works in practice. Exploring real projects gave me a perspective that tutorials alone could not provide.
At the same time, I became more involved in the developer community. I began writing articles on DEV Community(https://dev.to/nikita_maharana_879884df2) to document my daily learning sessions and share the concepts I was exploring. Writing regularly helped me strengthen my understanding while also improving my ability to explain technical topics clearly.
I also started sharing my work consistently on LinkedIn(https://www.linkedin.com/in/nikita-maharana-750580361/). Through this, I connected with more developers, interacted with people from the industry, and became more comfortable communicating my ideas publicly. Over time, I realized that communication is just as important as technical skills in a developer's journey.
Alongside building projects, I also practiced JavaScript extensively through freeCodeCamp(https://www.freecodecamp.org/). Their structured approach to learning helped me strengthen my fundamentals step by step. The combination of theory explanations, hands-on labs, quizzes, and practical projects made the learning process much more effective for me. Instead of only reading concepts, I was constantly applying them through coding exercises, which helped me understand JavaScript more clearly and build confidence through consistent practice.
This is also how I first came across Google I/O. I learned about it through LinkedIn posts and emails related to the event and the writing challenge. It felt genuinely exciting to see developers around the world sharing ideas, innovations, and experiences through a global platform focused on technology and learning.
Looking back, I now understand that real growth in development comes from building consistently, making mistakes, solving problems independently, exploring real-world projects, and engaging with the community.
Tutorials can introduce concepts, but projects and practical experience are what truly develop understanding.
I still consider myself a learner, but now I approach learning differently. Instead of focusing only on completing courses or watching videos, I focus on building, experimenting, and improving step by step through practice.
Top comments (0)