Day 100 is the end of counting the days, not the end of the journey.
MY 100 DAYS IN TECH june
18, 2026 — September 25, 2026
100 days. One journey. Countless lessons
.On June 18, 2026, I started my 100 Days in Tech,Today September 25, 2026, I have reached Day 100.When I started, I didn't know exactly what these 100 days would become. I didn't know all the things I would learn, the questions I would ask, the plans I would change, the things I would build, or how much my understanding of learning itself would change.I only knew that I wanted to start.And now, after 100 days, I can finally look back at the journey as a whole.
WHY I STARTED
I didn't start my 100 Days in Tech because I was already good at technology.I started because I wanted to learn.I had already developed a strong interest in cybersecurity, ethical hacking, Python, artificial intelligence, technical writing, and technology generally.But having an interest in something and actually putting in the work are two different things.I wanted to move from simply saying:“I am interested in technology.”to actually being able to say:“I am learning technology.”That difference became important to me.
So I decided to give myself 100 days.
Not 100 days to become an expert. Not 100 days to master cybersecurity. Not 100 days to suddenly become a professional. But 100 days to learn, build, document, reflect, and become better than the person who started.
DAY 1
Day 1 was June 18.
At the beginning, I didn't have every step planned out.I had goals, but I didn't have all the answers.And I think that is one of the most important things I learned from this journey:“You don't need to know everything before you start.”Sometimes you only need enough clarity to take the first step.I started with the intention of making learning a consistent part of my life.But very quickly, I realized that the challenge wasn't going to be technology alone.
It was going to be consistency.Could I keep learning while working?Could I continue when I was tired?Could I balance technology with my Deen, Qur'an, reading, health, and other responsibilities?Could I keep going when a day didn't go according to plan?Those questions followed me throughout the 100 days.
MY DAILY REVIEWS
One of the things that made this journey different for me was that I didn't just count the days.I reviewed them.
My daily reviews became a record of what was happening in my life while I was learning technology.I wasn't only asking:“What did I learn today?”I was also asking:Did I show up?Did I keep my discipline?What did I accomplish?What didn't I accomplish?What can I improve?What should I focus on next?My daily reviews included different parts of my life — Deen, Qur'an, learning, Python and cybersecurity, work, reading, health, content creation, reflection, wins, improvements, and my daily score.Looking back, I realize that those reviews were almost as important as the technical learning itself.Because a single day can look small.But when you put 100 days together, you begin to see the journey.TECHNOLOGYThroughout these 100 days, cybersecurity remained one of my strongest areas of interest,
My interest in ethical hacking isn't simply because the word “hacking” sounds interesting.I became interested because technology affects people's everyday lives.People get scammed.Accounts get compromised.People click links they don't understand.People use websites and applications without knowing what happens behind them.
Technology can be used to help people, but it can also be abused.I want to understand how technology works so that I can eventually use that knowledge responsibly.That is why ethical responsibility has always been important to me.I don't want to learn technology simply to say I know it.I want to understand it well enough to use it properly and eventually help others understand it too,
BUILDING MY CYBERSECURITY FOUNDATION
One thing I learned very early was that I couldn't just jump straight into advanced cybersecurity.I needed foundations.I spent time learning about cybersecurity concepts, networking, computer technology, ethical hacking, and different technologies that people interact with every day.I explored concepts around things such as VPNs, proxy servers, networking, DNS, firewalls, and security.The more I learned, the more I realized that cybersecurity is much bigger than what people often imagine.
It isn't simply about hacking into something. It involves understanding systems, networks, people, risks, vulnerabilities, protection, and responsibility.And the deeper I went, the more I realized how much there still is to learn.
PYTHON
Python became another important part of my 100 Days in Tech.I understood that programming would be useful for my long-term cybersecurity journey, so I started building my foundation.I learned through different resources and worked through Cisco Python Essentials.I completed Module 1 and continued progressing through the following modules.On September 1, I reached Module 2.3.That may sound like a small milestone to somebody else.But for me, it represented something bigger.
It showed me that I wasn't just talking about learning Python anymore.I was actually doing it.And I learned that technical learning doesn't always feel dramatic.Sometimes progress looks like finishing another module.Sometimes it looks like finally understanding something that confused you before.Sometimes it is simply sitting down and trying again.
LEARNING IS NOT LINEAR
There were things I understood quickly.There were also things I didn't.Sometimes I had to go back.Sometimes I had to ask questions.Sometimes I needed another explanation.And sometimes I had to accept:“I don't understand this yet.”That word — yet — became important.Being a beginner doesn't mean you are failing.
It means there are things you haven't learned yet.And that's okay.I started becoming more comfortable with being a beginner instead of constantly feeling like I had to prove that I already knew something.LEARNING IN PUBLICAnother major part of these 100 days was learning in public.I started documenting my progress.I shared what I was learning.I wrote.I created content.I connected with people.And gradually, people started following the journey.But the biggest thing I gained from learning in public wasn't simply the growth in followers or connections.
It was accountability.When you share your learning, you become more conscious of what you are actually doing.
You also learn how to communicate.And I discovered that explaining something can expose whether you truly understand it.That became one of the reasons technical writing and content creation became part of my journey.
OFF_LIMIT TECH
During this journey, my learning also developed into something bigger:OFF_LIMIT TECH
OFF_LIMIT TECH represents the kind of technology platform I want to build.Its idea is simple:“Making technology easier to understand, one concept at a time.”I started creating beginner-friendly technology and cybersecurity content.I worked on topics such as:VPNsProxy serversCybersecurity conceptsComputer literacyScam awarenessTechnology explanationsI also explored video creation, technical writing, research, scripting, and publishing.And I learned something important:Creating educational content is also a form of learning.When you have to explain a concept to another person, you can't hide behind complicated words. You have to understand it.That is the kind of learning I want to continue.
CERTIFICATES ARE NOT THE WHOLE STORY
During these 100 days, I also completed different learning programs and earned certificates in areas related to cybersecurity, ethical hacking, Python, and AI.Those achievements matter to me.But I don't want my journey to be defined only by certificates.A certificate can show that you completed something. It doesn't automatically show how well you understand it.For me, the more important question became:“What can I actually do with what I learned?”That question changed the way I looked at learning.
MY WORK AND REAL LIFE DIDN'T STOP
Something important about my 100 Days in Tech is that I wasn't spending 100 days sitting at a computer with nothing else happening.I still had work.I was doing plumbing work.I still had my Deen.I was reading Qur'an.I was reading books.I had family and everyday responsibilities.There were days when I was tired.There were days when work took a lot of energy.There were days when I couldn't accomplish everything I had planned.And that made the challenge more real.I had to learn how to build technology into my actual life instead of waiting for the perfect conditions to learn.
DISCIPLINE
One of the biggest things I learned wasn't actually technical. It was discipline.I learned that discipline doesn't mean doing everything perfectly every single day.Sometimes discipline means showing up.Sometimes it means doing less but still doing something.Sometimes it means resting.Sometimes it means returning after a difficult day. One sentence that became meaningful to me during this journey was:“Discipline is not about being perfect every day. It's about returning to the path every time life pulls you away.” That describes a large part of my 100 days.
THE QUESTIONS STARTED CHANGING
Something else changed during the journey. My questions became different. At the beginning, I was mostly asking:“What is this?”“How does this work?”“How do I learn this?”Later, my questions became:“What should I learn next?”“What skills do I actually need?”“How do I gain practical experience?”“How can I contribute?”“How do I build a portfolio that shows evidence of my skills?”“Am I trying to do too much?”“Should I be creating more content or spending more time learning?”“What happens after Day 100?”Those questions showed me that my journey was changing from simply learning things to thinking about direction.
WHEN I CHANGED MY PLAN
On September 10, I made an important decision.I decided to stop creating new formal videos and articles for the remaining part of my 100 Days in Tech.Why?Because I realized I didn't want to rush.I had been learning. Writing. Creating. Building. Working. Planning. And trying to keep up with everything else.I realized that if I continued forcing myself to produce new content simply because I had planned to, I could end up rushing the very journey I was trying to document. So I changed the plan.For the remaining days, I focused more on learning, building, reflection, and completing the journey properly.That decision taught me something:“Changing your plan doesn't always mean you've given up. Sometimes it means you understand your goal better.”
I LEARNED THAT BEING BUSY IS NOT THE SAME AS MAKING PROGRESS
This became another major lesson. It is easy to look productive. You can post every day.Complete courses.Collect certificates.Start projects.Write articles.Create videos.But I started asking myself:“Am I actually becoming better?”I would rather deeply understand something than rush through several topics.I would rather build one meaningful project than have ten unfinished projects.I would rather create something useful than create something simply because I feel pressured to post.The goal isn't to look busy.The goal is to grow.
MY PORTFOLIO
Another major milestone during the journey was building my personal portfolio website.I wanted a place where my journey could become visible.Not just:“I am interested in cybersecurity.”But:“Here is what I have built.
Here is what I have written.
Here is what I am learning.
Here is OFF_LIMIT TECH.
Here is my work.”I built my portfolio from scratch and worked through the development process, debugging, reviewing, and improving it.On September 20, 2026, I launched it.That was another important moment because the website became more than a website. It became a representation of the journey. My portfolio: https://abdulqayum.netlify.app
ALSO LEARNED THAT BUILDING IS DIFFERENT FROM TALKING
It is easy to say:“I want to build a portfolio.”It is different when you actually have to build one. It is easy to say:“I want to learn cybersecurity.”It is different when you have to sit down and study. It is easy to say:“I want to create technology content.”It is different when you have to research, write, create, edit, publish, and receive feedback.The 100 days helped me move from talking about what I wanted to do toward actually doing some of it.
FREEDBACK
Another thing I started valuing more was feedback.I don't want people to only tell me:“Good job.”I want honest feedback.Tell me what is wrong.Tell me what can be improved.Tell me what doesn't make sense.Tell me where I can do better.Because if I am serious about improving, I need information that helps me improve.Praise feels good.But useful criticism can help you grow.
I DON'T WANT TO RUSH INTO MONEY
Another question I thought about during this journey was money.When should I start making money from technology?Do I need to immediately turn every skill into income?Or should I spend more time building my foundation?I realized that I don't want money to be the only measurement of progress at this stage.I want skills.I want experience.I want projects.I want feedback.I want practical exposure.I want opportunities to contribute and learn from other people. Money matters, but I don't want the pressure to make money immediately to control how I learn.
WHAT I WANT NEXT
Day 100 is not the finish line. It is a checkpoint.The next chapter will be about continuing the foundation I have built.I want to keep developing my cybersecurity knowledge.I want to continue learning Python.I want to keep researching and writing. I want to continue developing OFF_LIMIT TECH.I want to gain practical experience.And one of the directions I want to explore after this 100-day journey is volunteering, where I can contribute, work with people, receive feedback, and gain experience.I also want my portfolio to continue evolving as I gain new experiences and build more projects.
WHAT DID 100 DAYS ACTUALLY CHANGE?
Did 100 days make me an ethical hacker?No.Did 100 days make me an expert in Python?No. Do I know everything about cybersecurity? Definitely not. But that was never the goal.What changed was my approach.I became more comfortable with learning.More comfortable with not knowing.More intentional about my time.More willing to ask questions.More willing to receive feedback.More willing to change a plan when necessary.More interested in building instead of only talking.And more aware of how much there still is to learn.
DAY 1 ABDUL QAYUM VS DAY 100 ABDUL QAYUM
The person who started Day 1 had goals.The person who reached Day 100 still has goals.The difference is that now I have evidence.Evidence that I can commit to something.Evidence that I can keep learning.Evidence that I can build.Evidence that I can document my journey.Evidence that I can adjust when things don't go according to plan.And evidence that I still have a lot to learn.I don't want Day 100 to make me think:“I've arrived.”I want it to make me think:“Now I understand why I need to keep going.”
THE END OF COUNTING, NOT THE END OF THE JOURNEY
There is something I want to make clear about Day 100. Day 100 is the end of counting these 100 days.It is not the end of learning. It is not the end of building. It is not the end of cybersecurity. It is not the end of Python. It is not the end of OFF_LIMIT TECH. It is not the end of my technology journey. It is simply the end of this particular chapter.The counter stops at 100.The journey doesn't.
MY BIGGEST TAKEAWAY
If I had to summarize these 100 days in one lesson, it would be:“You don't need to know exactly where the journey will take you before you take the first step.”On June 18, I didn't know exactly what September 25 would look like.I only knew that I wanted to start.Then the days happened.I learned.I asked questions.I worked.I built.I wrote.I created.I struggled.I adjusted.I reflected.I continued.And eventually, those individual days became 100 days.
MY FINAL TAKE
I started my 100 Days in Tech because I wanted to learn technology.But somewhere along the way, I realized that technology was only one part of the journey.I was also learning discipline.I was learning patience.I was learning consistency.I was learning communication.I was learning how to receive feedback.I was learning how to build.I was learning how to document. And most importantly, I was learning how to continue.100 days didn't make me an expert. It made me more serious about becoming one. It didn't give me all the answers. It gave me better questions. It didn't finish my journey. It gave me a stronger foundation for the next chapter. So if someone asks me:“What did you achieve in 100 days?” I could list the courses .I could list the technologies. I could list the projects.I could list the content .But my real answer is simpler: “
I started as someone who wanted to learn technology, and I finished 100 days as someone who understands that learning technology is a journey I am willing to keep taking.”
Day 100 is the end of counting the days, not the end of the journey.And this is not where the story ends.The journey continues.
Top comments (0)