Feeling stuck isn't a sign to push harder

It's a sign that you have outgrown your environment

We've all felt stuck at some point in our lives

And you will feel stuck at some point in your career

It's normal

My favorite analogy for growth is the lobster analogy.

> Lobster grows

> Shell becomes to small

> Lobster sheds its shell

> Finds a new shell

In our case, it isn't so obvious:

• Your friends
• Where you live
• Your current job

These things are your "shell"

As you go through life you inevitably change. You find new values, pursue new goals, and crave different things.

Through that process it is likely you will get uncomfortable at some point

• The country/town you live in doesn't share your values
• The current job you have doesn't offer a path to your goals
• The friends you have are asking your to compromise your values

These things are painful to shed.

So we avoid them.

Luckily friends are possible to grow with. You can exchange values, share goals, and chase new dreams together. People are the rare exception of something that can work for your lifetime because they can change too.

Just make sure you're aligned from time to time.

But the other things? Those are harder to change.

It usually isn't worth the massive effort to try to individually:

• Change the values of your country
• Convince your employer to create the opportunity you want

In these cases:

It is time to shed your shell

Recently, I've gotten a lot of calls from developers who feel stuck.

So this newsletter is for them.

Even if you aren't stuck right now, you will be at some point in the future.

This is still worth reading.

So far in my career, I've been stuck 4 times.

In my experience:

There are two options

Change Jobs

Find a new Environment

This is the most obvious one.

Your current shell doesn't fit anymore? (current job)

Go find another shell. (new job)

This approach is good early in your career.

When you get your first job you have no idea what to expect. You will get projects you feel "not ready" for and be forced to learn new skills that you never heard of.

It's an exciting time of skill growth.

There is so much to learn.

But eventually, things can start to feel stale.

The same old tasks...

The same old service you know too well..

The same office politics getting in your way...

The same promises that things will change (and they never do)...

Odds are by the end of this first job you will have a better idea of what you do and don't like.

Maybe you need a fresh tech stack?

Maybe you learned you like front-end a lot?

Maybe you found a new interest in embedded engineering?

Maybe you learned that a life of coding in general isn't for you?

I can't answer that question for you.

Find that new opportunity that gives you room to grow in the ways you want.

The new job might offer:

• A cutting edge tech stack
• A front-end focused position
• Opportunities to do embedded engineering
• Opportunities in tech that don't involve coding

If you say yes to an opportunity:

Make sure it's a hell yes

You should feel excited about the opportunity to grow in new ways.

Like I said, this approach is great early in your career.

It can take time, but you only need one "yes"

And off you go to grow in new ways

Later in your career you can feel like you have grown in all the ways that normal job positions allow. Your skills are at a point where it feels like your only options for "growth" are taking on a manager role.

And that might not be for you.

Every step "forward" feels like a sideways-step, and the prospect of changing jobs might not serve you anymore.

Candidly, this is where I am at, and why this newsletter exists in the first place.

Which takes us to option 2

Start a Project

Create Your Environment

This one is less obvious, and a scarier than the first one in many ways.

It comes with a massive degree of uncertainty.

However, when you are at the point where your skills feel pushed to their limits within your current environment, this can be an amazing option.

I'm using the term "start a project" loosely here.

It could many any of these:

• Start a SaaS Company
• Teach other people how to code
• A YouTube channel featuring fun coding projects
• A completely different career that matches your new values

Many people feel like these types of steps aren't allowed.

There is a lot of pressure to be grateful for what you have and express your gratitude by grinding it out in your current position.

That is nonsense.

I've met too many burned out engineers to think that is the best option.

For the newbies reading this: I don't want to scare you away...

There is a massive benefit on the other side of traditional employment...

• Potent 21st century skills
• A bigger savings account
• Opportunities to meet skilled people
• Personal growth opportunities throughout

But at some point... You might feel stuck... And not know where to go...

And that is fine.

When you're climbing the corporate ladder you will feel like you cant let go. Even though you have become so skilled that you now have wings.

Just because the journey ends doesn't mean it wasn't worth it.

When the predefined journey doesn't serve you anymore.

It might be time to start your own.

It's scary at first, but I promise it's exciting.

___________________________________________

Thank you all for reading this week's newsletter.

I appreciate all of you who read to the end.

Email me at swdlodonnell@gmail.com with any questions

To anybody feeling lost on where to start. I'm extending an invitation to check out my first course ever The Coding Career Blueprint. The course is exclusively 60% off for my newsletter subscribers with the code: bokbsj3

Until next week!

I hope you all have a great weekend.