Today’s Tip
A mistake I made when I first entered tech was focusing too much on the salary. I used to search things like junior JavaScript developer salary thinking that would motivate me. But starting with a salary driven mindset is not the right approach. When you finish learning and do not get a job immediately, you lose hope quickly. And when your motivation is only money, it becomes very easy to quit. What actually works is focusing on building skills, completing projects and improving step by step. When you enjoy the process and develop real abilities the opportunities eventually come. Salary should be the result of your skill not the reason you start and if you are in tech stop comparing yourself to others who are waiting for opportunities to come to them. Instead, create opportunities for yourself by learning, building and taking initiative.
have a good night
@BuildWithAmir
A mistake I made when I first entered tech was focusing too much on the salary. I used to search things like junior JavaScript developer salary thinking that would motivate me. But starting with a salary driven mindset is not the right approach. When you finish learning and do not get a job immediately, you lose hope quickly. And when your motivation is only money, it becomes very easy to quit. What actually works is focusing on building skills, completing projects and improving step by step. When you enjoy the process and develop real abilities the opportunities eventually come. Salary should be the result of your skill not the reason you start and if you are in tech stop comparing yourself to others who are waiting for opportunities to come to them. Instead, create opportunities for yourself by learning, building and taking initiative.
have a good night
@BuildWithAmir
💯2
Part 10
Taking the Leap My First Real Tech Venture
After realizing that most job opportunities required experience I didn’t have, I remembered something from my Debbal days I had always dreamed about creating my own company. I asked myself Can I start now? Do I have enough skills? The answer was simple I had to start. I was lazy at first, hesitant, but I began. I tried to find clients… and it was really hard. Almost everyone rejected me. One afternoon, after returning from class, I noticed a banner for a company and I decided to take a chance. I went to their office and asked for someone who I assumed was the founder. To my surprise he gave me an opportunity. I started working on their full-stack website, including an admin panel to manage the site from behind the scenes. But he was busy, and I couldn’t submit the project fully. When I asked him to check my progress, he said: “I’m busy, we’ll see it again. Eventually the project stalled. I stopped working on it and decided to build my own tech company from scratch and that’s where the real journey of creating, learning, and growing began
@BuildWithAmir
Taking the Leap My First Real Tech Venture
After realizing that most job opportunities required experience I didn’t have, I remembered something from my Debbal days I had always dreamed about creating my own company. I asked myself Can I start now? Do I have enough skills? The answer was simple I had to start. I was lazy at first, hesitant, but I began. I tried to find clients… and it was really hard. Almost everyone rejected me. One afternoon, after returning from class, I noticed a banner for a company and I decided to take a chance. I went to their office and asked for someone who I assumed was the founder. To my surprise he gave me an opportunity. I started working on their full-stack website, including an admin panel to manage the site from behind the scenes. But he was busy, and I couldn’t submit the project fully. When I asked him to check my progress, he said: “I’m busy, we’ll see it again. Eventually the project stalled. I stopped working on it and decided to build my own tech company from scratch and that’s where the real journey of creating, learning, and growing began
@BuildWithAmir
🔥1
Channel Update
Weekly Posting Program
To bring more value and consistency, we’re moving to a clear weekly content system:
1 Monday: Business and startup lessons
2 Tuesday: Coding, tech, and skills
3 Wednesday: Build in public updates
4 Thursday: Strategy and thinking
5 Friday: Discipline and mindset
6 Saturday: Practical tips and frameworks
I'll also share important or timely updates whenever needed.
Stay tuned and keep building.
@BuildWithAmir
Weekly Posting Program
To bring more value and consistency, we’re moving to a clear weekly content system:
1 Monday: Business and startup lessons
2 Tuesday: Coding, tech, and skills
3 Wednesday: Build in public updates
4 Thursday: Strategy and thinking
5 Friday: Discipline and mindset
6 Saturday: Practical tips and frameworks
I'll also share important or timely updates whenever needed.
Stay tuned and keep building.
@BuildWithAmir
Forwarded from Sifen
AI isn’t the problem it’s how we use it. Especially when you’re a beginner, AI can literally do everything better than you, and that’s the dangerous part. When you’re starting something new, fight the temptation and try to learn the fundamentals without AI first.
The point isn’t to write code fast it’s to understand the flow, how debugging works, and why things break or work.
What’s been working for me:
- Take fundamentals seriously
- Build real projects (not just tutorials)
- Use AI to explain stuff, review your code, or help optimize not to blindly generate everything
The point isn’t to write code fast it’s to understand the flow, how debugging works, and why things break or work.
What’s been working for me:
- Take fundamentals seriously
- Build real projects (not just tutorials)
- Use AI to explain stuff, review your code, or help optimize not to blindly generate everything
👍2
Your idea is worthless without execution.
What matters is how fast you test it, build it, and improve it.
Stop planning.
Start shipping.
@BuildWithAmir
What matters is how fast you test it, build it, and improve it.
Stop planning.
Start shipping.
@BuildWithAmir
❤1
Knowing syntax doesn’t make you a developer
Building solutions does
Start before you feel ready
Google what you don’t know
Learn by doing
@BuildWithAmir
Building solutions does
Start before you feel ready
Google what you don’t know
Learn by doing
@BuildWithAmir
👍1
rain outside code inside.
the world slows down but your ideas don't
focus build repeat.
every line you write today brings you closer to what you want to create.
@BuildWithAmir
the world slows down but your ideas don't
focus build repeat.
every line you write today brings you closer to what you want to create.
@BuildWithAmir
🥰1
Authentication and Authorization Were My Biggest Confusion
When I first started learning backend development, authentication and authorization were my biggest problems. I built projects I made login systems I even used JWT
But honestly I did not understand the theory behind it. I was coding by copying patterns not by understanding concepts authentication and authorization felt like the same thing to me and that confusion followed me every day.
What Went Wrong
Most tutorials jump straight into:
Tokens
Middleware
Roles
Permissions
Without clearly explaining what problem each concept solves so even though my code worked my understanding didn’t. the turning Point everything changed when I simplified it
authentication answers only one question:
Who is the user ? That’s it.
nothing about roles , permissions and access Just identity.
Then I understood the next step
Authorization answers:
What is this user allowed to do?
Once I separated these two in my mind, the confusion disappeared.
Why I’m Sharing This
I know many developers are in the same place I was building projects, writing code but feeling confused inside
If that’s you, know this
You are not behind.
You are not bad at programming
You just need clear mental models not more libraries.
@BuildWithAmir
When I first started learning backend development, authentication and authorization were my biggest problems. I built projects I made login systems I even used JWT
But honestly I did not understand the theory behind it. I was coding by copying patterns not by understanding concepts authentication and authorization felt like the same thing to me and that confusion followed me every day.
What Went Wrong
Most tutorials jump straight into:
Tokens
Middleware
Roles
Permissions
Without clearly explaining what problem each concept solves so even though my code worked my understanding didn’t. the turning Point everything changed when I simplified it
authentication answers only one question:
Who is the user ? That’s it.
nothing about roles , permissions and access Just identity.
Then I understood the next step
Authorization answers:
What is this user allowed to do?
Once I separated these two in my mind, the confusion disappeared.
Why I’m Sharing This
I know many developers are in the same place I was building projects, writing code but feeling confused inside
If that’s you, know this
You are not behind.
You are not bad at programming
You just need clear mental models not more libraries.
@BuildWithAmir
⚡2
We Made It Official And This Is Why It Matters
Many partnerships do not fail due to a lack of ideas. They fail because expectations are never clearly defined. This is a reality many founders learn too late For that reason, we chose to take a deliberate and timely step. My partner and I have formally executed our partnership agreement. This decision was not a procedural formality; it was a strategic one Before scaling operations, facing external pressure, or navigating complexity, we prioritized clarity and alignment. The agreement clearly defines how we work together both when circumstances are favorable and when challenges arise.
Why does this matter?
Because strong and sustainable businesses are not built on assumptions. They are built on structure, trust, and shared accountability. Documenting our understanding required open and honest conversations. It strengthened our partnership and provided the confidence needed to move forward with focus and discipline.
With a solid foundation now in place, the next phase is clear
Execute Build Grow Deliver meaningful value.
This marks the beginning of a focused and intentional journey.
@BuildWithAmir
Many partnerships do not fail due to a lack of ideas. They fail because expectations are never clearly defined. This is a reality many founders learn too late For that reason, we chose to take a deliberate and timely step. My partner and I have formally executed our partnership agreement. This decision was not a procedural formality; it was a strategic one Before scaling operations, facing external pressure, or navigating complexity, we prioritized clarity and alignment. The agreement clearly defines how we work together both when circumstances are favorable and when challenges arise.
Why does this matter?
Because strong and sustainable businesses are not built on assumptions. They are built on structure, trust, and shared accountability. Documenting our understanding required open and honest conversations. It strengthened our partnership and provided the confidence needed to move forward with focus and discipline.
With a solid foundation now in place, the next phase is clear
Execute Build Grow Deliver meaningful value.
This marks the beginning of a focused and intentional journey.
@BuildWithAmir
👏1
2026 is closer than we think and no we’re not the same people we were a few years ago.
We broke things.
We built things that didn’t scale.
We trusted the wrong ideas, rushed decisions, and learned the hard way.
But here’s the truth most people won’t say out loud those mistakes were the real education.
As developers and builders, we didn’t just learn new tools we learned how to think, how to recover, how to adapt.
Now, heading into 2026, InshaAllah the focus is sharper than ever
Independence over dependency
Skills that compound, not trends that fade
Systems over shortcuts
Execution over excuses
We may still be learning but we’re no longer guessing.
We’re moving with intention, experience, and discipline.
2026 isn’t a reset.
It’s a level-up.
Same ambition.
Stronger mindset.
Better skills.
Insha’Allah, 2026 will be the year we build with clarity and purpose.
Are you ready for 2026 or will it pass you like the others?
@BuildWithAmir
We broke things.
We built things that didn’t scale.
We trusted the wrong ideas, rushed decisions, and learned the hard way.
But here’s the truth most people won’t say out loud those mistakes were the real education.
As developers and builders, we didn’t just learn new tools we learned how to think, how to recover, how to adapt.
Now, heading into 2026, InshaAllah the focus is sharper than ever
Independence over dependency
Skills that compound, not trends that fade
Systems over shortcuts
Execution over excuses
We may still be learning but we’re no longer guessing.
We’re moving with intention, experience, and discipline.
2026 isn’t a reset.
It’s a level-up.
Same ambition.
Stronger mindset.
Better skills.
Insha’Allah, 2026 will be the year we build with clarity and purpose.
Are you ready for 2026 or will it pass you like the others?
@BuildWithAmir