I Am Learning Cloud Engineering And It Is Giving Me An Identity Crisis
I studied electrical engineering, dropped out, survived war, rebuilt my life in Germany, built a large Arabic-speaking audience, and now I am starting again in English by learning cloud engineering.
The Path Was Not Clean
I studied electrical engineering 12-13 years ago.
Then I dropped out.
At the time, I probably did not understand the cost of that decision. Or maybe I did, but survival was louder than strategy.
Life became a long sequence of practical decisions:
find work
learn German
pay bills
adapt
help family
stay alive mentally
take whatever opportunity was available
From the outside, it can look like inconsistency.
From the inside, it felt like trying not to drown.
The hard part is that survival can become an identity.
You get good at adapting. You get good at starting over. You get good at explaining the strange shape of your CV.
But adaptation is not the same as direction.
At some point, you have to stop being proud of how much chaos you can handle and ask a quieter question:
What am I actually building?
The Strange Part About Audience
I know what it feels like to build attention.
Over 1.3 million people followed me on TikTok. More than 68,000 followed me on Instagram.
That did not happen by accident.
It came from testing ideas, reading audience signals, understanding hooks, making mistakes, staying consistent, and learning how platforms behave.
But most of that work happened in Arabic.
Now I am trying to build in English.
That means the old proof does not fully transfer.
It helps. It gives me pattern recognition. It gives me confidence that consistency works.
But it does not remove the beginner feeling.
In English tech content, I am early again.
In cloud engineering, I am early again.
In public technical writing, I am early again.
That is uncomfortable.
But it is also clean.
Why Cloud Engineering
Cloud engineering attracts me because it is not just another content niche.
It is a skill stack.
Linux teaches you to work close to the machine.
Networking teaches you how systems talk.
AWS teaches you infrastructure, identity, storage, security, cost, and tradeoffs.
Python teaches automation.
Data centers teach you that the cloud still has a physical body.
Writing teaches you whether you actually understand any of it.
That combination feels serious.
Not glamorous. Not easy. Serious.
It has the kind of difficulty that can compound.
And that is what I am looking for now: skills that compound.
Not just attention.
Not just another job title.
Not another reinvention based on panic.
Specific knowledge. Systems. Writing. Technical depth. Distribution. A calmer mind.
The Embarrassing Part
Learning cloud in your early 30s is strange.
You are old enough to see the mistakes from your 20s clearly.
You are young enough to fix them.
You have enough experience to understand discipline.
But you are still beginner enough to Google basic commands at midnight.
That combination is humbling.
There is also a special kind of embarrassment in moving from "I built a large audience" to "I do not fully understand subnetting yet."
The ego does not enjoy that transition.
But maybe that is the point.
The terminal does not care about your follower count.
AWS does not care about your old identity.
Networking does not care about your story.
The work is the work.
And there is something spiritually useful about that.
The Real Lesson
I used to think reinvention meant becoming a new person.
Now I think it means something more practical:
Keep the useful scars.
Drop the old excuses.
Build one boring skill at a time.
For me, that means learning cloud engineering in public.
It means taking my messy background and turning it into a system:
study
build
break things
fix them
document the lesson
publish what I learned
It also means accepting that the identity crisis is not a sign that I am on the wrong path.
It might be the price of entering a better one.
What I Am Learning Now
My current learning stack is:
Linux
networking
Python
AWS
data center fundamentals
CompTIA Network+
AWS Skill Builder
Solutions Architect material
technical writing
Obsidian notes
It looks messy because it is.
But the direction is clearer than before.
I want to become useful in cloud infrastructure.
I want to write in English about AI, cloud, technology, self-education, and the inner work behind building a new life.
I want to talk about technical skills without pretending the human side does not exist.
Because for many people, learning a new career is not just about the curriculum.
It is about shame.
It is about age.
It is about immigration.
It is about language.
It is about identity.
It is about looking at your past and deciding not to let it write the final version of you.
The Question
If you are rebuilding your career, learning cloud, switching fields, starting late, writing in a new language, or quietly panicking inside your own version of the terminal, I want to hear your story.
What are you learning?
What part feels embarrassing?
What part secretly makes you feel alive again?
That is the conversation I want to have.
Because maybe the messy middle is not something to hide.
Maybe it is the most useful part to share.