Having had a nearly 4-year career, I know this is relatively short, but I have worked for different companies with vastly different approaches. Along the way, I realize some things that as a student I could never have fully comprehended. Things that, had I known, might have saved me unnecessary stress and self-doubt. I share them here in the hope that it might help you on your journey. 1. Do Not Underestimate the Power of Documentation When I first started, all I wanted to do was write code and build features, which made me neglect documentation most of the time. More often than not, this is how this usually looked: something goes wrong in your code, and you go straight to Stack Overflow, find the solution, plug it in, and move on. However, even after those sessions in Stack Overflow, I wasn't getting knowledge or skill to handle that issue or similar issues in the future. In fact, without careful study of the documentation, there is no way to deeply understand the library or functionality - its strengths, weaknesses, etc. Well-written documentation is essential in building that deeper understanding. 2. It's More Important to Know "What" to Do Rather Than "How" A common beginner's mistake is focusing too much on learning every tool or technology. However, I’ve come to realize that it’s more important to understand what problem you’re solving than to know how to solve it. Tools and frameworks will constantly change; what’s popular today may be irrelevant tomorrow. But the ability to think critically, identify problems, and approach them logically is invaluable. Master the principles and fundamentals-these will guide your choices of tools and solutions. 3. Impostor Syndrome and How to Handle It One cannot know everything. When you're a student, it feels like there's some sort of threshold you can cross beyond which you can confidently claim you can do everything, but that's just not true. This syndrome may be present throughout your career. When you start getting overwhelmed by how knowledgeable others seem-like a conference speaker for instance - just remind yourself that it's most likely that you know something he or she doesn't know, perhaps even something most of the experts in that room don't know. And that is OK since nobody knows it all. 4. Learn, Learn, and Learn More The tech world moves fast, and standing still is falling behind. As you start your career, the finish line seems to get a degree or even the first job. In reality, it's just the beginning. Always be learning - new frameworks, languages, even soft skills like communication and teamwork. Your acceptance of continuous growth and ability to adapt will be your biggest asset over time. 5. Never Listen to the Alarmists Every industry has its doomsayers, those who spread panic and fear about the future. They will tell you the industry is dying, AI is coming for your job, or that you are doomed if you don't master the latest technology. Don't buy into it. Panic-driven thinking rarely leads to rational decisions. Stay focused on your goals, keep learning, and be adaptable. Like all industries, the tech industry has its ups and downs, but resilience and proactive thinking will pull you through those challenges. These are the things I want somebody to have told me before I joined the profession. Earlier in life, I would have been more confident and better prepared for the challenges of professional life. What might you say to your younger self? Having had a nearly 4-year career, I know this is relatively short, but I have worked for different companies with vastly different approaches. Along the way, I realize some things that as a student I could never have fully comprehended. Things that, had I known, might have saved me unnecessary stress and self-doubt. I share them here in the hope that it might help you on your journey. 1. Do Not Underestimate the Power of Documentation When I first started, all I wanted to do was write code and build features, which made me neglect documentation most of the time. More often than not, this is how this usually looked: something goes wrong in your code, and you go straight to Stack Overflow, find the solution, plug it in, and move on. However, even after those sessions in Stack Overflow, I wasn't getting knowledge or skill to handle that issue or similar issues in the future. In fact, without careful study of the documentation, there is no way to deeply understand the library or functionality - its strengths, weaknesses, etc. Well-written documentation is essential in building that deeper understanding. 2. It's More Important to Know "What" to Do Rather Than "How" A common beginner's mistake is focusing too much on learning every tool or technology. However, I’ve come to realize that it’s more important to understand what problem you’re solving than to know how to solve it. Tools and frameworks will constantly change; what’s popular today may be irrelevant tomorrow. But the ability to think critically, identify problems, and approach them logically is invaluable. Master the principles and fundamentals-these will guide your choices of tools and solutions. 3. Impostor Syndrome and How to Handle It One cannot know everything. When you're a student, it feels like there's some sort of threshold you can cross beyond which you can confidently claim you can do everything, but that's just not true. This syndrome may be present throughout your career. When you start getting overwhelmed by how knowledgeable others seem-like a conference speaker for instance - just remind yourself that it's most likely that you know something he or she doesn't know, perhaps even something most of the experts in that room don't know. And that is OK since nobody knows it all. 4. Learn, Learn, and Learn More The tech world moves fast, and standing still is falling behind. As you start your career, the finish line seems to get a degree or even the first job. In reality, it's just the beginning. Always be learning - new frameworks, languages, even soft skills like communication and teamwork. Your acceptance of continuous growth and ability to adapt will be your biggest asset over time. 5. Never Listen to the Alarmists Every industry has its doomsayers, those who spread panic and fear about the future. They will tell you the industry is dying, AI is coming for your job, or that you are doomed if you don't master the latest technology. Don't buy into it. Panic-driven thinking rarely leads to rational decisions. Stay focused on your goals, keep learning, and be adaptable. Like all industries, the tech industry has its ups and downs, but resilience and proactive thinking will pull you through those challenges. These are the things I want somebody to have told me before I joined the profession. Earlier in life, I would have been more confident and better prepared for the challenges of professional life. What might you say to your younger self?

Never Listen to Alarmist, and Other Career Advice I Would Give Myself If I Could Go Back in Time

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Exploring React Error Boundaries For A More Robust Application

What No One Told Me About Being a Product Manager at an Early Stage Startup

10x10: Ten Life Lessons from a Developer After Ten Years in the Industry

10 Things Every New Developer Should Know

10 Steps for Landing a Job at a Startup

Exploring React Error Boundaries For A More Robust Application

What No One Told Me About Being a Product Manager at an Early Stage Startup

10x10: Ten Life Lessons from a Developer After Ten Years in the Industry

10 Things Every New Developer Should Know

10 Steps for Landing a Job at a Startup

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps