==Hackers will always be there. Those that don’t speak their language wont even realize they are there. ==

They speak the language of understanding. they know one another due to long term fascination with software and hardware.

Let’s talk about the hacker communities. They are hard to get into for a reason. Not because they love gates, but because trust is expensive and time is non‑refundable. You don’t waltz in with cosplay competence. You show work.

You don’t see anyone running Cursor on arch forums for a reason. When you do. When you do, it’s usually as a roast. Those rooms optimize for understanding, not vibes. They measure you by what breaks when you touch it and how you fix it after. To be honest I feel like they are right to be so hesitant to accept strangers. Imagine worst case scenario someone “vibe contributes” some package which causes their hard work to go into oblivion.

Hackers are proud beings, but one thing they cannot stand and I learnt this from personal experience is when someone is dishonest about their capabilities and they are forced to waste time.

I’m lucky. I didn’t have to build my own laptop or bootstrap Arch from nothing. My co‑founder dragged me to his place one day and sat me down to teach me to code. At first I leaned on AI. He could tell, every time. Even when I told the model “don’t sound like an AI,” he’d look at the diff and shake his head. He knew by instinct: the code was too neat in the wrong places and not skeptical in the places that matter. No fingerprints, no scars.

He called me out line by line. I felt like a toddler handed a terminal as a second language, able to repeat, not converse. That’s the truth behind vibe‑coding: you can imitate the sound of a developer and still miss the sense. Pretend gets you to a demo. Pretend doesn’t get you a product.

5-6 months of suffering later, i kinda got the hang of it. When I say kind off I mean it. If I am being perfectly honest, I want to learn more. Sit me in an IDE with Python and I can tell you what each piece does and also ask questions about why you chose xyz. That fluency / ability to communicate with devs without wasting their time is one of the best gifts I’ve stumbled into. People sometimes confuse me for an engineer or a hacker; I’m fluent enough to collaborate. That’s the point.

I use this skill to talk with our inference providers, cloud compute infrastructure giants and since I now both business and tech, I know what makes them tick and their sales pitches. To date I think we have around 1-2 mil USD in cloud compute still available. We got 10k in gpus alone. I don’t think i will see a cloud bill for a while.

Languages come and go. Paradigms rotate. The language of tech stays. It teaches you how to put your thinking into a language of logic to be able to do some incredible things. Do this enough and the accent develops. Your questions sharpen. Your guesses get cheaper. Senior people stop translating for you; they start planning with you.

Closing

Is it better to be the “professional programmer”: the responsible, goal-oriented engineer who builds stable systems at scale. Or is it better to remain a programmer with an intrinsic love for computing in your heart and relentless hacker perfectionism in your soul?

Maybe the true magic lies not in choosing sides, but in maintaining the tension. Perhaps the best of us are those who learn to wield power without worshipping it, who master complexity without succumbing to cynicism, and who scale without selling out.

If the hacker ethic is to survive, it’ll be because we refused to let success corrupt curiosity; because we understood that code is as much poetry as product; and because we kept asking inconvenient questions, no matter who signed our checks.

One language to rule them all? It’s never been about languages. It’s always been about values.