Why I Stopped Trying To Fit My Life Into One Niche
The old topics were different doors into the same question: how do I rebuild, become useful, and document the work?
For a long time, I thought my problem was that I had not found the perfect niche.
Fitness felt close.
Dating felt close.
Self-development felt close.
Business and content felt close.
But every time I tried to put myself fully inside one of them, something felt off.
Not because those topics were fake.
They were real parts of my life.
The problem was that each one was only a piece of the picture.
The Simple Map
Here is the pattern I see when I look back at my old content:
fitness -> dating -> self-development -> business -> tech
At first, that looks like jumping between niches.
But I do not think that is the real story.
The deeper pattern was this:
rebuild yourself -> understand people -> learn systems -> build proof -> document the journey
That is why tech feels different for me now.
It does not replace the old topics.
It gives them a place to connect.
Fitness Taught Me Systems
Fitness was never only about looking better.
For me, it started much earlier.
I entered the gym for the first time around 14. I tried Muay Thai, kickboxing, and later resistance training.
After moving to Germany, after war, after losing the old shape of my life, the gym became one of the few places where I could feel a little bit of control again.
At different points, I was trying to rebuild my body, my confidence, my energy, and the way I saw myself.
The archive is full of fitness writing:
• walking
• fasting
• resistance training
• sleep
• testosterone
• real food
• recovery
• simple nutrition
• training 2-3 times per week instead of living in the gym
But the real lesson was not “fitness is my niche.”
The real lesson was:
If a system is too complicated to repeat, it will not change your life.
That lesson now follows me into tech.
Learning Linux, AWS, networking, or Python has the same problem.
You can collect endless courses.
You can save endless tutorials.
You can make the perfect roadmap.
But if you do not build a small repeatable system, nothing compounds.
Fitness taught me that the boring basics are not beneath me.
They are the work.
Dating Taught Me Trust
Dating content pulled me toward a different question.
How do people trust each other now?
Modern dating is strange because people meet through profiles, screenshots, public opinions, group chats, old posts, and small signals that get judged before two people even know each other.
The deeper issue is not only attraction.
It is trust.
It is patience.
It is values.
It is behavior over time.
Dating taught me that people are not just rational machines making clean decisions.
We are carrying fear, hope, ego, trauma, desire, shame, family patterns, and social pressure.
That matters for content too.
If you write online, you are not only sharing information.
You are building trust slowly.
You are showing your thinking.
You are letting people see your standards.
You are giving them repeated evidence of who you are.
That is why I do not want my writing now to sound like I am pretending to be an expert.
I want it to feel like a real person documenting a real path.
Self-Development Taught Me The Limit Of Advice
I spent years thinking about discipline, identity, purpose, fear, comfort zones, trauma, prayer, meditation, and responsibility.
That material is all over the archive.
Some of it is intense.
Some of it is useful.
Some of it sounds like a person trying very hard to find a stable ground under his feet.
The biggest thing I learned is simple:
Advice is cheap until it becomes behavior.
Everyone knows they should sleep better, train, stop scrolling, learn useful skills, write, save money, and take care of their relationships.
Knowing is not the hard part.
Changing the behavior is the hard part.
This is where a lot of self-development becomes weak.
It gives you a better sentence, but not a better day.
Tech makes this harder to fake.
You either understand why the service failed, or you do not.
You either configured the server, or you did not.
You either built the project, or you only watched someone else build it.
That kind of feedback is uncomfortable.
But it is clean.
Business Taught Me Distribution
The creator-business phase taught me a different kind of lesson.
A good idea is not enough.
You need positioning.
You need hooks.
You need to understand the person on the other side.
You need a clear promise.
You need repetition.
You need a system for turning notes into public work.
I built content around AI, personal branding, digital products, offers, sales, real estate scripts, and audience growth.
That gave me useful skills.
But there was also a risk.
Marketing can become packaging before substance.
You can get good at making something sound important before you have built enough proof.
I do not want that anymore.
I still care about distribution.
I still care about writing clearly.
I still care about building an audience.
But now I want the distribution to follow the work.
Study first.
Build first.
Break things first.
Then write.
Tech Feels Different
The reason tech feels different is not because it is easier.
It is harder.
It makes me feel like a beginner again.
Linux permissions do not care that I built an audience.
AWS does not care that I wrote about fitness.
Networking does not care if a post performed well.
The terminal gives very direct feedback.
That is exactly why I like it.
Cloud, Linux, automation, AI tools, writing, and Obsidian systems give me a way to connect the older parts of my life into one working direction.
Fitness taught me consistency.
Dating taught me human trust.
Self-development taught me that identity needs behavior.
Business taught me distribution.
Tech gives me a serious skill path.
Writing ties it together.
What I Am Doing Now
I am not trying to become “the fitness guy.”
I am not trying to become “the dating guy.”
I am not trying to become another self-development account.
And I am not trying to pretend I am already a senior engineer.
The new direction is more honest:
I am learning cloud, Linux, AWS, automation, AI workflows, and technical writing in public.
I am rebuilding my career through technical skill and documentation.
I am using writing to explain what I am learning while I am still close enough to the beginner confusion to remember what it feels like.
That last part matters.
A lot of expert explanations skip the exact steps that make beginners feel stupid.
I want to write from the middle of the climb.
Not from the mountain top.
The Bigger Lesson
Looking back, I do not think I wasted those years.
I think I was collecting pieces before I had the frame.
Fitness gave me the body and systems layer.
Dating gave me the relationship and trust layer.
Self-development gave me the identity layer.
Business gave me the distribution layer.
Tech gives me the skill and proof layer.
Now the work is simpler:
• learn one useful thing
• build or test it
• document what happened
• explain it in plain language
• publish the lesson
• repeat
That is not a perfect niche.
It is better.
It is a direction I can actually live inside.
What This Means For The Content
You will still see me talk about life.
But it will be grounded in work.
You will see me talk about AI.
But not as magic.
You will see me talk about cloud, Linux, AWS, and automation.
But as a learner building proof, not as someone pretending to know everything.
You will see me talk about writing.
But as a tool for thinking, not only growth.
The point is not to escape every box by becoming vague.
The point is to build a bigger frame that can hold the real life behind the content.
For the first time, it feels easier because I am not trying to manufacture a persona.
I am documenting the work.
And maybe that is the clearest niche I have had so far.
I wrote the longer version of this because I think a lot of people are stuck in the same place:
trying to pick the perfect label before they have built enough proof.
If that is you, start smaller.
Pick one skill.
Build one proof point.
Write one honest note about what happened.
Then repeat until the pattern becomes visible.