An Engineer's Secret - Beyond the Code

Working in tech is a strange mix of fun and frustration. You get to build things out of nothing, fix problems that shouldn’t even exist, and somehow convince a computer to behave. But it can also get loud, political, and fast in ways that catch you off guard.

When I started, I honestly thought the hardest part would be keeping up with the tech. Nah. The hard part is finding your footing while everything around you keeps changing. And caffeine only gets you so far.

Learning where your energy goes

One thing that helped me heaps was figuring out what actually drains me versus what puts fuel back in the tank. I kept quick notes for a week and patterns showed up straight away.

This job is constant context switching, so I stopped wasting energy proving things that don’t need proving. The work speaks for itself if you let it. I write things down, keep my PRs tidy, and make decisions traceable.

The people who make it work

Good people matter more than any company slogan. I've worked with teams who cared about the outcome and teams who cared about looking clever. The difference is massive.

Pay attention to who still shows up when things get messy. Those are the ones worth keeping around.

Keeping receipts for yourself

I used to think writing down wins was a bit up myself. Turns out it’s just practical. It’s the career version of commits. A year later, when someone asks what you’ve actually done, you’ve got proof, for yourself more than anyone else.

It’s basically leaving breadcrumbs so you don’t lose track of everything you’ve pushed through.

Holding your own in meetings

Meetings can feel like endurance training. The thing that helped me most is learning not to rush. Don't fill every silence. Don't fight every battle. Some ideas need time to land.

I've seen things I said months earlier suddenly show up as roadmap items. Though it's hilarious watching the same idea you pitched three months ago get praised as "innovative thinking" when someone else says it with better slides.

Keeping curiosity alive

Whenever I start feeling flat, I learn something small. A library, a shortcut, a better way to explain something to a junior. It doesn’t have to be big. The small stuff compounds, and it keeps your head in the right place.

Finding air when things get heavy

Some days you just have to laugh. The deploy that breaks right before the demo, the “simple fix” ticket that eats your week, the meeting that ends with more confusion than answers.

The laugh isn’t denial. It’s breathing space. You need it.

The hidden side of resilience

People talk about resilience like it’s this big heroic thing. But most of the time it’s just accumulation. You handle enough stuff, and one day you realise you don’t react the same way you used to. You bounce back faster. You don’t spiral over things that made you fall over.

It’s growth, but you only notice it looking backwards.

Why I still do this

I still remember studying web dev, turning up late to class (classic), and trying to sneak in because a business owner was visiting. He asked the room why we were studying this stuff.

Half the class said “for the money”. When it got to me, I said, “I love coding.” lol.

He ended up hiring me part-time after that. I didn’t think much of it back then, but now I get it. You can teach skill. You can’t teach curiosity. We’re still mates today.

I’m still friends with a lot of people I’ve worked with over the years too. That’s the best part of sticking around long enough, you get to see where everyone ends up. This industry can be a rollercoaster, but the relationships make it make sense.

At some point you realise it's never really been about money. You need it, sure, life doesn't pay for itself. But once you find work that feels right, that part sorts itself out. You show up because you care, because building things still feels like the right use of your time.

And when you’ve built enough, you start to see that survival isn’t just about staying in the industry, it’s about keeping the part of you that still loves it.