DEV Community

Cover image for What Would You Tell Someone Early in Their Career?
Hemapriya Kanagala
Hemapriya Kanagala

Posted on

What Would You Tell Someone Early in Their Career?

Community wisdom on avoiding early burnout

📌 TL;DR

I'm still early in my own career, and lately I've been thinking about how much advice we hear when we're starting out.

Learn this. Build that. Get certified. Network more. Specialize. Don't specialize too early. Work harder. Protect your work-life balance.

Sometimes it feels like everyone has an answer 😄

But careers are long, and I think some lessons only really make sense after you've lived through them.

That's what made me think about this community.

DEV has people at so many different stages of their careers, with completely different experiences. Some are just starting. Some have been working for a few years. Others have decades of experience. Some have changed careers entirely, managed teams, built companies, made mistakes, started over, burned out, found work they love, or discovered that what they thought they wanted wasn't actually right for them.

That's a lot of experience in one place.

So this post is a little different. I'll share some of what I'm learning while being early in my own career, but mostly, I want to listen to you.

What would you tell someone early in their career?

And there's no limit here 😄 If one thing comes to mind, share one. If you have five, ten, or a whole list of things experience has taught you, I'd genuinely love to hear them all. They don't have to be about the same topic either.

Talk about whatever you feel is worth passing on. It can be technical, personal, or somewhere in between: work, money, learning, managers, communication, confidence, health, work-life balance, mistakes, opportunities, relationships, or something completely different.

And if you're early in your career too, you're absolutely part of this conversation. Share something you've already learned, something you wish you'd known when you started, or something you're still trying to figure out.

And if you have a question, ask it. There might be someone here who's already been through exactly what you're wondering about and can share what they learned. And if it's something I happen to know or have experienced too, I'll be happy to share what I can.

My hope is that we can turn the comments into a place where people at different stages of their careers can ask questions, share experiences, and learn from each other 💙


📚 Table of Contents


This Post Is a Little Different

I had a slightly different idea for this post.

Usually when I sit down to write something, I have a topic I want to explore, an experience I want to share, or, apparently lately, a technical report that sends me down a rabbit hole for several hours 😄

But this time, I want to write a little less and listen a little more.

all ears

I'm still early in my own career. There are things I understand much better today than I did a few years ago, but I'm also pretty sure there are things I'll look back on five or ten years from now and think, “I really wish I had understood that earlier.”

Maybe someone has already told me some of those things and I haven't had enough experience yet to understand why they matter. Or maybe they're lessons I'll only learn by going through something myself.

Either way, it made me think about something I really like about communities like DEV: we're all at completely different points in our careers.

Some people here are just figuring out what they want to do, while others have been working for years or even decades. And even within that, no two paths look exactly the same. People change fields, become managers, go back to being individual contributors, build companies, take career breaks, start over, or watch their carefully planned career go somewhere completely unexpected.

Every one of those paths comes with lessons.

And that's what made me wonder:

What could those of us who are early in our careers learn from everyone else's experiences?


I'm Learning That There Probably Isn't One Correct Way to Build a Career

When you're early in your career, it's surprisingly easy to feel like you're doing something wrong.

You look around and someone seems to be learning faster than you, someone else just got promoted, and another person landed an opportunity you'd love to have. Some people already seem to know exactly what they want to specialize in, while others have incredible portfolios or somehow sound completely confident about where their careers are going.

And meanwhile, you might still be sitting there thinking, “I don't even know exactly what I want to be doing three years from now” 😄

i do not know

I've definitely spent time worrying about things like that myself. But I'm slowly realizing that careers probably aren't as linear as they sometimes look from the outside.

People change roles, discover that something they thought they'd love isn't actually for them, or become interested in something they never planned to pursue. They take breaks, make mistakes, change their minds, and sometimes start again. An opportunity that looks perfect might teach you what you don't want, while something that feels like a complete detour might end up being useful years later in a way you couldn't possibly have predicted at the time.

I think that's part of what makes comparing career paths so difficult. We usually see where someone is now, but we don't necessarily see all the changes, uncertainty, mistakes, and unexpected turns that happened along the way.

I'm still figuring out my own path, so I'm definitely not going to tell anyone exactly how they should build theirs. But one thing I'm trying to become more comfortable with is not having the entire map yet.

Maybe knowing where I want to go next is enough for now.

one step at a time


There's So Much About a Career That Doesn't Fit on a Resume

When we're starting out, a lot of our attention naturally goes toward the things we can show: the skills we're learning, projects we're building, certifications we're earning, our education, experience, and eventually the achievements we can point to.

And of course those things matter.

But the longer I think about careers, the more I wonder whether some of the lessons that shape them the most are things we'll never put on a resume.

Things like knowing when to ask for help instead of spending another five hours trying to solve something alone. Learning how to disagree with someone without turning that disagreement into a fight. Being able to say “I don't know” without immediately worrying that everyone will suddenly think you don't belong there.

Then there are decisions that don't always have an obvious right answer. How do you know whether an opportunity is genuinely good for you or just looks impressive from the outside? When should you negotiate, and when should you walk away? How do you deal with a bad manager, or eventually learn to become a good one yourself?

And some of the questions go beyond work itself. How much of your identity should your career take up? How do you stay ambitious without feeling like every free hour needs to become another opportunity to be productive? How do you take care of your health while still trying to build the future you want?

I don't think there's one course we can take that neatly teaches all of that.

learn hard way

A lot of it seems to come from living through things, making choices, getting some of them wrong, watching other people go through their own experiences, and slowly figuring out what matters to us along the way.

And that's exactly why I wanted to write this post.


Some of You Have Already Lived the Years the Rest of Us Are Just Beginning

That's something I think is pretty amazing when you really stop and think about it.

Someone reading this might be preparing for their very first interview, while someone else might be three years into their career. Another person might have fifteen or twenty years of experience, and someone else might have spent decades doing one thing only to eventually decide they wanted to start over in a completely different direction.

And all of that experience means much more than knowing different technologies or having different job titles.

People have worked with managers they loved and managers who taught them exactly what they wouldn't want to do if they ever became one themselves. They've made career decisions that worked out beautifully and others they probably wouldn't make again. They've negotiated salaries, accepted opportunities, turned others down, stayed somewhere too long, left somewhere too early, found mentors, and maybe eventually became mentors for someone else.

They've also had time to discover which worries actually mattered. Some of the things that felt incredibly important at the beginning of their careers might barely matter to them now, while things they hardly thought about back then may have turned out to matter much more than they expected.

And that's the kind of knowledge I'm curious about.

I'm not looking for another perfect career roadmap or a formula that says, “Do these seven things and you'll be successful.”

I'm much more interested in what people learned from actually going through it: the good decisions, the mistakes, the unexpected turns, and the things they understand now that they couldn't have understood when they were just beginning.


So... What Would You Tell Someone Early in Their Career?

This is the part where I hand the post over to you 😄

your turn

If you've been working for a while, I'd love for you to think back to the beginning of your career and everything you've experienced since then.

What do you know now that you wish you'd understood earlier? And what would you want someone early in their career to know?

Please don't feel like you have to choose just one thing either. You might have something to say about technical skills and something completely different to say about work-life balance. Your lessons might be about managers, communication, money, confidence, networking, changing jobs, burnout, asking for help, choosing opportunities, dealing with mistakes, knowing when to walk away, or something I haven't even thought to mention.

Maybe there's something you spent far too much time worrying about early on that you now realize wasn't nearly as important as it seemed. Or perhaps there's something you barely thought about at the beginning that you now wish you'd taken much more seriously.

And if your advice completely contradicts someone else's advice here, that's okay too. I'd actually love to see those different perspectives. What worked beautifully for one person might have been completely wrong for someone else.

You also don't need twenty years of experience to contribute. If you're early in your career too, you're just as much a part of this conversation. You might already have learned something from your first job, an opportunity you took, a mistake you made, a difficult experience, or simply something that's helped you along the way.

And if you feel like you're still figuring everything out, you don't need to have advice at all.

You can ask instead.

What do you wish you could ask someone further along in their career?

ask away

There might be someone reading this who remembers having exactly the same question and has already lived through the experience you're wondering about.

That's really what I'm hoping this discussion can become: not experienced people talking at people who are just beginning, but people at different stages of their careers learning from each other.


It Doesn't Have to Be Career Advice in the Traditional Sense

When we hear “career advice,” it's easy for the conversation to immediately become about what skill to learn next, which certification to get, or which technology to master.

And those conversations can absolutely be useful. But I think a career is much bigger than the technical skills required to do a job.

Maybe experience taught you to protect your weekends, start saving money earlier, ask more questions, find mentors, document your work, take your health seriously, make sure you have a life outside work, or stop comparing your entire career with the small part of someone else's life you see online.

Maybe it's something completely unexpected that I haven't even thought to mention.

Actually, those unexpected answers might be the ones I'm most curious to read.

Because sometimes the advice that stays with us isn't the advice we went looking for in the first place.


Why I'm Asking the Community Instead of Writing an Advice Post

I could have written an article called “Things You Should Know Early in Your Career.”

But that wouldn't feel quite right coming from me.

I'm early in my own career too. I have things I've learned so far and experiences that have changed how I think, but I also know there are situations I simply haven't lived through yet.

Instead of pretending otherwise, I'd rather ask people who have lived through them.

And experience doesn't only mean years worked.

Someone with twenty years of experience might share something that helps someone with two. Someone with two years might remember the uncertainty of starting out much more clearly. And someone entering the workforce today is experiencing things around AI, remote work, learning, and hiring that didn't exist in quite the same way ten or twenty years ago.

Different stages of a career teach us different things, and that's what makes this much more interesting to me than trying to write a career guide myself.


I Have a Feeling the Best Part of This Post Might Be the Comments

And honestly, that's what I'm hoping for 😄

I've had conversations here where someone left a comment that made me look at something completely differently, introduced me to an idea I hadn't considered, or brought years of experience to something I had only recently started thinking about.

That's one of my favorite things about writing in a community like DEV. You don't just publish something and walk away. Sometimes what you write starts a conversation, and that conversation ends up teaching you just as much as the article itself.

So maybe this post can become a little collection of experiences.

Not a definitive career guide.

Not a roadmap everyone is supposed to follow.

Just people at different stages of their lives and careers sharing what they've learned along the way.

Someone might come across a comment and think, “I really needed to hear that.” Someone else might discover an idea they hadn't considered before, or read a perspective that stays with them until they encounter that situation themselves.

And I fully expect to be taking notes too 😄

taking notes

So I'll leave this one with all of you:

What would you tell someone early in their career?

Share as much or as little as you'd like. If you have one lesson, I'd love to hear it. If years of experience have given you five or ten things you wish you'd known earlier, please share those too.

And if you're early in your career too, I'd love to hear from you just as much. Tell us what you've already learned, what you're struggling with, or what you wish you could ask someone who's been where you are now.

There isn't one correct way to build a career, and I don't expect there to be one correct answer here either.

In fact, I think the different answers are what could make this discussion useful.

So, what has your career taught you that you'd pass on to someone who's still near the beginning? I'd really love to hear it 💙


Transparency note: The banner image for this article was generated using DEV Community's built-in AI image generation feature. I wrote the prompt, generated multiple variations, and selected the final image used in this post.

I also used AI to help check my grammar and make sure I was expressing my thoughts clearly. English isn't my first language, so sometimes I know what I want to say but need a little help making sure the wording comes across correctly. The ideas, experiences, and perspectives in this article are my own.

Top comments (84)

Collapse
 
itsugo profile image
Aryan Choudhary

I don't have decades of experience yet, but there are a few things I wish someone had told me when I started.

  1. Don't optimize your career so much that you forget to live it.
    Early on, I felt guilty whenever I wasn't learning, coding, studying Japanese, building projects, or doing something "productive." It took me a while to realize that rest isn't falling behind, it's part of staying consistent.

  2. Fundamentals outlast trends.
    AI, frameworks, and tools will keep changing, but being able to think clearly, communicate, solve problems, and understand the basics has helped me far more than chasing every new thing.

  3. Find people who genuinely want you to succeed.
    A supportive community can change the direction of your career. I've learned as much from conversations with people here on DEV as I have from tutorials. Sometimes one encouraging comment is enough to keep you going when you're questioning yourself.

  4. Your career isn't a race against everyone else.
    It's easy to compare yourself to people getting promoted, shipping incredible projects, or writing amazing articles. What I've realized is that everyone is running a different race with different starting points. The only comparison that has consistently helped me is with who I was a few months ago. Though a little healthy competition is always favorable, a good balance is the best way to move forward in my opinion.

I'm still figuring things out myself, but if I could summarize everything into one sentence, it'd be this:

Build a career that you can sustain, not one that only looks impressive from the outside.

Thanks for opening this discussion, Hema. I have a feeling I'll be taking notes from the comments too. 😄

Collapse
 
leob profile image
leob

This:

"Your career isn't a race against everyone else."

and

"What I've realized is that everyone is running a different race with different starting points"

So true ...

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Very true. It's probably one of the easiest things to forget, especially with social media making it so easy to compare ourselves with everyone else.

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Aryan, thank you so much for sharing this. And thank you for always being so supportive on my posts.

I loved so many of the points you made, especially the one about building a career that's sustainable instead of one that only looks impressive from the outside. I think that's something a lot of us, especially early in our careers, need to remind ourselves of.

And I completely agree about community too. I've learned so much just by talking to people here on DEV, and this comment section is already becoming exactly what I was hoping for.

I'm already taking notes as I read through everyone's comments, and I'm learning something new from each one 😄

Thanks again for taking the time to share all of this 💙

Collapse
 
energeticpixels profile image
Anthony Jackman

Absolutely!! Doesn't just apply to the devsecops world but any career!!

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala • Edited

That's what I've been thinking after reading these comments. Even though we all come from different backgrounds, so many of the lessons are universal.

Collapse
 
xulingfeng profile image
xulingfeng

My advice: learn to steal time for rest. Don't let work fill every hour. Rest properly when it's time to rest, and slack properly when it's time to slack. Take care of your body. We're not machines. Even machines need maintenance — they wear down, they need oil, they need replacement parts.
Most of my best ideas and clearest directions have shown up when I was relaxed, not when I was grinding. Urgency gives you quick answers. Stillness gives you the right ones.
P.S. That's just my experience. It may not work for everyone, haha.🤣

Collapse
 
klaudiagrz profile image
Klaudia Grzondziel

Good that you mentioned it @xulingfeng ! 💯 The bitter truth is, if you do not give your body proper maintenance, it will force you to do it sooner or later. And it will take more time and effort to get back to normal.

Collapse
 
xulingfeng profile image
xulingfeng

@klaudiagrz So glad this resonates! Health really is the real currency. Nothing sadder than grinding away when you're young, earning all that money, only to pay it back as medical bills later.😂

Thread Thread
 
klaudiagrz profile image
Klaudia Grzondziel

earning all that money, only to pay it back as medical bills later.😂

omg, I wouldn't summarise it better 😂

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

I love this 💙 I think a lot of us forget to rest until something forces us to slow down.

It's actually something I'm still learning myself. Taking care of our health and giving ourselves time to recharge isn't time wasted. Like you said, we're not machines.

Thanks for sharing this. I think it's a reminder a lot of us need 😀

Collapse
 
unitbuilds profile image
UnitBuilds

Master Oogway, I see you're still sharing wisdom 😂 (Kung Fu Panda is best movie, cant tell me differently)

Like he once said: "Your mind is like this water, my friend. When it is agitated, it becomes difficult to see. But if you allow it to settle, the answer becomes clear."

That sentence will become clearer with each ring in your years (tree reference). We tend to rush everything, a bug... IN PRODUCTION!!! Panic causes you to rush, you disrupt the surface of the water, you panic and you deploy a hot-patch that fixes that problem, but doesnt guard everything... Instead, take it as a bug-tester discovery, they pointed out 1 failure vector for you, your job is to guard it properly. That's the difference between 'these stupid clients keep using the system wrong' to 'wow, these clients actually let me know where the flaws are in my code, so I can fix it'. Same scenario, different mindsets, night and day in patch deployment time and future robustness. Take your time, do it right, so you only have to do it once... Else you'll end up fixing it forever instead of having fixed it forever.

Also, I'd add to it, share your problems, so you can outsource solutions. You never know how much it helps, until you experience it and finding people kind enough to help is worth it every time. As is KFC, but that's besides the point (and not just cuz I live in a town without one 😭)

Collapse
 
xulingfeng profile image
xulingfeng

Absence makes the heart grow fonder, right? You'll never get tired of KFC, but I've eaten enough of it to last a lifetime, haha🤣

Collapse
 
technogamerz profile image
𝐓𝐡𝐞 𝐋𝐚𝐳𝐲 𝐆𝐢𝐫𝐥

After reading this, I thought, “That’s it, I’m done with stress. I’m going to relax from today.
Then my brain said, “Sure… but what about tomorrow?” 🤣

Collapse
 
xulingfeng profile image
xulingfeng

Easy — leave tomorrow's problems to tomorrow's you. And if that fails, just hop in a time machine, drag future-you back here, and put them to work. 😂

Thread Thread
 
technogamerz profile image
𝐓𝐡𝐞 𝐋𝐚𝐳𝐲 𝐆𝐢𝐫𝐥

The time machine’s gone for repairs. Doremi said it should be fixed by the day after tomorrow.

Collapse
 
jonrandy profile image
Jon Randy 🎖️ • Edited

Over 30 years experience here...

  1. Never waste time on estimates. Better still, just refuse to do them. Complete waste of time
  2. Question everything - never accept things blindly. Try to understand as much as possible
  3. Automate the boring donkey work whenever possible - save your effort for the fun, interesting stuff
  4. Always push back against poor decisions - especially against user-hostile design and dark patterns
  5. Try to treat it less as a career and more a fun hobby that you're lucky enough to get paid for
  6. Learn new stuff through curiosity and play - it will sink in better than 'formal' learning
  7. Certifications are a waste of time
  8. Never do technical preparation for an interview - the only preparation you should do is on things you don't know (i.e. learning about the role and the company). You should already be relaxed and confident about your abilities. The best advice I ever received on this was from my high-school physics teacher - "Revision is for wimps"
  9. Never do overtime unless it is an absolute emergency (which is very rare) - you work to live, not live to work
  10. Prefer manual testing over trusting automated tests - you'll learn and understand more about the codebase
  11. Don't pigeonhole yourself as a particular kind of developer... do whatever interests you
  12. Don't take jobs purely for the money
  13. Job titles are largely meaningless - don't chase them
  14. There's nothing wrong with reinventing the wheel sometimes - you'll gain a much deeper knowledge of wheels, and may even make a better one
  15. Diving straight into code is often the BEST way to start a project - despite what you're told about planning. Exploring the problem space through experimenting and testing ideas is often the best route to a solution
Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you for taking the time to share all of this! I really enjoyed reading through it.

The idea of treating it less like a career and more like a hobby you're lucky enough to get paid for made me think. I don't think I've heard it put quite that way before, but I can definitely see how that mindset could make a big difference over the long run.

Your point about learning through curiosity and play really resonated with me too. I always find I remember things much better when I'm genuinely interested in exploring them instead of feeling like I have to learn them.

Can I ask you one question? After more than 30 years in the industry, how have you managed to keep that same curiosity and enjoyment, especially with how much technology has changed over the years?

Thanks again for taking the time to share your experience 😀

Collapse
 
jonrandy profile image
Jon Randy 🎖️ • Edited

After more than 30 years in the industry, how have you managed to keep that same curiosity and enjoyment, especially with how much technology has changed over the years?

In work, I always try to steer away from roles and projects that are too similar to things I've done before - not always possible, but if you manage it then things should remain interesting. Also, try to maintain habits of:

  • Reading the more obscure stuff about development - it will fire your imagination and help you to think 'outside the box'
  • Coding for fun. If you have the time - just build random stuff, try out all your crazy ideas, play with code. Never take on the mindset of 'I have to make something useful that solves a problem' - that is the death knell to creativity

I think the fact that the tech does change so much helps to provide many avenues for curiosity - always new toys to look into if they take your interest.

Thread Thread
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you for taking the time to answer my question, Jon.

I really enjoyed reading this. I don't think I've come across many people who look at learning and work in quite this way, so it gave me a different perspective.

I also like what you said about building things just for the fun of it. I think it's easy to fall into the mindset that everything we build has to be useful or productive, when sometimes just exploring an idea is where we learn the most.

And you're right, technology changing so quickly does give us endless opportunities to stay curious and keep learning. I hadn't really looked at it from that angle before.

Thanks again for taking the time to share your experience. I learned a lot from this conversation 😀

Thread Thread
 
jonrandy profile image
Jon Randy 🎖️ • Edited

You answer in a manner suspiciously like an AI 🤔

[EDIT] Unfortunately - almost every one of your responses is also coming back as 100% AI generated when tested on zerogpt.com

Thread Thread
 
hemapriya_kanagala profile image
Hemapriya Kanagala • Edited

English isn't my first language, and honestly I get quite anxious when I'm replying to people here. I usually know what I want to say and write my own thoughts first, but sometimes I'm not sure if I'm expressing them correctly in English. That's when I use AI to help me improve the wording or grammar.

The thoughts, experiences, and things I'm trying to say are still mine. I'm not just giving AI a comment and asking it to come up with a reply from nothing. I usually write what I want to say first and then use it to help me make sure I'm communicating it clearly.

I'm trying to use it less though, because I do want to get better at replying and have more confidence in my own voice. I'm sorry if some of my replies have come across differently. I really do read the comments and think about what I want to say, it's just the English part that I sometimes struggle with.

And yes, even this reply, I used AI because I wasn't sure how to explain this properly. I hope you understand, and sorry about that.

Thread Thread
 
jonrandy profile image
Jon Randy 🎖️

I understand, but at the same time I think most people would appreciate hearing directly from a human. It would also help you gain confidence by writing your own replies.

Thread Thread
 
hemapriya_kanagala profile image
Hemapriya Kanagala

I will keep this in mind as I move forward and use my own writing for replies, even though it might not be perfect. It's just that I have had some bad experiences in this regard previously, and that makes me doubt my own voice while I'm replying, and it makes me question whether people will still be kind or if the bad experiences will come again. But yes, thanks for being kind and understanding. (I did reply by myself here without checking with AI, so I hope I am getting it right and you can understand)

Thread Thread
 
francistrdev profile image
FrancisTRᴅᴇᴠ (っ◔◡◔)っ • Edited

Thanks @hemapriya_kanagala and @jonrandy when bringing this up.

I understand these bad experiences and we all have those bad experience to a degree.

I remember back then, I was a type of person who talks a alot to the point people didn't like me because I was too energetic. Right now, I am still who I am, but people tend to be more accepted because we are all adults. We are mature and we are all grown to respect others.

I come to learn that sometimes, it's not universal. Just because it happened as a result of speaking, does not mean it will happen 100% of the time. Besides, if you got bad experience because you spoke not-perfect English, that tells them more about who they are than about you!

Collapse
 
kenwalger profile image
Ken W Alger

@hemapriya_kanagala This is a very interesting topic for those of us who have been around for a while, regardless of industry, but technology in particular. I wrote a little bit of my journey here not too long ago, but I think there are some nuances to the advice I'd give for early-career folks. Some of which echo what has already been mentioned, but here's my top few takes on things:

1) As others have said, make time for yourself throughout the day/week/month/year. Days may seem long at times, but years wind up flying by. Make sure to stop and smell the roses (as it were) along the way.
2) As a follow-up to #1 here, find an outlet that is outside the industry in which you work. Resist the urge to "add technology to everything." Meaning: if you are a software engineer and enjoy gardening, don't try to automate every aspect of garden management.
3) Learn the fundamentals. This is true across every industry I've been involved with, not just technology and programming. "Hot" languages and frameworks come and go. Fundamentals are there across it all, and once you've learned those, the syntax and implementation come easier to understand in new languages and frameworks that you might want to use.
4) Work in places that align with your interests. It is much more enjoyable to work in places where you enjoy the mission, rather than just taking "a job." Meaning, and this is a very simplistic version of things, if you're a dog person, don't focus your time working in the cat industry.

I think we're in an interesting time at the moment. With a few exceptions, gone are the days in which a career is strictly linear, and you end your career at the same place you started in an uninterrupted timeline. Take your experiences with you as you go and see how they fit into your current role. You'd be surprised at the knowledge I gained from delivering newspapers on my bicycle (yes, that was a thing, and I am that old) as a grade schooler still shapes me today.

Sorry for the ramble here. It's an interesting subject that I've had many conversations with interns, new graduates, and early career folks about. Happy to expand further in comments or 1:1.

Best,
Ken

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala • Edited

Thank you so much for taking the time to write all of this, Ken (@kenwalger).

Please don't apologize for the ramble! This is exactly what I was hoping this post would become. Reading through everyone's experiences and learning from people who've already been through different stages of their careers is the whole reason I wanted to write it.

I liked what you said about having something outside of work that's just for you. I think it's really easy, especially early in a career, to feel like every hobby has to become another way to learn or be productive. That's definitely something I'm still learning myself.

And I really liked your newspaper story too. It's a good reminder that experiences don't have to look important at the time to end up shaping us later.

I'd also love to read the post you mentioned, so I'll definitely check it out.

I wanted to ask you something too. Since you've had so many conversations with interns and people early in their careers, is there one piece of advice you find yourself repeating over and over because it's the one people tend to overlook the most?

And one more question. Looking back now, is there something you wish someone had convinced you of earlier, but you only really understood after experiencing it yourself?

Thank you again for taking the time to share all of this 💙

Collapse
 
kenwalger profile image
Ken W Alger

I think the "one thing" I mention is that you need to figure out what your one thing is. If you haven't watched City Slickers (1991), there's a scene in there that hits on this theme. Language Warning Scene here.

Beyond that, on a more practical side of things, the conversations I have tend to be more nuanced than a single "silver bullet" answer, as it really depends on one's goals. Some folks want to get into the C-Suite. Some want to learn what they can and start their own business. Some just want to make a ton of money. Some are passionate about a cause. The path to get there varies. And, honestly, the goal can change along the way. Get comfortable with change. It happens.

And I think that's an important lesson that you wind up learning after going through life, especially in the tech industry. Get comfortable with change. Be it a change in language, framework, trends, companies, etc. Change happens frequently, often due to factors well beyond our control. Corporate decisions are made based on the bottom line, and what makes sense today may not pencil out next week. And then, :poof: your team/division gets reorganized or disbanded. Remember that corporations are responsible to their shareholders, not to the engineer who implemented a great feature, the marketer who writes amazing content, or the salesperson who consistently hits a quota. If a division of a company doesn't fit the overall corporate goals, everyone is disposable.

Again, sorry for the ramble, and I'll stop before this turns into more of a rant.

Thread Thread
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you for taking the time to answer both of my questions, Ken.

I really like what you said about figuring out what your own "one thing" is. I think it's easy to spend a lot of time looking at everyone else's path instead of taking the time to think about what we actually want ourselves.

And I also found what you said about change and corporations really interesting. Being early in my career, it's not something I've experienced yet, so hearing that perspective from someone who's been through it is really valuable. I think it's a good reminder that while we can't control every change around us, we can keep learning and adapting as things evolve.

And honestly, I don't mind the longer replies at all. This is exactly why I wanted to open this discussion.

Thank you again for taking the time to share your experiences and answer my questions. I've genuinely learned a lot from this conversation, and I have a feeling others reading through the comments will too 😀

Collapse
 
thormeier profile image
Pascal Thormeier

I got roughly 2 decades under my belt now. Here's my 2 cents:

  • Sometimes, a good night's sleep is the best debugging tool. When you're stuck, get away from the problem. Give it a few hours, don't stare at the problem until 10pm, but call it a day once you're stuck and get back to it tomorrow. More often than not, you'll find the solution within the first 15 minutes the next day.
  • Don't compare yourself to others all the time. It's unnecessary pressure that no one benefits from. Don't get me wrong, though, looking up to people is perfectly fine, but see them as "you can be that good!" instead of "I need to be this good, too." Aiming high and seeing how much potential one can have is different from trying to force yourself to comply with some arbitrarily set standards.
  • Do what is fun to you. If you're into building 3D stuff, go ahead! If you're into crafting beautiful frontends with an extra focus on accessibility, go for it! Chances are you'll be more successful if its also fun to you, since you're more invested, emotionally.
  • On the same note, see what other skills could benefit you in mastering your favorite niche. Perhaps an in-depth UX course gives you a different angle on your frontends? Maybe a course in vector geometry helps you understand 3D stuff even better? Computer science is rarely isolated and often adjacent to other skills. For example, imagine a client project that's highly dependent on specific research data. Let's say genetics. If, in this case, you understand biology, chances are your solution fits the problem better.
  • The best code is the code that's never written in the first place. Meaning: If you can solve a problem without writing code, you have a solution that you don't need to maintain. Software engineers are first and foremost problem solvers. Code is the tool we use to solve problems if no other solution works.
  • You'll mess up eventually. And that's fine. Unless you work in a field with fast-moving things (cars, planes, etc.) or where the machine you work on is directly involved with anyone's body functions (i.e. medical pumps, etc.), there's a high chance that whatever you messed up did not cause that much damage. Large financial loss? That's what insurances are for. Someone can't work for half a day? Perhaps they'll be mad for a few hours, get another coffee and forget about it the next day. A friend of mine once asked me after a failed deployment "did anyone die?" to which I answered no, and their response was "so it's not so bad!"
  • If you mess up, own your mistakes. Trying to cover them up doesn't help anyone, neither does shifting blame. Make mistakes, as many as you can, but each of them only once. Once a mistake is made, inform relevant people and form a plan on how to mitigate damage. Never making a mistake is less impressive than making one, owning it, fixing it and being proactive about it.
  • If someone else messes up: Don't blame, but help. If they apologize, that's alright, but try to shift the mindset from problem-oriented to solution-oriented and make them take part in the solution. If they apologize, a possible answer could be "Everyone makes mistakes, don't worry. How could we quickly resolve this?" That way, they feel better about themselves, the problem gets solved quicker and it's less of a "this person specifically bad" and more of a "how could we prevent this in the future".
  • If you solve a problem within 10 minutes that other experts in your team couldn't solve for days or weeks, chances are you didn't understand the problem. The Dunning-Kruger effect is real. Be aware of it at all times.
  • If you're given a task that seems too complex for you, that you're afraid to touch because it's so large, do it anyways. Growth comes from stepping outside your comfort zone. In the worst case you learned something, in the best case you rocked it and people trust you more.
  • There are no stupid questions, only lack of knowledge, and that can be fixed. That's what questions are for. Words like "simple" or "easy" are highly subjective and should be avoided at all times. You don't want to feel stupid, so don't make others feel stupid by belittling them over a question or because they struggle to do something that anyone considers "simple" or "easy".
  • Once you're a little more senior, you'll eventually work with juniors. Treat them well, respect them and teach them, no matter how you yourself have been treated. Each and every interaction with a junior is a learning opportunity for all. Seniors can learn by listening to a fresh new angle on a problem, juniors can learn from the senior's expertise.

Ok, that was half a blog post... Might come up with some more later on lol

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Hey Pascal, all of these points are really helpful to me as I am still early in my career. The first point was really true; whenever I was stuck on a project during my master's and working late nights on it, I usually wasn't able to figure it out, but as you said, whenever I took a good break and came back with fresh eyes, I somehow ended up with a solution.

But if you do not mind, I would love to ask something regarding communication. From what I know, there is a lot of speaking involved in tech, like it could be talking to our team, explaining our ideas, asking questions in meetings, or it could be presenting something like what we worked on.

So, I am actually trying to get good at public speaking or communicating with others without getting nervous. I usually have the content in my mind, but I fumble sometimes, and that makes it sometimes hard for me to recover and get back to the point I am speaking about, especially if the situation is stressful, let's say interviews as an example. So, I would love to hear your thoughts on this one.

Collapse
 
thormeier profile image
Pascal Thormeier

Thank you for the feedback, glad my thoughts help! :)

Very good and valid question. Tech is, indeed, more communication than anything else. Yes, a good chunk is all the logic and knowing your tech etc. etc., but team work is communication, and large projects are team work.

I'd ask myself why I'm nervous to begin with. Is it that I'm afraid of being ridiculed or not be taken seriously? If so, why? Do I not trust my own expertise on this? Do I struggle with having a lot of people listen to me all at once? Or something entirely different? Perhaps a bad experience in the past? All of these reasons are valid. In fact, every reason to be nervous is a valid reason. For me, it comes down to handling the reason more than the nervousness itself and from my experience, people are often way more forgiving about nervousness than one might think.

I think the key is to take your time and be honest. Don't rush it and prepare. For example, if you present something, take your time beforehand to prepare some notes. If you want to ask a question in a large meeting, write it down before asking. In interviews, deliberately think about the answer. Nobody will kick you out for thinking about a question for 5 seconds. If you struggle with the words, tell them that you're nervous because of the situation. It's not your fault for being nervous and trying to hide it doesn't help you. If being nervous is the reason I didn't get a job, I'd ask myself if I really want to work in such a competitive environment at all.

Practicing can help you a lot, but you also need to know yourself and find other strategies to deal with it. For example, a friend of mine does regular talks at large conferences, and they take their shoes off on stage, which they usually only do at home, to force the brain into a "I'm in my living room" situation. The very first slide is also usually a "I have severe stage fright, let's all shout 'yay' and jump to loosen up a bit".

Additional hack: When answering crowd questions at a presentation, the phrase "That's a great question! Could you elaborate a bit more?" gives you additional time to think of an answer ;)

Does that help?

Thread Thread
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Yes, that helped, Pascal. I will try to sit with myself and will list down the actual root cause why I am nervous to begin with and work on it from there. But as you said, practice is not enough; I will try to find a startegy which can make my nervous system calm rather than going the opposite, because, as in the example you said of your friend, I see that the feeling of a safe environment helps a lot.

Also, love the additional hack 😄 Thank you so much for taking the time to explain all of this to me, means a lot.

Collapse
 
dharshan_dev profile image
Dharshan Programmer

Well Said The Roadmap

Collapse
 
webdeveloperhyper profile image
Web Developer Hyper

I'm not a senior developer yet, but I'm keeping in mind that I need to improve both my deep expertise and my broad development skills. However, life doesn't always go as I imagine. So, let's keep improving! 😄

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

A big yes to this. I am also trying to stay updated and learn as much as I can. But yes, life doesn't always go as we planned, and it happened for me too, so because of it I learned to be more flexible and keep improving, as you said, rather than think about the past.

Also, looking forward to your updates on AI Avatar 😀

Collapse
 
jenatechio profile image
Jennifer Smith

Twenty-five years in, the advice I would give my early-career self is to keep a written inventory of what I have personally seen break and what fixed it. The technology stack rotates out from under you every few years, but the catalog of failures you have debugged compounds forever, and it is the one asset that transfers intact across stacks, roles, and even careers. Start the inventory now, because the years when you are sure you will remember everything are exactly the years you won't. It will be invaluable as a record and framework you can always lean on in any role, and serve essential talking points for interviews to come.

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Loved this advice, Jennifer. I also happen to see that many of the people around me usually say they wish they had documented more since the beginning, as you said it would be really helpful in interviews. Also, I think it is a great way to look back on our journey and see how much we have solved and progressed throughout our careers.

Collapse
 
jenatechio profile image
Jennifer Smith

Hemapriya — the "look back and see how much we solved" part is real, though the thing that surprised me is that the record earns its keep when it is unflattering rather than when it is impressive. The entries I get the most out of are the ones where I wrote down the wrong diagnosis next to the eventual fix, because the wrong diagnosis is the part that repeats, and reading it back is what stops me from making the same wrong call a second time. For anyone who wants to start today, the smallest version that works is one dated line written at the moment the thing gets fixed: what broke, what I thought it was, and what it actually turned out to be. I still keep mine exactly that way, and it is the only document I own that has gotten more valuable every year instead of going stale.

Collapse
 
shubhradev profile image
Shubhra Pokhariya

This is such a thoughtful question, Hema. 😊

If I had to pass one thing on to someone early in their career, it would be: have a clear vision, but stay flexible about the path you take to get there.

I like having a bigger picture in mind and then giving my full attention to the step I'm working on. I don't think we need to keep changing the destination just because something unexpected comes along. But if we discover a better way to get there, I think it's important to be open enough to change the route.

And one thing I've learned along the way is that not every problem needs to be solved right now. When you're stuck, it's tempting to keep pushing because you feel like you should be able to figure it out. Sometimes the better thing is to step away for a while, let your mind reset, and come back to it later. Very often, looking at the same problem with a fresh mind helps you see something you couldn't see when you were forcing it.

That's something I've carried with me throughout my journey with coding. I've never felt the need to have everything happen at once. I make a plan, take the next step, learn from it, and keep moving forward. And I still genuinely enjoy learning, building, teaching, and keeping up with how the field evolves.

I think that's one of the things I love about software development. You can have a long-term vision, focus completely on what you're doing today, and still be open to learning something that changes how you approach the next step.

And I really like that you opened this as a conversation rather than giving everyone a fixed roadmap. There are so many different paths into this field, and I think hearing how people actually approach them is far more valuable than a single formula. I'm looking forward to learning from the comments too. 😊

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much for sharing this, Shubhra 😀

I really liked your idea of having a clear vision while staying flexible about the path. I think that's something a lot of us need to remember, especially when things don't go exactly as we planned.

I also completely agree about stepping away sometimes. It's so easy to keep pushing because we feel like we have to solve something right away, but I've found that taking a break and coming back later often helps me see things much more clearly.

And thank you for what you said about the post too. That was exactly what I was hoping for. There are so many different journeys here, and I think we can all learn something from hearing how other people have approached theirs.

Really appreciate you taking the time to share your thoughts 💙

Collapse
 
phalkmin profile image
Paulo Henrique

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you, Paulo! I think a lot of people, myself included, need that reminder from time to time 😀

Collapse
 
vinimabreu profile image
Vinicius Pereira

Lovely question. Mine: the years that feel like a detour are usually the foundation. I spent my early career doing statistical risk modeling at a credit bureau while friends were shipping apps, and it felt like falling behind. Years later, that is exactly what separates my AI work from the crowd: I knew what a model getting it wrong costs before it was fashionable to ask. So fear the sideways move less.

One more, learned slowly: saying "I do not know, but I will find out by tomorrow" out loud is an accelerator, not a weakness. The people worth working with trust you more after hearing it, not less.

And seconding your health point. The body keeps better logs than we do, and it never loses them.

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you for sharing this, Vinicius.

I liked what you said about the years that feel like a detour. I think it's so easy early in a career to look at what everyone else is doing and wonder if you're falling behind, when in reality those different experiences might end up becoming the thing that makes your perspective unique later on.

I also loved your point about saying, "I don't know, but I'll find out by tomorrow." I think a lot of us worry that admitting we don't know something will make us look less capable, when it probably does the opposite if we follow through.

Can I ask one question? Looking back now, was there a moment when you realized that your experience in statistical risk modeling had actually become one of your biggest strengths, or was it something you only appreciated gradually over time?

Thank you again for sharing your experience 😀

Collapse
 
vinimabreu profile image
Vinicius Pereira

Gradual for years, with one sharp click at the end. For most of my career I treated it as the boring part of my resume. The click came with the LLM wave: I kept sitting in rooms where a demo was celebrated and shipped without anyone asking the questions my credit-risk years had burned into me. How often is it wrong, what does a wrong answer cost, and who pays for that cost. In credit modeling those questions are the entire job, because a miscalibrated model approves bad loans and the loss lands on a ledger with your name near it.

The moment was noticing that my discomfort in those rooms was not anxiety, it was training. Everyone was asking if the model could do the task. Almost nobody was asking what happens when it does the task wrong. I had spent years on the second question before the first one got exciting.

So: gradual, but you only recognize a foundation when the ground shakes. The hype cycle was the shake. And thank you for the question, it made me put into words something I had only felt.

Thread Thread
 
hemapriya_kanagala profile image
Hemapriya Kanagala

I really like the way you put that: "You only recognize a foundation when the ground shakes." That's such a good way of describing it.

I also found it interesting how you said your discomfort wasn't anxiety, it was training. I don't think I would've looked at it that way, but it makes a lot of sense. Those years gave you a way of thinking that became valuable when everyone else was focused on a different question.

And thank you for taking the time to answer mine too. I learned a lot from this conversation 😀

Thread Thread
 
vinimabreu profile image
Vinicius Pereira

Likewise, Hemapriya, this was a good conversation. Keep asking questions that make people put into words what they had only felt. It is a rare skill, and this thread is proof it works.