Yes, it's much easier directly in Telegram.
Many people are already familiar with in-chat payments, and for users behind censorship, Telegram often feels safer and more accessible than opening websites with unknown crypto gateways.
You might want to consider adding a Telegram-based payment bot.
For users in China, Iran, or Russia, this could be much more practical than navigating obscure web wallets or exchanges.
I don’t want to sound discouraging, but I’ll be honest.
First of all, you need to figure out what you really want and what you’re willing to do to get there.
Some people mentioned starting your own project above. I think that’s a really great path. I was in a similar situation: I started learning programming about five years ago. I don’t have a technical background at all — I’m actually a humanities student. I didn’t choose programming because it was trendy. I chose it because something inside me said, “This is my path.”
At the time, I lost my job. I had several children to take care of. It was a tough time, but I kept learning every day - step by step.
And now? I create things. Not for money yet - for craftsmanship, for freedom, for the future. And little by little, doors are opening.
That’s why I say: follow your heart, but don’t forget about your mind.
No problem is unsolvable. Sometimes the road is long. But it’s still a road.
Yeah, that’s a fair point. Abstraction is part of progress — and we do rely more and more on things “just working.”
But that trust can be dangerous when we don’t even know what we’re trusting.
And when something breaks, it can leave us completely blind.
I’m not saying everyone needs to go all the way down to the metal — but I do think it’s important to at least understand the boundaries. Know what’s underneath, even if you don’t touch it every day.
Otherwise, it’s not engineering anymore — it’s guessing.
And I’ve never been good at just “believing” things work. I need to poke around, break them, fix them.
That’s how I learn. Maybe I’m just stubborn like that.
Yes, I think many people are starting to feel this exact tension.
The key, I believe, is to mentally reframe the AI: it's not the driver, it's your assistant — a helper, a debugger, maybe even a silent teacher. But you're still the architect. You're still the creator.
The problem begins when we forget that. When we let the AI lead the design, the structure, the reasoning. That’s when we start losing ownership — and understanding.
Ironically, AI was built to help us — not to replace our thinking. But without solid fundamentals, it's easy to let it take over. And then we're just directing prompts, not building things we truly understand.
I think the real sadness is that many developers may stop learning the deeper fundamentals — the things that AI can't replace.
When people start relying on the "I just want it to work this way" mentality and let AI take over, they can lose track of how things actually work under the hood. And that opens the door to a lot of problems — not just bugs, but blind trust in things they don't understand.
For me, the joy is in understanding. Understanding what each part does, how it all fits together.
If that disappears, I think we lose something important along the way.
I really appreciate you sharing that journey — it reads like a personal history of programming.
I’ve heard others mention the elegance of Turbo Pascal and Delphi, especially the string handling.
And yes — C macros and pointer syntax can absolutely feel like arcane incantations sometimes.
I guess in the end, we all gravitate toward the languages that feel like home.
Exactly. That’s how I feel too — writing small, precise tools in C by myself is strangely rewarding.
Thanks for sharing that — it’s good to know others feel it too.
I’ve heard similar thoughts from others who went into Rust expecting something radically freeing — and found themselves wrestling with the borrow checker and unexpected heap usage.
I still want to explore Rust at some point, but I think it’s important to hear real experiences like yours.
Sometimes the simplicity of C — for all its sharp edges — feels more honest.
For me, it’s not just about building tools — it’s about understanding what I’m building.
I like knowing where the bytes go. What the memory looks like. How the binary behaves.
It slows me down, sure — but it teaches me things I didn’t even know I didn’t know.
I’m not building for scale or clients. I’m building to see.
That kind of closeness makes the machine feel less like a mystery, and more like a partner.