It's You: Why Your Career Depends on Action, Not Excuses

The Conversation That Changed Things

A few weeks ago, someone posted about feeling behind in their tech career. The response was overwhelming—the community cared. But one developer, FrancisTRᴅᴇᴠ, noticed something in the feedback that bothered him. Yes, everyone has regrets. Yes, the job market is tough, especially with AI changing the landscape. But there's a difference between recognizing where you're stuck and doing something about it.

He started talking with other developers about this. In a group called Virtual Coffee, conversations with Giorgi Kobaidze and Jiro (known as @georgekobaidze and @codingwithjiro) kept circling back to the same theme: regrets and inaction. They talked about not networking in college because they were shy. Not pushing themselves beyond the bare minimum. Not showing up.

Then it clicked. The real problem wasn't market conditions or lack of talent—it was a choice to stay still.

Two Types of People

When you talk to developers about their careers, you see two patterns emerge.

One group identifies their regrets and acts. They realize they didn't network because of fear—so they join communities, start sharing their work, attend events. They learn that most of the scary thoughts in their head never actually happen. They rebuild.

The other group identifies the same regrets but stops there. They see the job market and think, "I'm not good enough anyway." Impostor syndrome is real. The market is tough. AI is changing hiring expectations. So they use these truths as permission to do nothing. They accept defeat and do the bare minimum.

There's a third group worth mentioning: people trying their absolute hardest and still not getting results. That's real too. But even then, Kobaidze points out something most people miss. In his own 6-month career review, he laid out the unsexy truth: he kept "pushing myself to the limit, at times even through severe physical pain (no exaggeration), and sacrificing a lot of my personal life along the way. My evenings, nights, and weekends were dedicated to all of this."

That's not inspiring in a motivational-poster kind of way. It's just honest. He worked while others didn't.

The Real Secret Isn't New

You've probably heard this before. You've probably rolled your eyes. But there's a reason it keeps coming back: it's true.

FrancisTRᴅᴇᴠ references a line from the movie Ip Man that stuck with him: "It's not about style. It's about you."

In martial arts, that means technique doesn't matter more than the person holding the sword. In software development, it means your results don't depend on the "right" tech stack, the "right" job market, or the "right" timing. They depend on you.

Every developer has a different goal. Some want to stay ahead of AI. Some want to learn every programming language. Some want to fill their GitHub graph with contributions. Some focus on data analysis or machine learning. Everyone has a different "style" because everyone has different constraints and goals.

But that's exactly the point. What works for someone else's career won't work for yours, because your situation is different. Your fears are different. Your starting point is different. Your path is yours.

Instead of blaming the market for being "cooked," do one thing that shrinks that problem: network. Participate in challenges on DEV Community or similar platforms. Instead of thinking "I'm not good enough," ask the community for advice. Share what you're struggling with. Don't hide it.

FrancisTRᴅᴇᴠ is living proof this works. He was afraid of networking. But he took one small step—joining DEV Community—and kept showing up. And he's here now, moderating a community, writing posts people read, having the exact conversations that helped others.

It took time. It didn't happen overnight. But it happened.

The Thing Nobody Wants to Hear

Discipline and consistency aren't sexy. They're not the answer you want. But they've always been the answer, and they still are.

The only question is whether you'll actually commit to them—not when things are perfect, not when the market improves, not when the news stops being scary. Now. Regardless of what's happening outside.

You might be scared of networking. You might be exhausted by all the AI doom you read online. You might genuinely believe you're not good enough. Those feelings are valid. But if you let them make your decisions instead of you, then you've handed control over to external things. Your fear becomes your ceiling.

Instead, what if you decided: I'm going to take one small action this week, even if I'm terrified. I'm going to ask one person for advice. I'm going to share one thing I've learned. I'm going to show up.

Do that next week too. And the week after.

There's a quote that keeps coming up in this conversation—one attributed to Franklin D. Roosevelt: "A smooth sea never made a skilled sailor." The point is simple: easy conditions don't build skill. Struggle does.

But here's the twist: you can't wait for the rough seas to find you. You have to go sailing.

It Comes Down to You

The developer market is changing. AI is reshaping what companies look for. Hiring is genuinely harder. All of that is true. But truth isn't destiny.

The truth is also this: the people who succeed aren't necessarily the smartest, the most talented, or the ones who got lucky. They're the ones who did the work when the work was hard, when nobody was watching, when the odds looked bad.

They networked when networking felt risky. They shipped when they weren't sure it was perfect. They asked for help when asking felt like admitting failure. They kept going.

Your career is the sum of your actions, not your circumstances. The market is real. Your doubts are real. But so is your ability to choose what comes next.

So the question isn't "Is the job market rigged?" or "Do I have what it takes?" The question is: what are you going to do about it? Because at the end of the day, that's the only thing that's actually in your control.

And that's where the results come from.

Conclusion

Feeling behind in tech isn't unusual—most developers feel it at some point. The unusual part is what you do with that feeling. You can let it paralyze you, or you can let it push you. The choice is yours, and it always has been.

Merits

• Honest perspective on self-doubt without toxic positivity
• Emphasizes actionable steps: networking, sharing, community participation
• Acknowledges real obstacles (AI concerns, tough job market) while showing they're not insurmountable
• Uses real examples from the developer community
• Balances personal responsibility with empathy for those struggling

Demerits

• Doesn't address systemic barriers like discrimination or access to mentorship
• Could feel discouraging if you're already burned out
• Success stories are harder to achieve with certain constraints (health, family, location)
• The "just work harder" framing, while honest, isn't a complete picture

Caution

This article is educational and reflects a perspective shared within the developer community. It does not constitute career advice tailored to your individual situation. Any specific examples or timelines mentioned (such as timeframes for success) are illustrative. Readers should verify claims and consider their own circumstances before making career decisions. The motivational framework here works best when paired with realistic self-assessment and access to actual mentorship.

Frequently asked questions

• How do I overcome impostor syndrome as a software developer?
• What's the best way to start networking in tech if I'm introverted?
• Is it too late to change careers or start fresh in software development?
• How can I stand out to employers in a competitive job market?
• What should I do if I feel behind compared to other developers?
• How much time should I dedicate to side projects and open source?
• How do I build confidence when applying for jobs I'm not 100% qualified for?
• What's the difference between healthy ambition and unhealthy burnout in tech?