About Me

Or: How a Commoner from Konoha Learned to Turn Curses into Code

My name is Kustian—pronounced like Koosty, not "Christian" or whatever autocorrect thinks it is. Here's the quick rundown:

Location: Konoha (yes, really)
Day Job: Software Engineer (the kind that debugs at 2 AM)
What Gets Me Talking: Tech, Culture, Society, and why things are the way they are

But stats don't tell stories. So here's mine.

The Blessing That Felt Like a Curse

Living in Konoha sounds cool until you realize being born a commoner here means you're starting the game on hard mode—no cheat codes, no safety net, just raw survival instincts.

The nobles? They get shortcuts, connections, and a safety net the size of a castle. Me? I got awareness. The kind that comes from knowing nothing is guaranteed, nothing is free, and every step forward is earned with bruised knees and late nights.

Real talk: Growing up under what felt like a curse taught me the most valuable lesson—nothing should be taken for granted. Not opportunities. Not comfort. Not even tomorrow.

College: A Quest I Didn't Sign Up For

I earned my degree through what I can only describe as the developer's version of a dark souls playthrough. No easy mode. No saves. Just pain, persistence, and a ridiculous amount of coffee.

Was I basically a slave during that time? Yeah, let's call it what it was. Did it suck? Absolutely. Would I recommend it? Hell no.

But here's the plot twist: that discomfort, that grinding struggle where every day felt like debugging legacy code without documentation—that shaped who I am today. It taught me:

How to solve problems when there's no Stack Overflow answer
How to keep going when the error messages make no sense
How to find workarounds when the "proper" solution isn't available
That survival instinct is the best teacher

The Punchline: Pain is a terrible teacher, but a memorable one. I wouldn't wish that journey on anyone, but I also wouldn't trade what it taught me.

My First Gig: Adventurer Mode Activated

My first job as a Software Engineer? Picture this:

No contract (just vibes)
No direct contact with the employer (mystery quest)
Show up on-site and figure it out (tutorial? what tutorial?)

It was like being handed a sword and told "good luck, the dragon's that way." No onboarding, no documentation, no "here's how we do things around here." Just... go.

What I learned:

Adaptability isn't optional in this industry
Documentation is a myth (write your own)
The best way to learn is by breaking things (and fixing them at 3 AM)
Sometimes the best mentor is your own trial and error

Looking back, it was chaotic, stressful, and absolutely not sustainable. But it also taught me to be resourceful, to ask the right questions, and to never assume anyone will hold your hand.

Would I recommend this approach? No. Modern me would've said "where's the contract?" and "what's the onboarding process?"

But did it work? Unfortunately, yes. I survived. Barely.

The River Philosophy: Swim Upstream

Here's how I see the world: it's a river. Everyone's in it, moving along.

Most people float with the current—it's easier, it's comfortable, it's what everyone else is doing. The current takes you to the same places everyone else goes, with the same views, the same outcomes, and the same "this is fine" energy.

Me? I swim against it.

Not because I'm trying to be difficult (though I probably am). Not because I enjoy the struggle (spoiler: I don't). But because swimming upstream means:

You see things differently: When you're fighting the current, you notice details others miss—the rocks, the eddies, the hidden paths.
You build strength: Flowing is easy. Fighting builds muscle—mental, physical, emotional.
You choose your destination: The current decides where it takes you. Swimming upstream means you decide where you're going.

Is it harder? Absolutely. Every stroke is effort. Every moment is resistance.

Is it worth it? For me, yes. Because the alternative is ending up where the river decides, not where I decide.

What This Means for My Work

As a Software Engineer, swimming against the current looks like:

Questioning "best practices" when they don't actually solve the problem
Pushing back on tech trends just because they're trendy (looking at you, blockchain-everything phase)
Choosing the hard-but-right solution over the easy-but-messy one
Building systems that matter, not just systems that ship

It also means:

Debugging when others would give up
Learning the ugly, boring fundamentals instead of jumping to the shiny new framework
Writing documentation because someone has to care about future-me
Being the person who asks "but why?" in meetings (sometimes too many times)

The Cost: More effort, more pushback, more late nights.

The Reward: Better code, better systems, and the satisfaction of knowing I didn't just take the easy path.

Why I Share This

Because maybe you're swimming against your own current. Maybe you're the commoner in a room full of nobles. Maybe you're debugging life without a manual.

If that's you—you're not alone.

The struggle isn't pretty. It's not a motivational poster. It's messy, exhausting, and full of moments where you wonder if it's worth it.

But here's what I know: the people who swim upstream are the ones who build new paths. They're the ones who don't accept "that's how it's always been done." They're the ones who turn curses into code, pain into progress, and struggle into strength.

So yeah, I embrace the struggle. Not because I love it, but because it's the only way I know how to move forward. Against the current. Upstream. One stroke at a time.

And if you're swimming too? Keep going. The current is strong, but so are you.

P.S. If life ever feels easy, check if you're actually moving or just drifting. Usually, it's the latter. 🚀