In the next few weeks, I’ll explore with you how to choose a developer path: from technical deep dives to people leadership, and everything in between. Whether you’re at a fork in the road or just getting curious, this series is for you. Week 1 will be about exploring (experimentation, choosing a growth theme), Week 2 we'll focus on becoming visible and taking initiative, while the final week is about claiming growth (or moving away) and choosing your own path. Join me on this journey!

Why Sharing Feels Like You're Bragging (But Matters Anyway)

Ever feel weird about talking about your own work?

Like if you post a small win, someone’s going to roll their eyes?

Or that “real devs” don’t need to say they’re growing, they just are?

Yeah. Been there.

I always thought I would just add to the noise: "There are tons of developers out there who have way more valuable things to say than me".

Turns out I was wrong.

Sharing content over the past few months has made me valuable connections all over the world. I got positive feedback from people, was able to help then get unstuck, share my thoughts and create a safe little community around me where people can voice their concerns and feel related to.

Sharing Your Work

Here’s what I’ve also learned:

Visibility ≠ vanity. Visibility = leverage.

If your work stays hidden, so do your skills, your growth, and your potential impact.

Visibility Isn’t About Bragging

It’s about:

  • Helping others learn from your process
  • Making your contributions visible to your team
  • Creating clarity for those who depend on your work
  • Building your internal (or external) reputation

Your manager can’t read your mind and your team might not see the problem you quietly fixed.

Sharing helps them see and learn.

Ways to Be Visible (Without Feeling Like a Salesperson)

  • Drop a short update in Slack: “Hey, I just refactored X and documented Y.”
  • Share “what I learned” notes in retros or planning
  • Walk a teammate through your PR before merging
  • Write an internal blog post or run a casual demo
  • Post a small thread on LinkedIn/Dev.to

The key? Teach, don’t just promote. Share your curiosity! You'd be surprised how many people share your thoughts.

Visibility Builds Trust

When people see your thought process, they:

  • Trust your decisions
  • Ask for your input more often
  • Consider you for growth opportunities
  • Learn faster (because you model learning out loud)

And honestly? It helps you reflect and celebrate, too.

Final Thought

You don’t have to shout or be “that person.”

Just be visible enough for your work to have the impact it deserves.

💬 What’s one thing you’ve done recently that’s worth sharing, even if it feels small?

In case you want more guidance: I'm now offering free 30-minute coaching calls for developers who want to grow (whether you're junior, medior, or senior). In this call, we’ll talk about your current situation, challenges you're facing, and where you want to go next. You'll receive tailored advice specific to your goals and concrete next steps. No catch. Just me, helping you grow.

👉 Book your free call here: https://calendly.com/tim-lorent/free-30-minute-growth-call-for-developers

Speaking of free guidance: download my Free Developer Growth Kit — 3 Practical Guides to Grow from Coder to Leader. It gives you practical tools to level up your skills, mindset, and workflow, without burning out or guessing your next step.

Or if you’re ready to take the next step: check out my book From Hello World to Team Lead or the developer platform for career growth Campfires.dev. 20% of all revenue from the book and coaching will be donated to tech charities like TechMeUp, SheSharp, GirlCode, HackYourFuture.