One of the things I love most about the tech community is that there isn't a single path to becoming a developer.
Some people wrote their first lines of code when they were 10 years old. Others discovered programming in college. Some switched careers after years in a completely different field. Many are self-taught, learning through documentation, open-source projects, YouTube videos, blogs, and countless hours of trial and error.
And that's exactly what makes this community so special.
Behind every GitHub repository, every app, every website, every open-source contribution, and every successful developer is a story filled with curiosity, mistakes, late nights, debugging sessions, self-doubt, small victories, and continuous learning.
We often see the finished product but rarely hear about the journey that made it possible.
That's why I wanted to ask the community a few questions.
I'd genuinely love to hear your story.
How did your tech journey begin?
Was there a particular moment that sparked your interest in technology? Did someone inspire you? Was it a school project, a YouTube tutorial, a book, a game, or simple curiosity?
What was your biggest challenge when you started?
Was it understanding programming concepts? Learning mathematics? Finding good resources? Balancing work or studies? Staying motivated after repeated failures?
What kept you going?
Every developer reaches moments where giving up seems easier than continuing. What helped you push through those difficult phases?
What are you learning today?
Technology evolves incredibly fast. Are you exploring AI, cybersecurity, cloud computing, web development, mobile apps, DevOps, data science, game development, or something completely different?
If you could go back and talk to your beginner self, what advice would you give?
I think this question alone could help hundreds of people who are just starting their own journey.
Why I'm Asking
I believe the most valuable lessons in tech don't always come from courses or documentation.
Sometimes they come from real people sharing honest experiencesโwhat worked, what didn't, what they wish they had known earlier, and how they overcame obstacles.
A beginner reading your story today might find the motivation they need to keep going tomorrow.
So whether you've been in tech for 20 years or you're writing your very first "Hello, World!", your experience matters.
There are no small stories.
Every journey has something worth learning from.
I'm looking forward to reading your experiences, lessons, failures, breakthroughs, and advice in the comments. Let's make this a collection of stories that inspires the next generation of developers.
Top comments (60)
Hey, this article appears to have been generated with the assistance of ChatGPT or possibly some other AI tool.
We allow our community members to use AI assistance when writing articles as long as they abide by our guidelines. Please review the guidelines and edit your post to add a disclaimer.
Failure to follow these guidelines could result in DEV admin lowering the score of your post, making it less visible to the rest of the community. Or, if upon review we find this post to be particularly harmful, we may decide to unpublish it completely.
We hope you understand and take care to follow our guidelines going forward!
It's urgent. Can I have talk with you?
Yes!
Can I have your microsoft teams id? or whatsapp number?
There is a guy who suggested me to do some AI stuffs for side income so that i can fix my 0 budget problem and invest it in akhouri systems.
Sorry, Anmol, but this is against the privacy policy.
Ok. Is there any platform where we can chat privately or in dev.to is there is any private chat option? It's important.
Please let me know what you want to discuss with me.
There is a guy, he is very expert in AI field, probably from mexico(because he has degree from mexico in AI automation stuffs), he gave a doc file, and a suggestion in which I have to create AI training accounts and rent it to developers and from that rent revenue I can invest in my akhouri systems and solve my 0 budget kid problem. I have less expertise in that field so I felt you can make me understand is it good or not. He gave me invite in microsoft teams, then he chatted with me and gave these suggestions, if you want to see his profile check my activities I have talked with him a little bit in dev.to
If you are okay then give me your whatsapp number, or if you use microsoft teams then invite me there.
His profile name-Luis
Please tell me what you want to do for your app.
not for app just a suggestion or guidance what should i do? he says he will take my laptop access through anydesk. what should i do?
I am confused. I have to share you the doc file he gave me how can i do that?
I don't use any online platform where I could talk to you.
ok then leave it. I will it figure it out myself.
I can hide your comment, so it will be visible only to the two of us.
Giving someone access through AnyDesk is more than just sharing your screen. Once you grant remote control, they may be able to access your files, install or remove software, change settings, and potentially view accounts that are already signed in.
That's why you should be very cautious if someone asks for remote access to create AI trainer accounts or any personal accounts. Those accounts are linked to your identity, so it's much safer to create and manage them yourself.
If someone genuinely wants to help, they can guide you step by step over chat or a call while you perform the actions on your own computer. They don't need remote control to explain the process.
For that reason, unless you completely trust the person and clearly understand why remote access is necessary, it's generally not a good idea to give anyone control of your PC through AnyDesk or similar software.
Yeah I knew it. I was just cross checking it. Thanks so, I will deny right?
The AI training platforms themselves (such as Alignerr and Mindrift) are legitimate, but I'd be careful about the account-rental idea.
If the accounts are created in your name and then used by other developers, that may violate the platform's terms and could result in suspension or a permanent ban. I would strongly recommend checking each platform's Terms of Service before considering anything like that.
Also, be cautious if someone asks for remote access to your computer through AnyDesk or requests your login credentials. If they're genuinely trying to help, they should be able to guide you while you create and manage the accounts yourself.
If your goal is to earn money to support Akhouri Systems, a safer approach would be to create the accounts yourself, complete the verification yourself, and work on the projects yourself instead of renting the accounts.
Before making any decision, ask him to clearly explain how the account-rental model works, whether the platforms explicitly allow it, and what happens if an account is suspended. If he can't answer those questions with evidence, I'd avoid the arrangement.
Thanks for sharing ๐๐ป
So, now can you explain me. in a easy tone?
Yes, Iโll explain it to youโjust give me a little time. Iโm heading to China for work right now, so Iโll let you know on Monday.
OK, for sure.
safe journey. in xi jingping's land. ๐ฅ
Thank you โค๏ธ
Can you explain now?
Did you talk to him?
I said him that I will talk my mentor and then reply him by today.
I checked the offer. The AI training platforms part looks interesting, but I would suggest being careful before investing time or money. First verify that the platforms are genuine, check their terms and conditions, and confirm whether account sharing or renting is actually allowed.
If the idea is about creating your own AI skills and working on these platforms, it can be a good opportunity. But if it is about renting personal accounts to others, I would be cautious because it may create security, policy, and account suspension risks.
My suggestion would be to start small, test the platform yourself, and only continue if everything is verified and transparent.
If you want to know more about this, let me tell you that xulingfeng would be aware of it; you could ask him as well.
how you know about xulingfeng?
You also know mustafa
are they your freinds?
and yea I am planning to have a meeting with that guy for explanation
Yes
My Journey
As a 2002 kid, my world was filled with: spiderman, ironman, power rangers, kiteretsu, doraemon,ninja hattori!
All of them had something in common, science!
I wanted to become a scientist like kiteretsu!
Waiting for school bell to ring and going home as fast as I can!
Trying to build cardboard armour of iron man, sling shot web shooter of spiderman.
Playing with my cousins.Those were the days!
After getting into high school, took science seriously and later did 10+2 with Maths Physics Chemistry.
Then came a gap, some health issues and then came the pandemic!
At that point as I said before in fear of math took some time and then officially started BCA!
Goals
My initial goal was to be an astronomer!
Current goal: to be a computer scientist!
I like science and am kind of lazy person who wants to be sitting in his room with just a computer and do all the things, so I thought of astronomy and later programming as the right thing!
Advice to myself
Just believe in the flow and jump into the ocean!
Working on my habit of quitting easily!
@technogamerz
I love this idea of telling everyone about their story!
Thank you for this post!
And I really want to thank you for reading my posts and your support!
โบ๏ธ
Hey!! Hope you are doing well โค๏ธ
Your journey proves that life can give you gaps and obstacles, but what matters is where you are heading next. The transition from wanting to be an astronomer to a computer scientist makes perfect senseโboth fields require a deep curiosity about how things work.
Acknowledging the habit of giving up easily is the first step to beating it. Coding will test your patience, but the satisfaction of seeing your logic work is worth every failed attempt.
Please don't thank me at all! To borrow what @xulingfeng said, we are all here to support each other, and I'm just doing my part to back up a fellow developer.
You've got a fantastic mindset. Trust the flow, keep experimenting, and all the best for your future goals! ๐ฅ๐
Love seeing this โ that's exactly what I meant when I said it. Passing it forward is the whole point. You're doing great work here, Divyanshi ๐
Also I feel like one of those motivational quote posters hanging in a school hallway right now ๐ Gotta stay humble. Gotta stay grounded๐คฃ
๐ ๐ฏ ๐โจ
1. How did your tech journey begin?
My parents got me my first computer but skipped the antivirus. From then on, every time something broke, I had to figure it out myself.
2. What was your biggest challenge when you started?
Staying away from the screen. I was hooked โ late nights, every single night. Still am, kinda ๐
3. What kept you going?
Mentors and friends who had my back. Especially the test manager at my second company โ she's the reason I got to build my first real test automation platform, one that ran the entire project.
4. What are you learning today?
Sneaking in some writing between the chaos. Might just switch careers and become a writer ๐
5. If you could go back and talk to your beginner self, what advice would you give?
The world's bigger than your screen. Go see it. You're not as alone as you think.
This is honestly such a beautiful and inspiring tech journey!!! โค๏ธ
I absolutely love how your story startedโgetting a computer without an antivirus and having to fix everything yourself. They say challenges shape the best engineers, and you are the living proof of that! ๐ฅ๏ธโจ
That addiction to the screen and those countless late nights is a phase every passionate developer knows too well, but the way you turned that obsession into building something as massive as a core test automation platform is incredible. Itโs also so heartwarming to see how much you value your mentors and the people who backed you up early in your career. That gratitude shows exactly what kind of a person and professional you are.
And please, keep sneaking in that time to write! Your bio says you write about the 'systems behind the systems and the 3 AM calls,' and honestly, you already have the voice of a storyteller. If you ever decide to make that career switch to becoming a full-time writer, just know that Iโll be the very first person to buy your book! ๐โ๏ธ
Your advice to your beginner self absolutely hit home. That is a profound piece of wisdom not just for coding, but for life itself.
I am incredibly proud to call someone as talented, humble, and brilliant as you a close friend. Keep shining, keep writing, and keep breaking boundaries. Always rooted for you! ๐๐ฅโ
Divyanshi, this reply genuinely caught me off guard. I was just sharing my story like everyone else โ didn't expect to get a whole essay back โค๏ธ The way you connected the "no antivirus" start to "challenges shape the best engineers" was something I hadn't even thought about myself.
And "I'll be the first to buy your book" โ that line hit. Might just be the push I needed to actually sit down and write one ๐
Thank you for reading that carefully and for being this kind of person in the community. Means more than you know.
How did your tech journey begin?
I was always a gamer. I spent many, many hours sitting in front of a PC playing games, so at first I wanted to become a game developer.
But to be a game dev, you really have to be dedicated to it. And letโs be honest, not all game developers make the same money as developers in general. So I ended up as a boring corporate senior dev instead. ๐
What was your biggest challenge when you started?
I think the struggle and challenge never really ended. ๐ But at the beginning, syntax was probably my biggest struggle.
What kept you going?
Curiosity and the motivation that came from finishing side projects.
What are you learning today?
Iโm experimenting with AI and all the new tools that come with it.
If you could go back and talk to your beginner self, what advice would you give?
Donโt be angry with yourself when you are not able to learn something in a few minutes that others spent months learning. ๐
Haha, thanks for sharing your journey, Daniel! I absolutely love your honesty. I can totally relate to the gamer mindsetโhonestly, I still end up losing at least 2 hours every single day just playing GTA and Call of Duty! ๐ฎ So I completely get how that passion draws you into tech.
Going from wanting to be a game dev to becoming a senior backend dev is such a solid transition. There is absolutely nothing boring about being a senior dev who solves performance and architecture puzzles!
Also, the advice you'd give to your beginner self is pure gold. Itโs so easy to get frustrated when you don't grasp something immediately, forgetting that others spent months mastering it. Patience is definitely the hardest syntax to learn. Good luck with your AI experiments, and thanks for adding so much value to this discussion!โค๏ธ
Hey Divyanshi ๐
My journey has been a lot of learning by building (and breaking ๐). Every small project taught me something new.
If I could tell my beginner self one thing, it'd be to document the journey earlier. It's amazing how much you forget until you write it down.
Still learning every day, and I wouldn't have it any other way.
Sorry for the late reply! And thank you so much : D for sharing your journey.
I really liked what you said about documenting your learning early. It's such a simple piece of advice, but I can already see how valuable it is. The "building (and breaking)" part made me smile because that's honestly how most of us learn. Wishing you many more exciting projects and lessons ahead!
Thank you for sharing such a wonderful article, Divyanshi๐โจ
Iโve just started my own tech journey here on DEV, and Iโve been able to keep working on iOS development โ something I had wanted to try for years but couldnโt quite start๐ฆ.
Although I work in IT, Iโm not a developer, so I donโt really have mentors or people around me who can guide me in development.
Thatโs why writing articles about what I learn and knowing that someone might read them definitely helps keep me motivatedโค๏ธโ๐ฅ.
And congratulations on reaching 2K followers! ๐
Hey Umitomo hope you are doing well โค๏ธ
Thanks for sharing your journey!!
My tech journey honestly started with curiosity.
I did not enter tech through some grand master plan. It started with Linux.
At first, Linux felt like this strange world where everything looked powerful, but nothing explained itself politely. I remember experimenting with Ubuntu, Fedora, Arch, and different desktop environments just because I wanted to understand how things worked under the hood.
The spark was simple: I wanted control over my own machine.
Windows worked, sure, but Linux made me curious. It made me ask questions like:
Why does this command work?
Why did this break?
What is a package manager?
Why did I just destroy my bootloader at 2 AM?
That curiosity slowly became an obsession.
My biggest challenge in the beginning was not programming itself. It was understanding the ecosystem. Terminals, permissions, filesystems, drivers, repositories, logs, documentation, forums, kernel updates, display servers, window managers, all of it felt overwhelming.
And yes, I broke things. A lot.
There were failed installs, broken desktops, missing Wi-Fi drivers, boot issues, weird errors, and many moments where reinstalling the OS felt like a personality trait.
But that is also what kept me going.
Every time I broke something and fixed it, I understood a little more. Every error message became less scary. Every forum post, man page, GitLab issue, and random late-night experiment taught me something.
Linux taught me patience.
It taught me that troubleshooting is not magic. It is pattern recognition, curiosity, and refusing to panic when the screen goes black.
Over time, that interest grew into open-source involvement, Fedora testing, experimenting with different distributions, learning how systems behave, and eventually building confidence in tech support, IT operations, and software projects.
Today, I am still learning.
I am exploring Linux more deeply, working on my own programming projects, understanding system design better, improving my Git workflow, and slowly building toward stronger skills in software, cloud, automation, and open-source development.
The best part is that I still feel like a student. Technology changes too fast for anyone to act like they know everything. The moment you think you are done learning, the industry politely throws a new tool, framework, or error log at your face.
If I could go back and talk to my beginner self, I would say this:
Do not be afraid of breaking things.
Break the system, but learn why it broke.
Read documentation, even when it feels boring.
Ask questions, even when they feel basic.
Do not compare your journey with someone who started earlier.
And most importantly, build things. Small things. Ugly things. Half-working things. Real learning happens when you stop only watching tutorials and actually try to make something yourself.
Linux did not just teach me technology.
It taught me how to think, how to troubleshoot, how to stay curious, and how to keep going even when nothing works the first time.
And honestly, that is still the most valuable skill I carry today.
@technogamerz
My journey started with curiosity, not a roadmap.
More than 20 years ago, I was the person who wanted to know how everything worked. If something broke, I didnโt just want to fix itโI wanted to understand why it broke.
Over the years, that curiosity led me through networking, Linux, system architecture, ERP systems, virtualization, cloud technologies, DevOps, cybersecurity, and now AI.
The biggest challenge wasnโt learning a programming language. It was learning that technology never stops changing. Just when you think youโve mastered something, thereโs another wave to ride.
What kept me going was building real systems. Every production issue, every outage, every bug became another lesson. Success teaches you confidence; failures teach you architecture.
Today Iโm spending a lot of time exploring AIโnot because itโs the latest trend, but because I believe understanding how to work with AI will become as important as learning programming itself.
If I could give my younger self one piece of advice, it would be this:
Donโt chase technologies. Chase fundamentals. Languages, frameworks, and tools come and go, but understanding systems, networking, databases, and problem-solving will always pay off.
And never stop building. Real projects teach lessons that no course ever can.
Hey Mustafa hope you are doing well!! โค๏ธ
Wow, thank you so much for sharing this! Your story is incredibly inspiring, and honestly, itโs exactly what I needed to hear. That lineโโSuccess teaches you confidence; failures teach you architectureโโis just pure gold. It shifts the whole perspective on running into bugs and production issues!
Your advice about chasing fundamentals instead of just jumping from one trending framework to another makes total sense. Tools change so fast, but core logic and system design stay. Also, itโs amazing how youโre still driven by that same curiosity after 20+ years, now diving into AI. Thanks for passing down this incredible wisdom to the rest of us. Keep building, and keep inspiring! ๐โจ
I'm still early in my tech journey, but one lesson that's already made a big difference is not being discouraged by difficult topics.
There have been concepts that seemed impossible at first, but breaking them down and practicing consistently eventually made them click. Looking back, I'd tell my beginner self to trust the learning process.
Hey!! Hope you are doing well โค๏ธ
Such a wise takeaway, especially for being early in your journey! Trusting the learning process saves so much anxiety. Thank you for this beautiful reminder, you're going to do amazing things!
I appreciate your kind words.
Some comments may only be visible to logged-in visitors. Sign in to view all comments. Some comments have been hidden by the post's author - find out more