Shipping v[Age].0 – Using birthdays as intentional version bumps for your life and work

It is what it is, and I can’t change that: every year, right on schedule, another version of me ships.

The calendar doesn’t ask for my approval. It just rolls forward, drops a birthday in my lap, and quietly asks, “So… what’s new in this release?”

Some people treat birthdays as a reminder that time is running out. I’ve started treating mine as a release date. Once a year, on the same day, I pause, reflect, and consciously decide what I’m going to deprecate, which bugs I’m going to fix, and which new features I want in the next version of myself.

Version bumps for humans, basically.

Over the last ten years, this has become less of a cute metaphor and more of a survival strategy. So much has changed that I sometimes look back and barely recognize the professional I used to be.

I have worked as a network engineer for exactly 31 years, but only in the last ten years have I started implementing the ideas discussed in this article.

I’ve been lucky and tested. I’ve been through wild projects across different environments, industries, and technologies. I’ve planned, designed, engineered, implemented, and supported the kind of infrastructure that most network engineers daydream about when they imagine “big, complex, important work.” Like we say: been there, done that.

On top of that, I’ve taught so many courses as an accredited instructor that I genuinely lost count. Hundreds of students, maybe thousands. Whiteboards, CLI, labs, airplanes, bad coffee. Years of pouring energy into helping other people grow.

And yet, here I am, on another birthday, realizing that the story I want to tell about myself going forward is changing.

On my birthday, my wishes hold a special significance. They’re not just “I hope things get better.” They’re version-change decisions:

That was my release note for this year. But this isn’t just about me. This is about you, too, especially if you’re a few chapters into your career and starting to suspect that simply grinding harder is not a long-term plan.

Let’s talk about what it means to intentionally “version” yourself.

For better or worse, you are the product you ship into the world.

Your skills, your health, your habits, your boundaries, your values, that’s the stack that shows up in meetings, on calls, in incidents, in design reviews, in classrooms, in interviews. You can dress it up with titles and logos, but at the core, people work with you.

Birthdays are one of the few built-in milestones life gives you. Most people just count them and call it a day. But you can also use them as intentional version bumps.

Instead of “I got older,” you can ask:

We do this naturally for software. Nobody expects a system to stay the same for ten years and magically keep up with new load, new threats, and new requirements. We version it. We refactor. We deprecate. We retire things.

But with our careers and our lives, we often just… drift. Same patterns, same tradeoffs, same unhealthy compromises, year after year, hoping the next project or promotion will somehow fix everything.

It won’t.

At some point, you have to say: “This is v[Age-1].x. I’m grateful for what I learned there, but I’m not shipping that same model again this year.”

That’s exactly where I found myself.

If you work in big, complex environments long enough, the list of things you’ve done starts to sound like a brag sheet:

Add to that a teaching career: endless weeks on the road or on camera, helping engineers from all over the place wrestle with protocols, architectures, and real-world scenarios.

It’s a lot. It’s meaningful. It can also be a trap.

“Been there, done that” is great when it means “I have experience, I know how this works.” It’s less great when it becomes “I keep proving the same point over and over, in environments that treat me as an infinite resource.”

The quiet danger of being “that person who can handle it” is that people will keep handing it to you. The gnarly projects. The late nights. The broken processes nobody wants to fix. The mentoring emotional load. The teaching, the documentation, the glue work.

If you’re not careful, ten years of high achievement can leave you with a beautiful résumé and a completely neglected human underneath it.

That’s where my first commitment came from.

My first birthday wish this year was deceptively simple:

That sounds like something people say every January and forget by February. But I mean it in a very literal, engineering sense:

My body and my mind are the platform on which everything else runs.

The teaching, the deep work, the creative writing, the troubleshooting, the mentoring, the travel, the family, all of it depends on whether that platform is stable.

If I treated my core network the way I’ve sometimes treated my health—random maintenance, constant overload, no capacity planning, no redundancy—I’d fire myself as an engineer.

But most high performers I know do exactly that. They run themselves like a cluster permanently in overload: sleep debt as normal, stress as default, food as an afterthought, no real off-switch, chronic context switching, phone lighting up 24/7.

At some point, the platform shows its displeasure: burnout, health scares, chronic issues, strained relationships, and creativity gone. You can keep pushing for a while, but the quality of everything you ship starts to drop.

So in v[Age].0, I’m treating health less like a wish and more like an SLO.

That means asking questions like:

This isn’t about optimization hacks. It’s about acknowledging that my career is a long game and my platform has to last.

For you, the specifics will be different. Maybe it’s sleep. Maybe it’s a movement. Maybe it’s mental health, boundaries around work hours, or addiction to constant news and social feeds. But if you’re a few years or decades into your career and you’ve never intentionally versioned your health, your next release is a good time to start.

My second commitment was sharper:

For a long time, many of us have treated values as fuzzy background noise. “I want to do good work.” “I care about quality.” “I like helping people.” Nice sentiments, but not particularly actionable when money, prestige, or pressure enter the picture.

At some stage in your career, that’s not enough.

You need values that behave more like a routing policy:

Those aren’t slogans. They’re filters.

And just like filters in a network, they determine where your packets (your days, your years) actually end up. If you don’t define them, the default route is “whatever shows up and pays,” and that’s how you find yourself in roles that erode you while you tell yourself you’re just “pushing through.”

Writing your non-negotiables down is uncomfortable. It forces you to admit that some of what you’ve tolerated in the past is not okay anymore. It also forces you to confront reality: your current situation might not survive the filter.

This doesn’t mean storming out of every job at the first disagreement. It means being honest about persistent patterns:

When you’re earlier in your career, you might not feel you can push back. Later, you can’t afford not to. Values that are “non-negotiable” in theory but endlessly negotiated in practice will quietly hollow you out.

In v[Age].0, my routing policy is stricter. I know what I’m willing to do and what I’m not. I’d rather walk away than bend myself into shapes that violate my own sense of what’s right.

You can do the same. The point isn’t to judge anyone else’s values. It’s to stop ignoring your own.

The third commitment was the one that tends to sting the most:

If you’re a solid, dependable engineer, this is probably familiar. You’re the person who quietly holds things together. You solve the hard problems. You take the late-night calls. You mentor others. You own the scary changes. You write the documentation. You teach the courses.

And then, when it’s time to talk about impact, somebody else’s name is front and center.

Sometimes it’s an accident of visibility. Sometimes it’s leadership that doesn’t understand what you actually do. Sometimes it’s a deliberate choice by people who are very comfortable standing on the work of others.

If this happens once, it’s annoying. If it happens for years, it becomes corrosive.

In my case, I realized I had slipped into a pattern: environments where my ability to “get it done” was relied upon heavily but structurally under-recognized. I was over-invested in making the system work and under-invested in checking whether the system worked for me in any meaningful way.

Let me be clear: this is not about chasing applause or transforming into a self-promotion machine. It’s about basic fairness and sustainability.

When your work and your recognition are completely disconnected, a few things happen:

Deciding not to accept that pattern anymore is part of your version bump.

Sometimes that means:

And sometimes it means something simpler and harder: admitting that the environment you’re in is designed to extract your best work without giving you what you need in return, and then leaving.

In v[Age].0, I’m not interested in subsidizing broken environments with quiet heroics. I’m interested in situations where contribution and recognition, while never perfectly balanced, at least live in the same universe.

You’re allowed to want that, too.

There’s another part of this story: being open to new opportunities.

When you say, “I’m excited to be open to new opportunities soon; it’s the perfect time for potential discussions about roles,” you’re not just fishing. You’re acknowledging something important:

The version of you that exists now doesn’t necessarily fit where you’ve been. It might be designed for somewhere else.

The trap for many experienced engineers is staying in motion without direction. More projects, more responsibility, more teaching, more firefighting without stepping back to ask:

When you’ve accumulated a “been there, done that” decade, you have more agency than you might feel. You don’t have to beg for a seat at the table. You can choose which tables you even want to sit at.

So as you bump your personal version, don’t just say “I’m open to opportunities” as a generic line. Be specific with yourself about what you’re open to:

That clarity makes conversations about roles very different. You’re not auditioning for any and every part; you’re looking for a mutual fit.

All of this can sound very abstract until you turn it into a concrete practice.

Here’s what my birthday “release ritual” looks like in simple terms:

You don’t have to copy this format exactly. You can pick your own date: birthday, new year, an anniversary, or some arbitrary day where you decide “this is my release cut.”

The important part is the intentionality. Instead of letting years stack up as generic “more time served,” you periodically ask:

Because yes, time marches on. You can’t change that.

But you can decide that not all years are created equal, that some are just increments, and some are real version bumps.

If you’re reading this and feeling a mix of recognition and discomfort, that’s good. It means there’s probably a v[You].0 waiting to be shipped that looks different from the one you’ve been running in production.

Maybe this is the year you stop running yourself as an overloaded, under-monitored system. Maybe it’s the year you finally write down your non-negotiables. Maybe it’s the year you stop giving 99% of the effort for 1% of the credit.

If so, happy release day, whenever it is for you.

Cheers,
…and blessings on whatever you ship next.

Leonardo Furtado