My 2026 Resolution – Choosing Depth Over Distraction
Ali Rezaiyan6 min read
It is already February.
Some people think if you miss January, you miss the chance to define your year.
I used to think the same.
But clarity does not follow the calendar.
In the last couple of months I spent a lot of time thinking about my professional future. After more than 10 years of Android development, I feel strong, experienced, and confident in what I do. But I also feel something else:
- 👉 I want to expand.
- 👉 I want to grow beyond mobile.
- 👉 I want to understand the systems behind the apps.
During these months I experimented a lot. With the help of AI tools, I practiced backend development and started to see how much I enjoy the server side of the world.
But arriving at this decision was not easy.
I was divided between multiple paths.
The Roads I Was Considering
Blockchain
In 2024 I invested heavily in learning blockchain.
I built personal projects, wrote smart contracts, connected applications to networks, and truly enjoyed the innovation in that space.
But when I looked realistically at my situation, I saw a bigger knowledge gap than I expected.
Going deeper would require a huge amount of time and energy, and right now time is my most valuable asset.
Creating Programming Courses
This has always been one of my dreams.
I already run a YouTube channel and have been publishing videos for more than a year.
Every time I tell myself, "now it is time to build the course".
But again, time.
A proper course requires deep focus, structure, recording, editing, marketing.
With a full-time job, it becomes a second full-time job.
Building a Business / Startup
This is my ultimate goal.
One day I want to build something of my own.
But let's be honest with ourselves.
A successful business needs:
- technical excellence
- domain knowledge
- network
- capital
- leadership experience
I am building those pieces, but I am not ready yet.
Rushing into entrepreneurship without preparation would be emotional, not strategic.
So What Did I Choose?
I asked myself a simple question:
Which path gives me the strongest foundation for everything I want in the future?
The answer became clear.
👉 Backend development.
- It strengthens my engineering profile.
- It opens more job opportunities.
- It improves my system design knowledge.
- It helps me become closer to building products end-to-end.
- And later, it will support my startup ambitions.
So I decided:
2026 is the year I go deep into backend.
And I want to do it with a plan, instead of watching tutorials forever and hoping it adds up.
🚀 My Backend Developer Roadmap
I'm not starting from zero, which helps a lot.
I already understand:
- Clean Architecture
- Dependency Injection
- REST consumption
- Testing
- CI/CD
- modular systems
- product thinking
Backend is, in many ways, the server-side version of what I already do.
🧱 Phase 1 – Backend Foundations (Network & Runtime)
I don't need university-level theory.
I need practical understanding.
What really happens when a mobile app calls an API?
I will study:
- how DNS translates domain to IP
- HTTP lifecycle
- REST vs RPC
- load balancers and reverse proxies
- latency and timeouts
- stateless systems
If someone asks me in an interview:
"What happens when a request hits your server?"
I want to answer with confidence.
⏱ Timeline: 2 weeks.
☕ Phase 2 – Java & Spring Boot (My Main Weapon)
This is where I become employable as a backend engineer.
The good part? Many concepts translate directly from Android to backend:
- ViewModel → Controller
- UseCase → Service
- Repository → Repository
- Dependency Injection → Dependency Injection
- Retrofit → RestController
The architecture I already know adapts naturally to server-side development.
What I need to master:
Java
- collections
- streams
- concurrency basics
- transactions
- exception handling
Spring
- controllers
- services
- repositories
- bean lifecycle
- configuration
- validation
- global exception handling
The Must-Build Project
I will build a business-oriented system: an Order / Payment / User service.
It will include:
- CRUD
- validation
- error mapping
- pagination
- filtering
- logging
- DTO mapping
- unit tests
- integration tests
When a recruiter sees this, they should think:
this person is serious.
⏱ Timeline: 6 to 8 weeks.
🛢️ Phase 3 – Databases (Critical for the Switch)
Backend interviews love databases.
I will focus on:
- schema design
- primary and foreign keys
- joins
- indexing
- transactions
- migrations
And on the Spring side:
- JPA / Hibernate
- lazy vs eager
- N+1 problem
- query optimization
My project must:
- ✔ store data
- ✔ run complex queries
- ✔ support pagination
- ✔ handle concurrent updates
At this point I stop being an Android developer trying backend.
I become a backend engineer.
⏱ Timeline: 4 to 6 weeks.
🔐 Phase 4 – Real Backend Engineering
Here I move from writing code to thinking about production.
I will learn:
- authentication (JWT, OAuth basics)
- rate limiting
- idempotency
- retries
- API versioning
- caching
- configuration management
And I will upgrade my project with:
- ✔ Swagger
- ✔ security
- ✔ metrics
- ✔ request logging
- ✔ proper error codes
⏱ Timeline: 4 to 6 weeks.
🔁 Phase 5 – Microservices & Messaging
This is also where backend roles start paying more.
I will understand:
- why monoliths fail
- async communication
- eventual consistency
- producers and consumers
- retries and dead letters
Then I will split my system into multiple services that communicate via events.
After this, I can honestly put distributed systems, scalability, and production experience on my CV.
⏱ Timeline: 6 to 8 weeks.
☁️ Phase 6 – DevOps & Cloud
A lot of developers skip this part. I don't want to. I will learn:
- Docker
- environment variables
- CI pipelines
- automated testing
- Kubernetes basics
- cloud fundamentals
And I will make my project actually deployable, because being able to ship it matters as much as writing it.
⏱ Timeline: 4 to 6 weeks.
🧠 Phase 7 – Senior Thinking (Ongoing)
This part never ends.
I will continuously improve in:
- scaling systems
- finding bottlenecks
- data consistency
- monitoring
- incident management
- making trade-offs
Where This Leads Me
If I follow this seriously until the end of the year, I will be in a position to apply for:
- ✅ Backend roles
- ✅ Full-stack roles
- ✅ Platform teams
- ✅ Fintech companies
- ✅ Startups
My Android background will become a strength, not a limitation.
Final Words
For the last few months I didn't really know which direction to take. Now I do.
It won't be the easiest or the fastest path, but it fits the engineer, and one day the founder, I want to be. That's enough for me.