DEV Community 新作者 Arhum Usman 分享其科技探索與寫作起點
Hello, DEV Community! I'm Arhum, and This Is Where My Journey Begins 👋
Arhum Usman 是來自巴基斯坦、就讀 NUML 的電腦科學學生,首次在 DEV Community 寫作,分享自己探索網絡安全、人工智能與軟件工程的經歷。他取得 EC-Council 的 CHFI 認證,參與 Verisight Shield 等項目及多場黑客松,並希望記錄學習過程、心得與錯誤。
Hello, DEV Community! I'm Arhum Usman, and This Is Where My Journey Begins 👋
Exploring cybersecurity, artificial intelligence, software engineering, and everything in between.
Hello, DEV Community!
I'm Arhum Usman, a Computer Science student from Pakistan, currently pursuing my bachelor's degree at the National University of Modern Languages (NUML).
I've been exploring the world of technology for quite some time, but this is my first time writing here.
Honestly, I spent a while thinking about what my first article should be. A technical tutorial? A project breakdown? Something about cybersecurity or AI?
Then I realized that before sharing what I know, it would make sense to introduce myself, talk a little about my journey, and explain what brought me here.
So, here we go.
A Little About Me
My interest in technology has always been driven by curiosity.
I've never been satisfied with simply knowing that something works. I want to understand how it works, why it works, and what happens when it doesn't.
That curiosity gradually led me toward different areas of computer science, particularly cybersecurity, artificial intelligence, and software development.
What I find interesting is how closely these fields are connected.
Software engineering teaches us how to build systems. Cybersecurity teaches us how to protect them. Artificial intelligence introduces new ways to make those systems more capable.
And somewhere at the intersection of these fields is where I enjoy working the most.
I'm still learning, experimenting, and figuring things out, but that's what makes the journey worthwhile.
How I Got Into Cybersecurity
Cybersecurity was one of the first areas that genuinely changed how I looked at technology.
Before getting into security, I mostly thought about systems from a development perspective: how applications are designed, how different components communicate, and how everything comes together.
Cybersecurity introduced another perspective.
What if an application behaves differently from what its developer intended?
What happens when someone finds a weakness in a system?
How do security teams identify suspicious activity, investigate incidents, and respond before things get worse?
These questions led me toward defensive security, security operations, network analysis, and digital forensics.
Over time, I've had opportunities to explore security tools, participate in practical labs, complete professional training, and gain exposure through internships.
One of my personal milestones was earning the Computer Hacking Forensic Investigator (CHFI) certification from EC-Council.
It was an encouraging achievement, but it also reinforced something I've come to believe:
A certification is a milestone in learning, not the finish line.
There's a difference between understanding a concept and being able to apply it when you're facing an unfamiliar problem.
That's why hands-on learning remains an important part of my journey.
Exploring Artificial Intelligence and Software Engineering
As I continued studying computer science, my interests expanded beyond cybersecurity.
Artificial intelligence caught my attention, particularly the possibility of using intelligent systems to solve practical problems.
I became interested in how machine learning models work, how they can be integrated into applications, and how their outputs can support real decisions.
One project I've worked on is Verisight Shield, an AI-powered image authenticity and digital forensics project.
The idea was to explore how different forensic techniques and machine learning approaches could help investigate potentially manipulated or AI-generated images.
Working on projects like this has taught me that developing an AI application involves much more than connecting a model to an interface.
You have to think about the problem itself, the quality of the data, the limitations of the model, system design, usability, and how results are communicated.
I've also become increasingly interested in software architecture, backend development, APIs, and building applications that are reliable and maintainable.
The more I learn, the more I realize how important it is to understand the fundamentals behind the tools we use.
What Hackathons Have Taught Me
Another important part of my journey has been participating in hackathons.
I've been fortunate to experience some memorable moments, including winning 1st position at the NUMFEST 2025 Hackathon and securing 3rd position at the GDGoC FAST-NUCES AI Hackathon 2026 with Team NightFury and our project, FounderOS.
Of course, winning feels great.
But looking back, the biggest value came from the experience itself.
Hackathons put you in situations where you have limited time, incomplete information, unexpected problems, and a team depending on you.
You quickly learn that having a good idea isn't enough.
You need to understand the problem, make technical decisions, divide responsibilities, write working code, handle failures, and communicate what you've built.
And sometimes, despite all your planning, something breaks just before the demonstration.
That's part of the experience too.
These competitions have helped me become more comfortable with problem-solving, collaboration, and working under pressure.
They've also reminded me that some of the most useful lessons come from things that don't go according to plan.
Why I Decided to Start Writing
For a long time, most of my learning remained somewhere between my laptop, notes, GitHub repositories, and unfinished experiments.
I'd complete a lab, solve a problem, explore a new technology, or build something interesting, then move on to the next challenge.
But recently, I've been thinking more about documenting what I learn.
Not just the successful results, but the process behind them.
The decisions that worked. The mistakes I made. The concepts that took time to understand. And the things I would approach differently if I had to start again.
I believe technical writing is one of the best ways to improve your own understanding.
When you try to explain something clearly, you often discover the gaps in your knowledge.
And when you share that explanation publicly, someone else might benefit from it, question your approach, or introduce you to an entirely different perspective.
That's what attracted me to DEV.to.
I'm not here to present myself as someone who has mastered everything.
I'm here to share what I'm learning, contribute where I can, and learn from people who have different experiences and perspectives.
What I'll Be Writing About
My interests are fairly broad, but most of my articles will focus on a few areas.
Cybersecurity and Digital Forensics
I'll share practical security concepts, defensive security techniques, network analysis, incident investigation, security tools, and lessons from hands-on labs.
Artificial Intelligence and Machine Learning
I'll explore AI concepts, model integration, intelligent applications, and the practical challenges involved in building AI-powered systems.
Software Development and System Design
I'll write about programming, backend development, APIs, architecture, debugging, and lessons learned while developing projects.
Hackathons and Project Development
I'll share the process behind some of the projects I've worked on, including the problems we tried to solve, technologies we used, engineering decisions we made, and challenges we encountered.
And occasionally, I'll write about my experiences as a Computer Science student trying to grow in an industry that never stops evolving.
I want these articles to be useful, honest, and based on things I've actually explored or worked on.
One Thing I've Learned So Far
If there's one lesson that has stayed with me throughout my journey, it's that you don't have to understand everything before you begin.
I've started projects without knowing exactly how I would finish them.
I've encountered errors that took hours to resolve.
I've spent time learning technologies that initially seemed far beyond my understanding.
And I've realized that this is a normal part of becoming better at what you do.
There will always be another framework, programming language, security vulnerability, research paper, or AI model to explore.
It's impossible to keep up with everything.
But you can keep improving your fundamentals, stay curious, and become better at approaching unfamiliar problems.
For me, that's what continuous learning really means.
Not knowing everything, but developing the confidence to learn what you need.
Looking Forward
I'm excited to finally become part of the DEV Community.
I hope this space becomes a place where I can document my work, exchange ideas, learn from experienced developers, and connect with people who share a genuine interest in technology.
I'll be sharing technical articles, project breakdowns, experiments, and lessons from my journey through cybersecurity, AI, and software engineering.
Some articles will be detailed and technical. Others will focus on practical experiences and things I've learned along the way.
Either way, I'll do my best to make them worth reading.
If you've made it this far, thank you for taking the time to read my first post.
I'm looking forward to being part of the conversations happening here.
Before you go, I'd love to ask you something:
What's one project, experience, or technical challenge that taught you more than any course or tutorial ever could?
I'd genuinely love to hear about it.
Until next time, happy building!
Arhum Usman
Computer Science Student | Cybersecurity & AI Enthusiast | Software Developer
GitHub: github.com/ArhumUsman9
Always learning, always experimenting, and always looking for the next problem worth solving.
來源:DEV Community · dev.to