Why get into all this in the first place

Everyone is talking about AI right now. Too much, too empty. Guides, courses, videos, "look how easy it is."

Strip away the noise and one normal question remains: what of this can you actually use if you're not planning to become a tech worker again?

Can you get into the topic without a fresh background? Without wanting to study for years? Without playing at a profession? Use the tools and get results, not the feeling of being busy.

There's a lot of information. Almost no understanding. Most of the content isn't about the work, it's about presence: looking current, saying the right words, explaining nothing.

It becomes clear pretty fast: it's not about the tools or how many of them you have. It's about how you use them and which problems you actually solve.

I ran into these questions after coming back to ordinary life — already without illusions and without any wish to "get into IT." It just got interesting: what's actually possible now, and where the real entry threshold sits.

Turns out it's much lower than people tend to claim. And the possibilities are much wider, if you don't try to live by the old rules.

In this channel I'm logging the path: what I try, what works, what doesn't, where I get stuck and what has to be rebuilt. No theory for theory's sake. No promises of fast success.

Let me set the frame right away. There won't be any "make a million" buttons, ready-made schemes, or pretty stories without the details. There will be process. Constraints. Mistakes and rebuilds.

This channel is for people who care about understanding how the tools actually work in practice. Not perfectly. Not glossy. For real.

Comments are open. The format is simple: a conversation about work, tools, and results. Everything else is off-topic.

This is not a "personal growth" channel. This is a record of a real path through current reality. Without illusions and without decoration.

Approximation 2. Where this all comes from

Straight up. I didn't "get into IT" and I didn't "retrain."

Twenty years ago I was running IT operations for companies. Servers, networks, users, infrastructure. My job was simple: keep everything working and not falling over. Not development, not coding — the system as a whole and the responsibility for it.

Then that life ended. Not by plan and not on my initiative. At some point there were just no options left.

It's not a story to dissect or a point worth coming back to. What matters is not the fact itself, but what came after.

I dropped out of familiar reality for a long time.

There was a life outside the system: silence, no race, no constant pressure. Jungle. Writing. Minimal external noise.

It wasn't romance and it wasn't escape. It was a forced pause.

And that's exactly what gave me what wasn't there before — distance. Time appeared to watch the world accelerate, speed up, choke on its own velocity. And I, in that moment, stayed off to the side.

Without the constant feeling that you're falling behind. Without the pressure to be on top of everything at once. Without needing to react to every signal.

Looking back, I understand: you can't get this perspective from inside the flow. I wasn't trying to catch up to what was happening — I was watching it.

When I came back, the world was already different. Different tools. Different speed. Different rules.

I didn't start with professions or with "structured" learning. I started with tasks. Systems. Automation. Service integrations. Working products with users, processes, and accountability.

Gradually it added up to full projects — not as ideas, but as working things that have to hold up against reality.

And here's the important part. I'm not trying to be a developer "by the book." I don't care about fitting the role.

What I care about is assembling working systems out of available tools. Understanding what can be automated. Where to remove manual work. Where not to be involved hands-on at all.

AI for me isn't magic and isn't a toy. It's a way to manage complexity and speed without burying myself in details that don't deliver results.

I look at all of this not as a "new profession," but as tools that finally let you do things that used to be too slow, too expensive, or simply impossible.

If the first article was about the questions, this one is about the lens.

What follows is practice.

Pinned

Here I'm logging how I use modern tools in practice, without hype and without playing at a profession.

I don't teach "getting into IT" and I don't sell ready-made schemes.

What I'm interested in is the process: how to assemble a working system out of an idea, where you can automate, and where you don't need to be involved by hand at all.

This channel is about the real path: tasks, constraints, mistakes, and rebuilds. No "make a million" buttons and no stories without the details.

If you care about understanding how this works in reality — you're in the right place.

If you need a quick result without the process — better not to waste your time.

Comments are open. The format is simple: a conversation about work and results. Everything else will be deleted.