A short series on what two layoffs taught me, so you don’t have to learn it the hard way.

It was my day off back in 2024. I opened my work laptop to check in, but I couldn’t. A message stared back at me: Your computer has been locked.

I checked a Discord group chat with my coworkers. Several people said they’d been laid off. Apparently there was a meeting that morning, and I missed it.

Did I just get laid off on my day off?

I checked my laptop again. Still locked.

A few hours later, HR called to tell me what I had already figured out. I never heard from my manager that day.

Stories like this have become normal since 2020. People get laid off on vacation, on parental leave, even sick in the hospital. Companies can’t control where you are when the news drops. But they can control how they deliver it. When they show no compassion, you feel like a row on a spreadsheet. And that stings.

A layoff is a business decision

When you get laid off, it’s easy to take it personally. You think about the projects you shipped, the late nights, and the sacrifices you made to give your job your best.

But a layoff is a business decision. Period. A few people at the top decide to move a number from one column to another. It doesn’t matter how many kids you have, whether you’re up for promotion, or whether you’re living paycheck to paycheck. They just decided your salary was a cost they could cut.

That sounds harsh, and it is. But it’s also good news. Remember that row on a spreadsheet? That’s exactly why it isn’t about you. The decision has nothing to do with the value you brought or your worth as a person.

It still sucks. And finding your next job might be hard. But don’t let a layoff erase the career you’ve built or what you still have to offer. You are more than your job title.

Company loyalty is dead

A few generations ago, work looked a lot different. You worked hard for 30 years and stayed loyal to the company. In return, you got job security and retired with a pension.

That deal is gone. Layoffs hit every industry and every type of employee. Your salary, your years at the company, your last performance review. None of it protects you.

When I posted about my two layoffs on LinkedIn, this came up in the comments again and again: you can’t trust the company. Loyalty only goes one way now. Companies do what’s best for them, not you.

It took me two layoffs to finally get this. But once I did, it changed how I showed up at work and at home. I stopped letting work creep into my evenings and weekends with my family. And I started a side business, so I’m not relying on one paycheck.

What you should (and shouldn’t) say after a layoff

Repeat after me: I don’t owe my former company anything after a layoff.

That includes a gratitude post. I know a lot of people feel pressure to write one. They don’t want to look bitter to recruiters and hiring managers. Or they worry that saying something negative could put their severance at risk. But posts that do nothing but praise the company come off as fake. And a little cringey.

Want to thank your old coworkers? Great. Do it privately. A direct message means more than a tag in a post anyway.

So what should you say? Be honest with yourself and your network. Acknowledge what happened, then focus on you. Share what you accomplished and how you grew. Say what you’re looking for in your next role.

Honest doesn’t mean trashing the company, though. Skip the blame, the names, and the inside details. Talk about how you feel and what’s next. That’s the post that helps you land your next job.

Both times I got laid off, I barely mentioned the company in my LinkedIn post announcing it. I was upset, confused, and worried. But I focused on me and what I wanted next, not on thanking the company for letting me go.

My first layoff didn’t change me. My second one did. Sometimes you have to learn a lesson twice before it sticks.

A layoff is a business decision. Company loyalty is dead. And you don’t owe your old company anything.

I also learned that no job is safe enough to bet everything on.

Next time, I’ll share why I stopped relying on one paycheck.

A short series on how I’m navigating the messy middle, and how you can too.

Last time, I admitted that I don’t have it all figured out. I’m in the messy middle with my career and my side business.

The old me would have been embarrassed to say that. The questions, the doubt, and the discomfort would have kept me frozen and quiet.

But I’ve started to see this phase differently. When I look past the hard feelings, I see a chance to grow and change.

Here are four steps I’ve been taking in the messy middle. They’ve helped me feel more grateful for where I am and more excited for what’s ahead.

Accept where you are

A few months ago, after a long week at work and at home, I asked myself, “Is this really what I want?” I didn’t have an answer. That’s when I knew I was in the messy middle.

I didn’t try to fix it right away. That would have just added more stress. I sat with the feeling for a while. Then, slowly, I started to take action.

That’s the first step. Whatever you’re feeling, admit it. Stuck. More questions than answers. Not sure what’s next. Say it out loud, even just to yourself. It’s a relief when you stop hiding from it.

The truth is, most people are here most of the time. Beginnings and endings are short. The middle is where we spend most of our lives. So you’re not behind. You’re just figuring out what comes next.

Once you drop that weight, the middle stops feeling like a bad place to be. It’s where you learn who you are and what you can do. And it’s where the growth happens.

Talk to the right people

When you’re stuck, it’s easy to feel like nobody gets it. But you’re not as alone as you think.

When I felt stuck, I wanted to talk about it. I didn’t need someone to tell me what to do. I just needed someone to listen. So I turned to a few close friends. They showed me empathy and compassion, and gave me the confidence to keep going.

Friends are a great place to start. So are former coworkers, people in your network, or a therapist. The right people listen without judging you or jumping in with advice. They don’t need to be experts or know what you should do. They just give you a safe space to be seen and heard. And they share what they notice.

I’d avoid anyone with skin in the game, like a partner or a manager. They may want to help. But it's hard for them not to tell you what they think you should do. Right now, you need less outside noise so you can hear your own voice.

Do the research

If you keep coming back to the same questions, it’s time to dig in. Your gut is pointing you somewhere. Research is how you find out if it’s right.

I wanted to know what engineering leadership was really like. So I talked with people who had made the jump from engineer to manager. I asked a lot of questions. I listened. Then I took time to process what I learned.

The biggest lesson? Being a manager isn’t a promotion from senior engineer. It’s a whole new career path, with a different set of skills.

You can do the same with whatever’s on your mind:

• Will I enjoy working in this industry? Learn what those companies are building.

• What’s it like at a startup vs. a big company? Ask someone who’s worked at both.

• How much work is a weekly newsletter? Ask a writer.

Let your curiosity lead. The answers won’t all come at once. But each thing you learn makes the picture a little clearer.

Run tiny experiments

You followed your gut and did the research. Now it’s time to act. You don’t need to know where it leads. You just need one small, low-risk way to test what you’re curious about.

To see if I’d like coaching, I offered a few free sessions. People reached out. I got real practice listening and asking the questions they needed to answer. And I walked away feeling energized, like I made a difference. That told me more than months of thinking about it ever could.

Here are a few more ideas:

• Want to share what you’re learning? Write one article on LinkedIn or Substack.

• Curious about management? Offer to mentor a junior engineer.

• Want to build an app? Make a short list of problems you’d like to solve.

If it feels too easy, good. It’s supposed to be small. You’re testing the water, not jumping in.

Accept where you are. Talk to the right people. Do the research. Run tiny experiments.

None of this will fix everything overnight. I still don’t have a full answer to “Is this really what I want?” But I’m closer than I was. And I didn’t need a big plan to get here. I just needed to start.

What’s one tiny experiment you could run this week? Tell me in the comments.

If you’re in the messy middle and want someone to talk it through with, I’d love to help. Book an intro chat and we’ll figure out your next step together.

A short series on how I’m navigating the messy middle, and how you can too.

Scroll LinkedIn for five minutes, and you’ll see two kinds of posts. Starts and finishes.

“I just started a new job!”

”I got promoted!”

”I’m starting a business!”

We love to share the start or end of a chapter. It feels natural, and people love to cheer for it. But most days, we‘re not at the beginning or the end of anything.

We’re in the messy middle.

It‘s the awkward, uncomfortable stretch that lasts way longer than we want. We have more questions than answers. Impostor syndrome shows up. We‘re not sure where we‘re going.

Maybe that’s why so few people post about it. It takes courage to admit you don‘t have it all figured out. Even fewer will admit they made a mistake or are going through a hard time.

But the messy middle isn't something to hide or feel ashamed of. It‘s where most of your life happens. And even with all the discomfort, it‘s where you grow the most.

My career

In many ways, I’m in the messy middle of my tech career. You’d think after 20 years in the industry, I’d have it figured out. But I have more questions now than ever.

• Do I want to be an individual contributor or a manager?

• Which path is more stable?

• What do I really want to do vs. what others think I should do?

• What kind of company do I actually want to work for?

• Will software engineering even look the same in five years?

• Do I still want to work in tech if it changes that much?

Earlier in my career, I never thought to ask these questions. Now I’m glad I do. I’m curious about them, and I’m sitting with them. I’m not rushing to answer them.

My questions about jobs have changed too. I used to ask, “Are the pay and people good?” and “Can I get hired here?” Now I ask, “Do the company’s values match mine?” and “Does the pace of the company fit my life?” These questions are harder to answer. That doesn’t make them less important.

Then there’s AI.

AI is changing how engineering teams work, fast. The job looks very different than it did five years ago. It’ll look even more different five years from now.

Tools like Copilot and Claude Code took away my favorite part of engineering: writing semantic, modular, and scalable code. I used to love writing CSS animations from scratch and building custom React hooks. Now I spend most of my time chatting with an agent. Finishing a feature doesn’t feel the same anymore. AI helps teams ship faster, but for a lot of engineers, it also takes away the part they enjoy most.

Tech has always moved fast. I’m used to learning new tools all the time. But AI has sped things up so much that keeping up feels impossible.

The good news is that what I love about the job has shifted. For the past six years, I’ve focused on leadership. Leading meetings, improving team processes, and mentoring other engineers are what I enjoy most now. As AI takes on more of the coding, people skills will matter even more.

I think those skills will help me in this new age of tech. But the question is still there.

Do I still want to work in tech if it changes that much?

My side business

I’m also in the messy middle with my side business.

I started it two and a half years ago. I’ve made a couple hundred dollars. And I still don’t really know what my business is. Not exactly the kind of thing people post on LinkedIn.

But I wouldn’t say I’ve failed. I’ve run a lot of experiments. I’ve built six apps and created half a dozen digital products. I’ve published more than fifty newsletter articles and hundreds of LinkedIn posts. I’ve hosted livestreams and had more coffee chats than I can count. And now, I’ve started coaching.

Even with all that, some days it feels like my business isn’t growing. I’ve tried a lot, but I haven’t picked a direction yet. It would be so much easier if I had a clear plan.

Right now, I don’t. And that’s the honest truth.

If any of this sounds familiar, you’re not alone. And you’re not doing it wrong.

The messy middle is full of discomfort, confusion, and growing pains. It feels messy because it is messy. And that’s okay.

Here’s what I keep reminding myself. Having more questions doesn’t mean you’re lost. It means you’re paying attention. You’re outgrowing your old answers and figuring out what you actually want.

That part is uncomfortable. It’s also where you grow.

Next time, I’ll share four things I’m doing to move through the messy middle, and how you can try them too.

What’s one question you’re sitting with right now, in your career or a side project? Share it in the comments. I read every one.

A short series on how I fit a demanding job, side projects, and staying healthy into the same week. This is what has worked for me over the years.

It took me nine months to build my first app. It was a simple Slack app where managers and their reports could build meeting agendas together. I had to learn some new tech, but nothing too hard.

It stalled out many times. I always blamed it on life getting too busy. That wasn’t the real reason.

The real reason was that I had no clear plan. Every time I sat down to work on it, I had to figure out where I left off and what to do next.

Time wasn’t the problem. Not knowing my next step was.

Fast forward to 2026. My sixth app, CareerCred, took three weeks.

The difference was a plan. Before I wrote any code, I used Claude to produce two docs: a project spec and a dev plan. I wrote more about that process in this post.

The spec covered the tech stack, V1 features, pricing, and beta phase. It was my source of truth for every decision Claude Code and I made.

Then I had Claude turn the spec into a dev plan. Phases, tasks, and subtasks. Each task had to take 30 minutes or less, from code generation to my code review.

So when I sat down to work, I never had to ask, “What’s next?” I just picked up the next task.

If your side project isn’t technical, make a spec and a plan anyway. Writing a book or building a digital product works the same way. You always know what you’re building toward.

You don’t need hours of free time to finish a side project.

I built CareerCred in a few 30-minute blocks during the week and a few 1-hour blocks on the weekend. That was it.

This works because of the plan. A small block is enough when you know the next task. Finish one, and take the win. That’s what makes it easier to come back tomorrow.

One more tip. Find test users early.

When you work alone, you get tunnel vision. Apps have beta testers and books have editors for a reason.

Before launch, give a small group access. Ask what confused them and what they’d change. Their answers will show you what to fix and what to stop building.

A few honest opinions now can save you weeks of work on the wrong thing.

That first app took me nine months. It didn't have to.

I had the time. I didn't have a plan.

That’s the whole series. Movement gives you the energy. Scheduling gives you the room. A plan gives you the direction. You need all three.

If you're stuck right now, start small. Write down the next task, then do it.

What’s the side project you keep meaning to get back to? Just naming it might be the spark you need.

Read Parts 1 and 2:

Stuck on something right now?

I’m offering 2 free coaching sessions next week.

This is for you if:

• Work is draining you and there’s nothing left for the rest of your life

• You can’t find time for your side project, or you’re struggling to make progress on it

• It’s hard to make your mental and physical health a priority

Bring something specific and we’ll work on it together.

Book a session

A short series on how I fit a demanding job, side projects, and staying healthy into the same week. This is what has worked for me over the years.

I used to block off afternoons on my calendar for writing code.

But when the time came, I’d hit the post-lunch slump. No energy. No brain power to code.

At first I felt guilty about it. Eventually I realized my body was trying to tell me something.

Time blocking alone doesn’t work. You don’t have the same energy and focus every hour of the workday.

When I looked closer at my calendar, I saw the problem. I was adding focus blocks around my meetings, not around when I actually do my best work.

So I ran some experiments. One week, heads-down work in the morning. The next week, I flipped it to the afternoon.

You can do the same. Look back at your last few weeks. When did your best work actually happen? That’s your window.

Once you know your windows, play matchmaker. Match the task to the time block, based on your energy, not just what’s open on your calendar.

If you write your best code in the morning, protect it. Push meetings, code reviews, and messages to the afternoon.

Only you know your ideal schedule. And this isn’t just about getting more done from 9 to 5. It’s about having energy left for the people and things that matter from 5 to 9.

Bookend your workday with some time alone, no meetings or messages.

Start the day by sorting your tasks. What must get done, what would be nice to do, and what can wait until tomorrow.

End the day with a few minutes of reflection. Did you finish what you wanted? How are you feeling? What’s tomorrow’s first task?

This closes the loop on your day. You stop carrying today’s work into tonight.

Your job is one part of your life, not all of it. When you give it all your energy, there’s nothing left for what actually matters.

That’s why it’s worth being smart about where your time and energy go at work. Get this right, and you get more done at work and still have energy for the rest of your life.

What’s your best hour of the day, and what are you currently spending it on?

Next week: the real reason side projects stall (it isn’t time).

Missed part 1?

Stuck on something right now?

I’m offering 2 free coaching sessions next week.

This is for you if:

• Work is draining you and there’s nothing left for the rest of your life

• You can’t find time for your side project, or you’re struggling to make progress on it

• It’s hard to make your mental and physical health a priority

Bring something specific and we’ll work on it together.

Book a session

A short series on how I fit a demanding job, side projects, and staying healthy into the same week. This is what has worked for me over the years.

I used to treat exercise as a reward. I’ll go to the gym after I get my work done, I’d say. Let me finish this task before I take a walk. The work never stopped, which meant the reward never came.

Last year I burned out. I was trying to do too much. I wasn’t moving, sleeping, or eating well. I didn’t even want to get out of bed. That’s when I realized that exercise shouldn’t get whatever’s left. It creates the energy I need to do everything else.

Exercise is my non-negotiable. When I was recovering from burnout, it went from optional to mandatory. Today it’s the one thing I do almost every day. Most days that means a walk around my neighborhood. Some days it means weight training in my small home gym.

Exercise gets me off screens and gives my brain a break from solving problems all day. It clears my head and resets my mood. When I move my body regularly, I’m more focused at my day job, more present with my family, and more productive on side projects.

Three rules keep me consistent.

• I exercise after work, before anything else in the evening. It also creates a clear boundary between work and life.

• On hard days, I set the bar low. Usually a 15-minute walk.

• If I miss a day, I don’t make a big deal of it. I get back to it the next day.

Two other habits matter almost as much. I aim for at least 7 hours of sleep every night. Anything less and I struggle the next day. I also try to take a few moments during the day for meditation and reflection.

Exercise used to get my leftover energy. And that's one of the reasons I burned out. Now I've learned that it fuels everything I do in life. What do you keep pushing off?

Next week: why some hours are worth more than others.

Stuck on something right now?

I’m offering 2 free coaching sessions next week.

This is for you if:

• Work is draining you and there’s nothing left for the rest of your life

• You can’t find time for your side project, or you’re struggling to make progress on it

• It’s hard to make your mental and physical health a priority

Bring something specific and we’ll work on it together.

Book a session

My first SaaS app took nine months to build. CareerCred took three weeks.

The difference? I used Claude Code for almost everything.

I’m not a beginner. I’ve built six apps. I have a full-time job, a family, and limited free time. So when I found a tool that let me ship faster without losing control of the code, I went all in.

Here’s exactly how I did it.

Start with docs, not code

Before I wrote a single line of code, I created two docs: a project spec and a dev plan.

I didn’t realize it at the time, but these two docs are the reason I shipped so fast.

Project spec

I spent 3–4 hours working with Claude Chat to build out the spec. At first it felt like a waste of time. In hindsight, it was the best investment I made on this project.

The spec covered everything: tech stack, authentication, V1 features, pricing, beta phase, API routes, and more. It wasn’t just a technical doc. It was a source of truth for every decision I made along the way.

Things like the cron schedule for reminder emails, the early adopter price, and the environment variables I'd need in production. All of it lived in the spec. No guessing. No context switching.

Claude Code doesn’t need all of this upfront. But giving it more context meant better output. Every time.

Dev plan

Once the spec was done, I used it to generate a dev plan. The goal was simple: break the project into phases, tasks, and subtasks. Small and specific.

I wanted to review every PR myself, so I told Claude to keep tasks small. Small enough that most could be done in under 30 minutes, start to finish. That included Claude writing the code and me reviewing and testing it locally.

Here’s what that looked like in practice:

- [ ]  Onboarding form — collect name, job title, timezone (auto-detect)
- [ ]  Wins feed (/dashboard/wins) — full card list, newest first; incomplete wins visually distinguished

Small tasks create momentum. When you can check something off, you want to keep going. That’s what kept me coming back to this project instead of abandoning it like so many others.

Building in 30-minute windows

I have a full-time job, a family, and other interests. My free time comes in 30-60 minute windows. The dev plan was built around that reality.

A typical day

1. Open Claude Code, ask what’s next on the dev plan, and either run with it or adjust based on my schedule.

2. For tasks I’m unsure about, use plan mode to see what Claude is thinking. Otherwise, ask Claude how it wants to approach something and accept the edits.

3. For trivial commits, push straight to main. For most tasks, have Claude create a feature branch, update the dev plan, commit the changes, and open a PR with a test plan.

4. When I have time again, review the PR on GitHub and run through the test plan.

5. Tell Claude to merge the PR.

Why this worked for me

I didn’t want to “vibe code” this project. I’m a software engineer. I know how to code. So I made a point to understand what was being built.

That’s why I used PRs for almost everything. It gave me a checkpoint to review the code, run the tests, and stay in control.

Claude wrote most of the code. But I made suggestions, changed course when needed, and understood every decision. The result is an app I own and actually understand.

Building a SaaS app on the side in 2026 has never been easier. Tools like Claude Code have changed the game.

But here’s what six apps have taught me: building is the easy part. Getting it in front of users, finding beta testers, marketing it… that’s where most side projects stall.

The faster you ship, the faster you get to the hard part. And the hard part is what actually matters.

If you have an idea and limited time, give Claude Code a shot. It handles the easy part so you can get to the hard part faster.

What are you building, or what have you been putting off starting?

CareerCred helps engineers track their wins and tell their career story. Join the waitlist for early access: https://careercred.io

So, in the spirit of the season, I’d like to give you a gift.

These are the biggest lessons I learned in 2025.

Besides Code was founded on sharing knowledge and helping you grow. This small present might be exactly what you need right now.

Your health comes first

Nothing matters more than your health. Not your job. Not your family. Not anything else.

I learned this the hard way this year.

By the end of the summer, I had said “yes” so many times that I had no energy left. No desire, either. I was officially burned out — and I had no one to blame but myself.

I thought I understood burnout. I’d been exhausted and overworked before. But this time was different.

It touched every part of my life.

I didn’t want to do even the most basic things — like getting out of bed or eating.

I didn’t want to work on my side projects.
I didn’t want to create content.
And I didn’t want to do my day job.

“What’s the point of working on my side projects? I’m just going to fail again,” I thought.

“Why bother posting on LinkedIn or writing on Substack? I’m a fraud.”

“I’m useless at work. I’m not providing any value.”

The worst part? My relationships suffered too.

I wasn’t myself. I became needy, anxious, constantly overthinking, and catastrophizing everything.

Once I realized I was dealing with burnout, I made a simple two-step recovery plan:

• Stop every non-essential activity

• Find joy again without screens or people

I canceled meetings.
I stopped posting.
I paused coding on the side.

I was doing too much. And I had to stop everything I’d said yes to.

I knew I couldn’t do it all. And even if I could, would I want to? Multitasking never works.

I filled that new space with things that genuinely made me happy.

I journaled.
I took daily walks.
I read a lot.
I prioritized sleep.

Many of these things are free — yet they’re priceless.

They fill my cup. They make me feel alive. And they give me the energy to create, build, and help others.

I’ve slowly started saying “yes” again. But this time, it’s on my terms and within my boundaries.

Your physical and mental health must always come first.

Because how can you do great things in this life if your body and mind aren’t well?

Showing up matters more than streaks

One of my goals this year was to post daily on LinkedIn and Substack.

The streak lasted six months — and then it ended.

Did I fail because I didn’t hit my goal?
Absolutely not.

I showed up consistently. And that matters more than any streak.

As creators and builders, we love to glamorize numbers.

“How many likes did your last post get?”
“How many apps did you build this year?”
“How many days in a row did you commit code?”

But numbers don’t tell the full story.
And there’s more to life than metrics.

Instead of counting followers or calculating engagement rates, try asking yourself this:

Am I learning?
Am I growing?
Am I having fun?
Am I making an impact?

Streaks can help you start a habit.
But they aren’t meant to last forever.

Just show up.

That’s enough.

Communication isn’t optional

Wouldn’t it be great if your manager were a mind reader?
What about your coworker? Your partner? Your kids?

You’d never have to explain yourself.
You’d always know how they felt and what they were thinking.

Of course, that’s not how life works.

So we have to communicate.
It’s required. It’s not optional.

The truth is simple. No one knows what’s going on in your head unless you tell them. I was reminded of this again and again throughout the year.

I messaged colleagues when I needed help.
I invited friends to join me on livestreams.
And I asked you to consider purchasing my digital products.

None of that would have happened without communication.

I had to say what I wanted. We all do.

Yes, it can feel uncomfortable. Even embarrassing, especially when asking for help. But the discomfort is temporary. The outcome can be better than we ever imagined.

Communication is essential to life.

It can be the difference between feeling stuck and miserable and finding fulfillment and purpose.

If you don’t ask, you don’t get.

I love this expression. It reminds us of the power of communication and gives us hope for what could be.

Growth requires change

We’re surrounded by change. In nature. At work. At home. Even in our own bodies.

And yet, we struggle to accept it. Sometimes we even resist it.

One of the biggest lessons I learned this year is simple: growth requires change. And it’s hard to change when you’re comfortable.

When you’re comfortable, you want to stay that way. Change threatens that comfort. It also brings uncertainty.

At work, there were roadmap shifts and project pivots.
My relationships with friends and family changed.
Even my interests and beliefs are different now than they were a year ago.

Some of these changes were scary at first.

But over time, they became less scary.

And once I realized those changes were helping me learn and grow, I stopped fighting them. I welcomed them.

The next time you face a big change in your life, try to look on the bright side.

Growth is ahead.

You’ve stepped outside your comfort zone before.
And you can do it again.

I’m grateful for this year, even though it didn’t go as planned.

I pushed myself outside my comfort zone.
I chose my health.
I showed up when I could.
And I leaned into change.

Life is a constant cycle of growth and change. The lessons we learn along the way are what make that growth possible.

Here’s to another year of lessons.

What did this year force you to learn?

Let’s keep learning and growing together.

I’m delighted to share this guest post from my friend, . We went live together on LinkedIn earlier this year to chat about avoiding common engineering pitfalls. We also talked about his brilliant book, Keep Calm And Code On. I’m so glad he wrote this guest post about a popular pitfall — development by hope.

I’ve developed by hope countless times in my career. We’ve all been there. You write some code, ship it, and pray it works. While this might work sometimes, it’s not a good habit to form, nor does it make you a good teammate. There will be times when you need to dive deep into something to learn it or fix it. And as painful as that might be, it’s worth it. Read on to learn more about development by hope and how to avoid it.

Over to you, Alex.

A few years back, I was in charge of fixing a bug that was causing one of the main pages in our application to crash. My approach could only be described as frantic. The code itself was in a part of the codebase I wasn’t too familiar with, and I had a proposed change that I consulted with a colleague on.

Since this was impacting customers, I was in a rush to push the deploy button as fast as possible. When my coworker who knew the code better suggested that I write a test to verify my change, I exclaimed, “It’s a hotfix, I don’t have time for tests!”

He paused for a second, then solemnly replied, “Those are the times you need tests the most.” His response took me by surprise, and his words still echo in my head years later whenever I’m addressing a hotfix.

I’ve since come to refer to this style of approaching a problem as “Development by Hope.”

Development by Hope occurs when you throw out a solution that you’re not particularly confident in and instead rely on having enough luck on your side to make it over the finish line. It’s taking the phrase “I’d rather be lucky than good” and quite literally applying it to software.

I’ve seen it time after time, and I myself have done it more times than I’d care to admit.

Hard-to-Reproduce Bugs

The underlying cause for Development by Hope is hard-to-reproduce issues. In my experience, these issues come in 2 flavors:

1. A race condition makes the issue appear intermittently.

   • For example, a webpage’s visual bug that only appears intermittently upon browser refreshes.

2. An interaction occurs in a hard-to-access area of the codebase.

   • For example, a bug that happens on the last step of a 10-step modal wizard. Both the data needed to set up that flow as well as clicking through could be painful to set up.

If you’re unlucky, a problem will fall into both categories at once. Those are the times that are most trying even for seasoned developers.

The problem with relying solely on hope is the same problem with tech debt in general: you’ll likely be able to do this for a while, but once that debt reaches a tipping point, there are all kinds of problems in the system. Not to mention that in the case of hotfixes in particular, I’ve found that haste often begets the need for another one right after.

Annoyance as a Code Smell

Before succumbing to how hard a problem is, I’ve found that flipping the script and asking myself “What can I do to be confident in a fix?” to be an incredibly effective technique. In my opinion, this is one of the most effective ways to jump right to the underlying pain point.

Let’s re-examine the examples of hard-to-reproduce issues from before and look at possible ways to deduce their underlying pain:

A webpage’s visual bug that only appears intermittently upon browser refreshes.

When seemingly random behavior arises, the only real way to be confident in fixing it is through understanding the lifecycle of an action. Being able to effectively debug and utilize observability tools are skills that are indispensable for this sort of task. If you can’t explain it, you can’t be sure you’ve solved it.

A bug that happens on the last step of a 10-step modal wizard.

This sort of issue is a real test of a feature’s architecture. Confidence here means being able to run this 10th step with a variety of input along the way. You’ll need the aid of short feedback loops which may also require mocking out data and other development environment niceties.

In either case, the initial feeling I’ve had when encountering both of these types of problems is annoyance. Annoyance that, for one reason or another, I’m not able to have my cake and eat it too when it comes to shipping high-quality code quickly.

But now I recognize that annoyance is a code smell that points to a chance to make things better in your system. Maybe it’s adding tools to increase observability, or maybe it’s expanding a test suite. Sometimes it’s as simple as taking the extra 5 minutes to write a test when you’re in the fervor of a hotfix.

Development by Hope doesn’t build robust systems. Confidence does. Chase the pain, fix the system, and leave the luck to the lottery.

Thanks to for writing about this common engineering pitfall. Please read his book and follow him on LinkedIn.

Don’t judge a book by its cover.

We’ve all heard that phrase, but we still do it.

Especially when it comes to jobs and interviews. We try to map out the next few years of our career after just a couple of hours in interviews.

I’m guilty of this. And I’ve been totally wrong sometimes.

It’s unsettling when you realize you judged too soon. You might even panic and wish you could hit rewind. I hate to break it to you, but that button doesn’t exist. The good news? There might still be time to change course.

In this post, I’ll share some common situations where a job or company turns out differently than expected. It happens all the time. And knowing how to respond can help you turn things around — and find your way forward.

The code

Companies are protective of their code. If you're lucky, you’ll hear about the tech stack in interviews or maybe see a quick demo. But that’s usually it.

They’ll highlight the fancy tools and gloss over the tech debt. And honestly, we do the same thing in interviews — we talk up our strengths, not our weaknesses.

I’ve seen all kinds of codebases. I’ve been told “our codebase is easy to learn,” only to still be lost months in. I’ve also heard “our code is complex,” and it turned out to be a glorified Next.js app.

I’ve even been flat-out lied to: “We don’t have much tech debt,” or “You won’t have to fix bugs.” So take what you hear in interviews — and even your first few weeks — with a grain of salt. The truth will surface. It just might take some time, and that’s okay.

After working through a few tickets, you might realize things aren’t what you expected.

There’s more legacy code.

The architecture is messy.

You’re seeing tools you’ve never used before.

It can be frustrating, but don’t accept defeat. You can get up to speed. Here’s how.

Zoom out before you zoom in

Before diving in, take a step back.

• What’s the tech stack?

• Which core packages are used?

• How is data fetched?

• How is code tested?

• What’s the build pipeline?

Once you have the lay of the land, you’ll feel more confident about where to start.

Create a learning plan

Did anything feel unfamiliar when you zoomed out? New tools? Old ones you haven’t touched in years?

Make a list of what you need to learn or relearn. Break big topics — like new languages or frameworks — into smaller chunks.

Turn your list into a learning plan. Block time on your calendar to work through it. You’ll build knowledge piece by piece.

Start coding

Reading code is helpful, but writing it is better. So spin up a scratch branch and start experimenting.

Add code. Change things. Delete stuff.

See what breaks. Pay attention to what changes.

When something doesn’t make sense, write it down. You can revisit docs or ask a teammate later.

Once you’re comfortable with a part of the codebase, pick up real tickets related to it:

• Know how testing works? Add a test to an existing function.

• Understand the component library? Build a new component from a recent design.

• Feel good about the data schema? Take on a task that updates it.

You’ll have questions — and that’s fine.

What matters is that you’re making progress. Bit by bit, you’ll get there.

The culture

Company culture is hard to gauge from a couple of interviews.

You might meet some friendly folks — but does that mean everyone is like that?

A hiring manager might preach work-life balance, but is it actually practiced?

Here are a few things I’ve experienced:

• I’ve met great people in interviews, only to later discover some not-so-great ones on the team.

• I’ve been promised a culture that values work-life boundaries, then found myself logging off alone at 5 p.m. while others messaged me at night.

• I’ve heard “we’re like family,” then watched the company lay off half the team.

Culture can be tricky. But you’re not powerless. Here’s how to stand tall — no matter what you walk into.

Establish your boundaries

Share what matters most with your team. That could be how you like to communicate, your work hours, or something about your identity.

Being upfront invites others to respect your space — and learn more about you.

Don’t want messages after hours? Say so.

Need a break from lunch meetings? Speak up.

You’re setting the tone. And you might just inspire your teammates to do the same.

Talk with leaders

Leaders are responsible for creating a healthy work environment. One that supports collaboration, growth, and performance.

If something — or someone — is getting in the way, tell them. Share your concerns early and often.

This helps build trust. And it shows you care about the team, not just yourself.

Get to know your team

It’s easy to form quick judgments. We’ve all done it.

But people can surprise you. Someone who seems quiet at first might open up over time. Others might come off strong in a group but be kind and thoughtful one-on-one.

Spend time with your team. Do 1:1s. Pair on work. Share wins.

Strong relationships take time — and effort. Support each other. Give honest feedback. Be human.

Your first impression might be right — or totally wrong.

You won’t know unless you stay curious and give people a chance.

Your career

You can’t get a full picture of your career path from interviews alone. It often takes weeks — or even months — to get a better sense of things. And even then, you might be left with more questions than answers.

The truth is, your ability to get promoted, earn a raise, or move into a new role is often shaped by factors outside your control — budgets, open roles, team size, and leadership opinions. But that doesn’t mean you’re stuck.

Here’s what I recommend if you want to keep growing at any company.

Be your own hype person

No one knows your growth better than you do. You know which challenges you’ve overcome, what problems you’ve solved, and what skills you’ve picked up.

So share that.

Give your manager regular updates about your progress. Sure, they might know some of what you’ve accomplished — but probably not all of it.

This could be a brag doc, a quick async message, or a one-on-one chat. However you do it, take pride in your growth. It’s your best evidence for what you want next.

Lead without the title

Sometimes you can’t step into your next role because of timing, budgets, or team structure. That’s frustrating, but don’t let it stop you.

Take ownership. Build trust with your teammates. Act like a leader now, even if your title doesn’t say so.

You don’t need to be a team lead to plan a project. You don’t need to be a manager to support your peers in 1:1s.

When you lead without the title, you:

• Show others what kind of leader you are

• Start practicing the skills you’ll need when you do get promoted

No one needs to give you permission. Start now.

You’ll be more than ready when the opportunity comes.

Own your future

Guess who cares most about your career? It’s not your manager. It’s not a senior leader.

It’s you.

If you’re waiting for promotions and raises to just happen — you might be waiting a long time.

No one owes you anything. So if you want something, own it.

Figure out what you want.

Make a plan.

Take action.

This also makes it easier to get support from your manager and teammates:

• Want to learn a new part of the codebase? Ask to pair with someone.

• Want to change teams? Talk to the team lead and share your interest.

• Want to move from IC to manager? Work with your manager on a transition plan.

And sometimes, owning your future means facing a tough truth — there might not be a path forward at your current company.

That’s okay.

Part of growth is knowing when it’s time to move on.

It might feel uncomfortable at first. But putting your future in your own hands is how you create real momentum — and real change.

When the truth unfolds

Companies and candidates pour time and energy into interviews. But the truth is you won’t really know if it’s a match until you start working together.

Both sides try to put their best foot forward. So it’s no surprise that flaws and red flags don’t show up right away.

The good news? You can let go of first impressions and embrace reality as it unfolds. That takes ownership of your role and your career, but that’s a good thing.

Next time you’re tempted to judge a company or role too quickly, pause.

The truth is usually somewhere between what’s visible and what isn’t. Give it time. Be patient.

I’d love to hear your stories:

What have you learned from a time when a job or company turned out very different than expected? Drop your thoughts in the comments. Your experience could help someone else navigate theirs.

I’m thrilled to share this guest post from my friend, . We went live together on LinkedIn to talk about creating videos. Sara has been a major inspiration to me when it comes to content creation, especially video content. She even helped me record my first few videos as a solopreneur. I highly recommend her services!

It’s easy to overthink video and put pressure on yourself to make it perfect. But as Sara reveals, you can get started with what you have today. And you don’t even need to talk on camera. Adding video to your online content can help you build a stronger connection with your audience. Read on to learn just how simple it is to create your first video.

Over to you, Sara.

When I posted my first video on LinkedIn, I had been overthinking it for months. I’d think to myself almost daily: “I need to get on video”. But the idea of actually hitting that ‘post’ button seemed too far-fetched.

I thought: Maybe one day, down the road. Maybe when my business gets bigger. Maybe when I stop caring what people think.

But with the launch of a new LinkedIn video feed format in 2024, I knew there was no better time to start posting my videos. I had to start before I felt “ready”.

And, now that I’ve done it (many times over), I can safely say it was one of the best decisions I’ve made for my personal brand and business.

So, how do you create your first video, too?

Let’s go over the basics and get you on camera.

What type of video should I create?

Most people automatically think “I’ll pull out my camera and just speak”. After all, we get on Zoom calls regularly. We see talking head videos in the feed. It looks easy enough!

So you pull out your camera. And immediately freeze up.

Almost everyone goes blank here.

This is why I always recommend people start by not speaking on camera at all. Instead, film some clips of you working, and let the text part of your post do the talking. It’s still you appearing on camera, but it’s lower effort and you can go through the motions of posting a video without the cringe factor.

By the time you do that a few times, you’ll be ready to speak on camera. And if not, that’s okay too. I help people all the time in getting past the overthinking that comes with this part.

What do I talk about?

A ton of people get tripped up here. Even if you’re an expert in your field, just know that it’s normal to not know how to translate that into bite-sized content.

Here’s a simple activity I do when I’m drawing a blank:

Start with the end result. It might seem overly simple, but what do you actually want the video to achieve? Are you looking to get more sign-ups on your newsletter? Get more clients? Get hired? Start with that, and work your way backwards.

I like to write down 3 big “buckets” or themes for my video content, that way all my video topics fall under one of those categories. This also helps you to never run out of ideas, because you can brainstorm and add topics to this list whenever your creative juices are flowing.

What equipment do I need?

I always say, “All you need is a phone and a face. And you have both!”

You don’t need any other equipment, but here are some pointers.

Lighting: Use natural light from a window in your office. I like to open the camera and hold it out, selfie-style, while walking to various windows to see which has the best lighting. And if you want to invest in equipment, a simple ring light will do wonders for a beginner.

Audio: If you’re going to purchase any new equipment, this would be where I’d recommend. Great audio is hard to achieve on our phones and laptops. They pick up background noise and sometimes sound low-quality, but it’s definitely not a deal-breaker as a beginner, so don’t sweat it too much. If you want to invest in equipment, there are some lapel mics for under $10 on Amazon that work really well!

Tripods & stands: You can easily prop your phone up against a stack of books, a lamp, a shelf, etc. But if you get tired of fumbling with it, there are several low-cost stands and tripods. I like to use a phone stand on my desk, so I’m hands-free.

What apps should I be using?

You can absolutely film using just the camera on your phone. Some people choose to use an app where they can do some light editing, but I would caution you to not let this part consume your time — especially when you’re just starting out.

The first time I edited a video, I used Instagram because I was already comfortable with the Reels editor. I also used Canva when I wanted to add text in a specific font over top of footage from my phone. I’ve also tried Capcut and Descript. It’s easy to get overwhelmed here, so just pick one and test it out! Or, just stick to the camera on your phone for now.

Bottom line: Don’t let lack of equipment be another excuse to put off filming.

How do I create a video?

As you can see, the options for creating a video are endless. But really — all you have to do is pick something and post it!

Your audience (if you’ve built one already) will cheer you on just for the simple fact that you were brave enough to show up on camera. Use that momentum to keep going!

And if you ever find yourself needing some moral support or quick video tips, swing by my profile — I love helping beginners out!

Thanks to for sharing her simple tips on how to create your first video. Please follow her on LinkedIn and let us know if her advice inspires you to post your first video!

We had a fantastic chat about juggling a side business with a full-time job. Watch the video to learn about our journeys with entrepreneurship. We also share advice on getting started with a side hustle. Spoiler: It’s easier than you think.

Want to watch my next live? Get the Substack app. ⤵️

Get more from David Weiss in the Substack app

Available for iOS and Android

Get the app

PS - Check your inbox next Wednesday. I’m launching a product to help you write better LinkedIn posts so you can grow your brand and attract opportunities. You’re going to love it.

I’m thrilled to share this guest post from my friend, . She’s a tech professional on a mission to elevate empathy. We both understand the importance of people skills in tech, and we share a similar view on leadership.

Her post hits home for me. If I had to sum up my tech career in one word, it’d be ‘change.’ I’ve embraced change over the years, but I’ve also been forced to change. Change can be scary and make you feel powerless. But as you’re about to find out, it’s also a powerful growth opportunity.

Over to you, Colette.

I like math because I can predict the outcome. However, I did not always like math. When I was in the K-12 system and trying to understand how it was being taught, I often felt confused, and it felt like a grey area.

The grey area made me panic because I lacked control.

But the reality is, we have less control than we think, even when we feel secure.

We can see the weather report and plan, but on a day that was supposed to be slightly overcast with the sun, it turns into a downpour.

We sometimes see on the news that perfectly healthy people have horrific traffic accidents. Hence the word - accident.

We can even work at a company for 27 years and one day walk out with a box packed up and a cold goodbye. This is a true story, as I ran into an old colleague who experienced just this. Even after finding new employment, she is still reeling a year later.

What felt like it was in your control was an illusion of our making. It is a myth. The reality is that you were never really in control.

Your Job Is Gone, Your Value Isn’t

Imagine attempting to sign in on your work computer and being locked out.

You call the IT help number on your sticky note next to your cup of coffee. They give a vague response and say they cannot unlock you at this time.

You sit with your coffee until it turns to the verge of being iced coffee. Then the phone rings. It's Rhonda from HR, and your job has been eliminated, along with 5% of the company. You are instructed to ship your laptop back in the box, which will be arriving in the mail later this week.

It's gut-wrenching. If you work in tech, you might have experienced this in the past two years, as we have seen a wave of layoffs impact software engineers, data architects, operations, and other supporting roles.

But, let's think - who are you other than your job?

Are you a parent? Are you a spouse or partner? A close friend?

Do you have a favorite spot in nature?

Do you like reading a particular blog (cough: Substack)?

Is there an event coming up that will bring you immense joy?

Are you kind, empathic, and willing to lend a helping hand?

Who are you?

Think.

While not entirely in your control, your most important value is who you are.

Yes, we need to earn money; many of us do to survive but do not conflate this with your value. Your value is you, not your job.

Tech's Only Constant? Change

A friend of mine has a partner who works at a significant management consulting firm as a software developer, but in a unique role - he is the developer who knows the code that is many years old.

He has a shelf of old books, the size of old phone books, that contain long-forgotten information on this code. Think Fortran, COBOL, and Perl.

Think of the code we leverage today and how the dozens of languages have evolved in the blink of an eye. Change has been constant. Few are like my friend's partner to have retained knowledge of the old code.

But is it really that old? It has been a few decades in the blink of an eye. I have a colleague who graduated undergrad in the 1980s, and for her computer science degree, absolutely none of the tools she worked with then are used today.

A wild statistic is how I read that 65% of students today will work jobs in the future that do not even exist yet! Speaking for myself, if someone had told me in middle school I would work on data in data science, I would have looked at them completely perplexed.

We can fight change, but change is all around us in tech. It is the only constant.

Change Isn’t the Enemy, Stagnation Is

It is human nature to want stability and safety. Change, depending on its nature, can feel like a threat, but it is our constant challenge to accept it.

With some self-management, such as naming our thoughts and feelings, we can take the first step toward acceptance. Change just is. We can fight it, but it is generally futile.

We can extend our empathy to others and help them adapt. This action can be as simple as explaining something simply so they can grasp it and not fear it.

We are in this together. Change is an opportunity - a bigger opportunity for better, beyond what we can see, and a power to behold. Change is not the enemy, but stagnating in denial about it is.

Thanks to for teaching us to embrace change. Please check out her newsletter, , and follow her on LinkedIn.

I’m happy to share this guest post from my friend, . She’s a fellow career switcher and Frontend Developer like me. We initially connected on LinkedIn where her heartfelt and inspirational posts caught my attention.

Doina has a powerful story to share about the challenges she faced when starting her tech career. Whether you’re just beginning your journey as a software engineer or have decades of experience, Doina’s message reminds us all that vulnerability leads to growth.

Over to you, Doina.

Making the switch to tech wasn’t easy. Coming from a background in social work and running a small business, I often felt out of place in a field where technical skills seemed to matter most. But I’ve learned that vulnerability isn’t something to hide; it helps us grow. As Brené Brown says,

Vulnerability is not winning or losing; it’s having the courage to show up and be seen when we have no control over the outcome.

Embracing vulnerability has been key in finding my place in tech.

Why Tech?

I never imagined I’d end up in tech. My roots are in social work, where I wanted to help people, and later, I ran a small business. But when I started exploring tech, I realized it could allow me to help even more people in ways I hadn’t thought possible. It was intimidating at first, but I saw that it wasn’t just about coding. It was about being curious, solving problems, being creative, and making an impact.

The Struggles Along the Way

Imposter syndrome hit hard. I felt like everyone else knew more than me. It wasn’t easy to admit how much I didn’t know, but over time, I realized that I wasn’t alone. We all start somewhere, and it’s okay not to have all the answers. There were moments when the pace of tech felt overwhelming, but instead of running from it, I leaned into the discomfort. I started asking questions and remembering that learning is a process, not a race.

The Lessons I’ve Learned

Fear held me back initially. I questioned if I was good enough or if I belonged. Over time, I realized that everyone feels fear; it’s about not letting it control you. I can trace this back to childhood, when I’d hide from guests at my parents’ house, whether in a wardrobe or on the roof, just to avoid feeling exposed. I thought hiding would protect me, but I learned that growth doesn’t happen in hiding. I had to take ownership, show up, and face my fears head-on.

Vulnerability Strengthens Your Brand

When I first thought about building my personal brand, I believed it had to be flawless. I was afraid that showing any vulnerability would make me seem unprofessional. But I soon realized that being real about my journey, both the successes and struggles, is what connects me to others. As Brené Brown says,

Vulnerability sounds like truth and feels like courage. Truth and courage aren’t always comfortable, but they’re never weakness.

Sharing something vulnerable made me nervous at first, but I was met with kindness. It taught me that being real doesn’t weaken your connections, it strengthens them. Vulnerability has helped me build trust and authenticity with others and with myself.

Advice for Those Considering Tech

If you're thinking about switching to tech, take it step by step and be kind to yourself. There’s so much to learn, and it’s okay to not have it all figured out right away. As Brené Brown says,

We don’t have to do all of it alone. We were never meant to.

Build a supportive community, ask questions, and keep moving forward at your own pace. Every little bit counts.

Tech can feel lonely at times, but it doesn’t have to be. Surround yourself with people who understand, mentors who can offer guidance and peers who get the challenges. As Brown writes in Atlas of the Heart,

True belonging is not something we achieve; it’s something we create.

Embrace Your Vulnerability

Don’t shy away from showing up as you are—imperfect, learning, and vulnerable. When you embrace these qualities, you’ll find opportunities you might otherwise have missed.

Let yourself be vulnerable, curious, and joyful. Transformation starts in those honest moments—not just for you, but for those around you too.

Thanks to for telling her story and giving us invaluable career advice. Please follow her on LinkedIn.

I’m excited to share this guest post from my friend, , an experienced engineering leader whose views on leadership align closely with mine. I asked him to explore an important topic:

There’s more than one way to lead in the tech industry. Gábor highlights three distinct paths—and what each role entails. Understanding these differences now can help you choose the right path and avoid the wrong fit later.

Over to you, Gábor.

Tech job titles can be misleading. A Tech Lead at one company spends most of their time mentoring engineers, while at another, they’re still coding full-time. An Engineering Manager might be hands-off, leading multiple teams, or they could be deep in meetings and still writing plenty of code.

Many software engineers step into leadership without knowing what they’re really signing up for.

I was no exception.

I started as a developer, moved into a lead role while also taking on Scrum Master duties, and later became an Engineering Manager. At first, I thought leadership meant taking on more responsibility and working harder. What I learned is that not every leadership role is the same, and choosing the right one matters more than just getting promoted.

Here’s how to figure out which leadership path actually suits you.

Leadership Titles Mean Nothing Without Context

A Staff Engineer at a startup might design entire systems, while at a large company, they might just review code and give technical input. A Tech Lead could be fully hands-on or spend most of their time running meetings and mentoring.

The title doesn’t define the job—the day-to-day work does.

If you’re looking for a leadership role, ignore the title. Look at what they expect you to own and deliver.

The Three Leadership Paths in Tech

Most leadership roles fall into three categories:

1. Technical Leadership: Designing architecture, making system decisions, setting coding standards. Titles: Architect, Staff Engineer, Principal Engineer, Tech Lead (with technical focus).

2. People Leadership: Mentoring, coaching, and managing engineers to help them grow. Titles: Engineering Manager, Tech Lead (with mentoring focus).

3. Strategic Leadership: Driving big initiatives, working with executives, making business decisions. Titles: Director of Engineering, VP of Engineering, CTO.

Each path requires different skills and responsibilities. Picking the wrong one can easily leave you stuck in a position where you struggle.

The Work You'll Actually Do

Moving into leadership almost always means less coding and more communication. The real question isn’t just Do I want to be a leader? but What will I be spending my time on?

• Tech Leads run standups, do code reviews, and help others solve technical issues.

• Engineering Managers handle hiring, 1:1s, and project coordination.

• Architects work on high-level system design, often with little or zero coding.

The transition to leadership roles isn’t always straightforward. You may gradually take over the leadership role and find that you spend more time in planning meetings than in technical meetings. If you would rather not end up like this, it's best to get this straight as soon as possible.

What Companies Value in Leadership Roles

Leadership is about more than technical skills. Companies expect leaders to:

• Remove roadblocks: Ensure the team delivers efficiently.

• Mentor and grow others: Help engineers level up.

• Influence decisions: Work with stakeholders and executives.

Leadership isn’t about individual success—it’s about the team’s success. If you enjoy seeing others grow, leadership might be a good fit. But if solving complex technical problems excites you more, a Staff Engineer or Principal Engineer role might be the better move.

How I Figured Out My Leadership Path

Early in my career, I thought moving into leadership was the obvious next step. Once I got there, I realized I enjoyed mentoring engineers but hated sitting in endless meetings.

Later, I moved into a role where I could coach engineers without spending most of my time in meetings. That’s when I realized there are multiple ways to lead—and following the default career ladder isn’t always the best choice.

For me, working efficiently means doing work that energizes me, not drains me.

Avoiding the Wrong Leadership Role

I’ve seen engineers step into leadership and regret it—some even give up their title to return to hands-on work.

What were the reasons?

• They didn’t realize how much of their time would be spent in meetings.

• They wanted to stay hands-on, but leadership pulled them away from technical work.

• They thought leadership was the only way to advance.

Leadership is not the next step in your career, it's a career shift. If you pick the wrong path, you’ll end up drained, unmotivated, and possibly burned out. I know from experience that this is not a pleasant situation.

The Right Move for Your Career

If you’re thinking about leadership, focus on the work itself, not just the title or salary.

• If you want to stay technical, consider Staff Engineer or Principal Engineer roles.

• If you love mentoring but don’t want to manage, a Tech Lead (with mentoring focus) role could be a great fit.

• If you’re ready for full people leadership, engineering management makes sense.

The best tech careers don’t follow a straight path—the key is making sure your next step is the right one for you.

Final Thoughts

Focus on the reality of the job, not just the name of it. The same title can mean wholly different things at different companies.

And if you’re unsure what a leadership job really involves, you don’t have to wait for a promotion to try it out.

• Want to take ownership of a codebase? Volunteer as a maintainer/owner of a feature.

• Curious about working with people? Mentor a junior dev or share knowledge with teammates.

• Thinking about management? Ask to sit in on a few leadership meetings.

The best way to figure out your leadership path is to start testing it now. The title will come later.

Thanks so much to for breaking down leadership paths in tech and offering valuable advice on finding the right fit. Don’t forget to follow him on LinkedIn and subscribe to his newsletter, .

I’m excited to share this guest post from my friend, . We recently went live on LinkedIn to talk about balancing side projects with work and family—something we both juggle (or at least try to). It’s not easy, but it is possible.

Side projects don’t just sharpen your skills for your day job; they also open doors to new opportunities and lessons. At your 9-5, you don’t always choose what you work on—but with side projects, you’re the boss. Brittany shares thoughtful advice on making it all work.

Between a full-time job and a family, pursuing a side project can feel like an impossible dream. But is it really? If you’ve ever wondered whether turning something you love into more—after bedtime stories and all—is worth adding to your plate, you’re not alone.

Why Spend Free Time on Side Projects?

For many of us, side projects aren’t just about extra income—they’re a creative outlet, a way to build something meaningful, or even a potential future career path. They give us a sense of purpose beyond our day jobs and family roles. There’s something deeply satisfying about pursuing a passion on your own terms, even if it means working late nights or early mornings.

Side projects also offer autonomy. Unlike a 9-to-5, where your work is shaped by company goals and leadership decisions, your side hustle is yours. You set the vision, decide how to grow it, and reap the rewards of your efforts. That kind of ownership can be incredibly motivating, even if there are moments when you feel like you can’t give it your all.

Is Balance Even Possible?

The short answer? Yes—but not without intentionality. Balance doesn’t mean equal time for everything; it means making space for what matters most at any given moment. Some weeks, your job takes priority. Other times, family needs you more. And sometimes, your side hustle gets a front-row seat.

Balance is fluid. It requires constant reassessment and a willingness to adjust based on what’s happening in your life. The key is to recognize when you’re overextending yourself and course-correct before burnout hits. It is important to make sure you document your WHY and your goals to keep you focused as you shift your focus between everything.

Advice for Parents with Full-Time Jobs Wanting to Start a Side Hustle

If you’re a parent with a full-time job considering a side project, here are some tips to help you manage it without overwhelming yourself:

1. Start Slow and Give Yourself Grace – You’re already juggling a lot. Instead of diving in full force, start with small, manageable steps. Consistency matters more than speed, and grace is the key to longevity. It’s okay to move at your own pace—progress is still progress. There will be days when life takes over, and that’s normal. Allow yourself the flexibility to adapt without guilt, and trust that small efforts will compound over time.

2. Acknowledge Progress to Stay Motivated – It’s easy to feel like you’re not doing enough when progress is slow. Celebrate the small wins—each step forward adds up over time.

3. Pick Something You’re Passionate About – When you genuinely enjoy what you’re working on, it won’t feel like another job. Passion fuels perseverance, making it easier to stick with your side hustle even when life gets busy.

4. Time Block and Set Boundaries – Dedicate specific time slots to your side project, whether it’s early mornings, lunch breaks, or an hour after the kids go to bed. Protect that time as much as possible.

5. Get Support Where You Can – Whether it’s a spouse, friend, or a virtual mentor from LinkedIn, having someone to encourage you and help where possible makes a huge difference.

At the end of the day, balance isn’t about perfection—it’s about making it all fit in a way that works for you. If your side hustle brings you fulfillment, it’s worth making time for. Just remember: slow progress is still progress.

A big thank you to for sharing actionable advice on balancing your 9-5, family, and side projects. Be sure to follow her on LinkedIn and check out her book, Our Sensory World.

I started Besides Code to help engineers develop the leadership and people skills that actually move careers forward. Because the best engineers don’t just solve technical problems, they inspire teams, drive decisions, and create opportunities.

Why Engineers Get Stuck in Leadership Growth

I know how frustrating it is to want to lead but feel like you don’t have the support or resources. I’ve been there, wondering if I’d ever move forward in my career or step into a leadership role. It left me drained and searching for more.

Here’s what holds many engineers back:

❌ Waiting for permission to lead instead of stepping up now.
❌ Great at coding but struggle with communication, influence, and decision-making.
❌ Unsure how to showcase leadership skills to get noticed for bigger roles.

I was stuck too, but I learned how to break through. Now, I help engineers like you grow into leaders without waiting for a title to make it official.

My Journey

👨‍🏫 Started as a teacher where I learned more about leadership than I ever expected.
💻 Transitioned into software engineering and worked my way up to Tech Lead and Engineering Manager roles.
🚀 Led projects, mentored teammates, and took on leadership responsibilities long before I had an official title.
🎯 Now, I help software engineers step into leadership roles with confidence, clarity, and the right skills.

What You’ll Get Here

If you’re a:

➡️ Senior engineer who wants to grow into a leadership role
➡️ New manager figuring out how to lead effectively
➡️ Technical leader who wants to sharpen your people skills

Then Besides Code can help you.

Each week (or so), I share insights to help you:

✅ Lead with confidence even if you don’t have the title yet.
✅ Communicate & collaborate effectively so your ideas get heard.
✅ Grow your personal brand and open new career opportunities.
✅ Navigate career growth strategically without burning out.

Start Leading Today

Want a roadmap to get started? New subscribers get my guide:

10 Ways to Start Leading as a Senior Engineer (Without the Title).

I normally charge for this, but as a subscriber, you get it for free. It’ll hit your inbox as soon as you subscribe. No catch, just actionable insights to help you grow.

What inspired you to write Besides Code and what do you enjoy most about it?

(Asked by )

How do you teach soft skills to engineers?

(Asked by )

Which publications do you read regularly?

(Asked by )

What advice would I give to someone just starting their career in tech?

(Asked by )

How did you get 1,000 subscribers on Substack?

(Asked by )

Did one of my answers help you? Hit reply and let me know.

Is there a topic you’d like me to discuss in a future live? I’d love to hear it.

Thanks for watching!

I’m delighted to share this guest post from my friend, . His engineering career includes management roles at Meta and Amazon. He has invaluable knowledge to share about engineering leadership. And he’s a fantastic writer too.

As you advance in your career, you need to level up your approach to promotions. And in this post, Gilad shares some excellent advice on how to do that.

Okay, we will not move forward with a promotion this half. Gilad, let Peter [not his real name] know the gaps that we highlighted today. We’ll see where he stands in another half.

That’s the message my Senior Director told me at the end of a promotion review meeting. I was disappointed, but hardly surprised. Staff+ promotions rarely go smoothly the first time. Stepping out of the room, I paused to reflect on whether I could have coached Peter so that he’d land the promotion this cycle? The answer was a clear yes. It was also clear that it would have been the wrong thing to do.

Because Staff+ level promotions are different.

Part of what makes them different is that the engineer needs to own more of their growth.

In this post, I will share some tips and tricks you can use to get your next promotion, faster. For context, I was a manager at Meta and Amazon. Since then I have coached hundreds of managers and staff level engineers at the top companies. I can help.

Danny Ocean and His Team

In the 2001 remake of Ocean’s 11, Danny Ocean, played by George Clooney, plans to run an impossible heist. He plans to rob three of the most well-guarded casinos, the Bellagio, Mirage, and the MGM Grand, all at the same time. Danny assembles a team of experts, and together they accomplish the unthinkable.

The first mistake engineers aiming for Staff promotions make is that they go at it alone. They might even have a conversation with their manager about it, but not much beyond it. To grow rapidly, you must build your own team.

What does a promo team look like?

• Your manager

• The cheerleader

• Your (future) peers

• The inside man

Your manager is the first person that you will need to convince. She is also the person most incentivized for your promotion to go through. It’s one of those little secrets that no one really talks about. Getting her on your team is the first step that you need to take.

Growing fast is hard, and you need motivational support. It doesn’t matter if it’s a friend at work, an old colleague, or even your best friend or spouse. Set yourself up for success by bringing in the person who knows how to lift you up when you’re down.

Once you get that promotion, your peers will be other staff engineers. You need to get them to see you as their peer. You need to get this done before the promotion. How do you go about that? Find a staff engineer and work with them. Find some connection between your work and theirs, so that you can build a relationship with them.

The Inside Man. This is the biggest and most powerful secret to a faster promotion.

The Secret—The Insider

In Ocean’s 11, Danny Ocean makes sure to get a member of his team inside the casino staff.

You don’t need to put a mole in the promotion committee. You need to find someone who’s already there.

There are several reasons for this:

• You need to understand the process. What needs to be ready when?

• You need a second opinion. Your manager is not objective. She is biased by working with you. If you’re working on a staff promotion, you’re likely one of her star performers.

• You need to understand the common pushbacks. Someone who has gone through several promotion cycles will be able to pattern match recurring objections with your situation.

• You need a sponsor. You need someone, who is “in the room,” to vouch for you. Your manager is not objective, and everyone involved in the promotion process knows this. Having a champion that is not your manager and is trusted by your leadership can completely turn around a contentious promotion discussion.

So, how do you find this insider?

The best trick is to find a mentor. It will take effort and asking around. The right mentor is someone who:

• Has been in the room for several staff level promotions

• Will be in your room when your promotion is brought up

• Is not in your direct reporting line

• Can share direct feedback every two to three weeks

With this insider, you have the best chances to pass your promotion review on your first try.

The Simple Part That’s Hard

Now, all that is left is just to be great. To meet the staff level expectations consistently.

Easy? No.

This is the hard part.

But, if you have the right team, then at least the path is clear.

You just have to walk it.

One Last Thing

In Ocean’s 11, the con was never about robbing the casinos.

The con was to win Danny’s ex-wife back.

For Staff+ promotion, you need to ask yourself:

Why do I really want this promotion?

Thank you to for sharing his tips on how to land your next promotion. Check out his newsletter, , and follow him on LinkedIn.

I’m happy to share this guest post from my friend, . She has a vulnerable story to share about burnout that we can all learn from.

Your mental health matters. And I’ll never stop saying that. I’ve learned this lesson the hard way in my career. I’ve suffered from burnout and high-stress levels more times than I can count.

In this post, Mindi shares three effective ways to foster mental wellness so you can stay focused on your goals and prevent burnout.

We’re human; we stumble.

Whether a resolution, intention, or goal, it can be hard to maintain momentum. You might grow exhausted or become derailed.

Whatever the case, start by reminding yourself that stumbling is OK. We’re here to talk about ways to pick yourself back up when that happens!

Shifting

Last year, I stumbled. More than once. Despite this, I tried to maintain multiple spinning plates. This led to severe burnout.

If you’re unfamiliar with “spinning plates,” it’s a balancing act, somewhat akin to juggling. Imagine someone holding a small wooden pole, precariously balancing a spinning plate. This feat takes work and attention, but it can be done.

Now imagine that person balancing another pole, another spinning plate. This is harder.

What if they held several poles and plates? More plates means the plates are more likely to fall or stop. We only have two hands!

Burned out, all of my plates suffered. Quality dipped, and it was perpetually harder to keep them spinning. You can probably see where this spiral leads.

When we notice that we’re not performing at our best we can:

• Drop certain plates

• Take a break

Drop certain plates

Dropping all the plates is the worst-case scenario. When you drop everything, you stop, and growth halts.

It’s possible to be forced here by unexpected circumstances. But, if we see the metaphorical train coming, we can jump off the track!

When we do nothing to address oncoming burnout, all the plates fall. They likely smash to pieces unsalvageable. We can catch ourselves and consider other options to avoid losing all of our plates.

The best way to do this is to pause and evaluate each plate. To be most effective, be honest with yourself.

• Do I need to do this right now? Is this a self-imposed pressure?

• What’s the worst that could happen if I drop this plate?

• What’s the best that could happen if I drop this plate?

• Am I spinning this plate for myself or someone else?

• What do I want to accomplish?

Compare the plates. Is our hands-on side project work the most important? Or is time better spent working to improve effectiveness at work?

The individual decision varies, but it’s important to examine thoroughly to identify if you spend your time where you desire or need to. Then you can drop plates that don’t help you progress or are okay to drop. Like a plastic plate that can easily be picked up later, maybe it’s reading a technical book or a personal project you can pause and resume in a few weeks or months.

Take a break

If you get anywhere close to burnout, it’s time for a break. Full stop.

This was difficult for me. I worked and learned during the day; during nights, weekends, and breaks in the workday I would:

• build and learn more things

• write Substack articles

• engage with my LinkedIn network

• organize, promote, and host women in tech events

• read informative books or articles

• work on conference or low-key talks

• …and handfuls of similar things plus balancing time with friends, family, and myself.

☝️ This is a list with too many plates.

To pinpoint what to drop, I paused everything for roughly 2-3 months. I found opportunities to step away from work, take a trip, enjoy a staycation, and find quiet space after my workday.

This space helped me think about what I wanted to accomplish and which plates might be plastic. I recharged, ending with a better sense of what was important for me moving forward.

Start Small

We shifted; we’re ready to regain motivation and resume growth! But how can we do that?

"If you can get one percent better each day for one year, you'll end up thirty-seven times better by the time you're done.” - James Clear, Atomic Habits

“Atomic Habits” is one of my favorite reads from last year. Much of its advice feels like common sense. However, that advice is often forgotten. We rarely enact this common sense.

The two concepts that helped me most:

1. The 4 laws of behavior change

2. Habit Stacking

The 4 laws of behavior change

Reflect on your goals, resolutions, or intentions and brainstorm ideas to make them slightly easier to accomplish. The more you break it down, the easier to start building momentum, however microscopic it may feel.

The 4 laws of behavior change are:

1. Cue: Make it obvious

2. Craving: Make it attractive

3. Response: Make it easy

4. Reward: Make it satisfying

Let’s use a common resolution to start an exercise habit to gain measurable strength or lose a certain amount of weight.

Cue: We might use an alarm or do this during lunch. Find a consistent way to make it obvious that it is time to head to the gym or outside for exercise!

Craving: We may feel energized to burn some energy. Perhaps if we exercise at lunch we feel a craving to blow off some steam.

Response: For a morning alarm, this might be prepping workout clothes near the bed. If we choose lunch and work remote, it may be easiest to step outside, put on a video, or have home equipment rather than heading to another location.

Reward: We are relaxed and enjoy the endorphins we released!

Even if we only make it to the gym at first, roll out a yoga mat, or put on some shoes, this is a small step in the right direction. Do a few minutes next, then a few more. Quickly your habit begins to form. Starting is the hardest part; don’t be too hard on yourself in the beginning and allow organic growth over time.

→ Bonus tip: Reverse the 4 laws of change to break a bad habit!

Habit Stacking

This is one of my favorite concepts because it worked particularly well for me. Building on an existing habit makes a new habit stickier.

I struggled to be consistent falling asleep “on time” for a restful night and an energized morning. I hit snooze on repeat and groggily rushed through a chaotic morning to get to work.

Of course, I still miss the mark sometimes, but it was easier when I built upon my nightly ritual. Instead of brushing my teeth and looking at my phone until I eventually drifted off, I replaced my phone with a physical book.

It keeps me from unnecessary scrolling and promotes my reading habit. Brushing my teeth now triggers an urge to open a book. In turn, I make a little progress in the book and it helps me drift off more easily than my screen!

Give Yourself Grace

There will be bumps and stumbles. It’s normal! The best thing we can do is remain kind to ourselves to keep going when it’s tough.

Self-talk matters. Talk to yourself like you would a friend.

Affirmations and Positive Self-Talk

I’ll leave you with some helpful ideas. We can reframe our self-talk. I like to imagine I’m talking to someone else in my shoes. It helps me provide more genuine self-talk.

Here are some examples:

• We wouldn’t tell a good friend that they are foolish to start a new project or bad at a new hobby right after starting, right?

  • What we can say instead: “I am learning a new craft. I will get better with time.”

• We wouldn’t tell our good friend they are terrible because they made a simple mistake.

  • What we can say instead: “I am allowed to make mistakes, we all do! They are growth opportunities.”

• We also wouldn’t tell a friend that they’re not smart or capable enough to understand a problem.

  • What we can say instead: “I don’t have to know everything right away. I can break it down step by step.”

Thank you to for sharing her story about overcoming burnout and three ways to prioritize your mental health. Please check out her newsletter, , and follow her on LinkedIn.