This is a submission for the 2026 WeCoded Challenge: Echoes of Experience
So it is finally time to write about the past year. It has truly been a roller coaster for me. Last year I quit my job to search for a new one. I am still looking, but the experiences I gained over this year are immeasurable. There is a lot to talk about, so let us begin this journey.
Learning Through Hackathons
After quitting my job, I quickly revised my web development skills and started participating in hackathons to gain more experience. I participated solo because I felt I did not yet have a strong hold on my stack.
I had built a few MERN projects during college, but they were not great. So this felt like a redemption arc for me to improve my skills while participating in hackathons.
Most hackathons are focused on students, so it was difficult to find ones open for working professionals. After a lot of searching I finally found one. The theme was to convert an old website into a modern version.
I chose cplusplus.com since I had been using it and coding in C++ since school. While building it, I faced many errors and struggled with choosing the right libraries and animations to make the website modern but still subtle and usable.
After all the effort I submitted my revised version and received a participation certificate. It felt great to build something and receive recognition for it. I was happy but also a little sad that I did not win.
That made me continue searching for places where I could build and learn more. Eventually I found my go to platform for challenges which was Dev.to.
Reflection
Participating in hackathons taught me that building something imperfect is still better than not building at all. Even though I did not win, the experience helped me understand my stack better and pushed me to keep improving.
Finding My Voice in Writing
When I discovered Dev.to I was amazed by the quality of content and the Dev Challenges on the platform.
Today I also received a badge for completing one year on the platform, so writing this makes me a little emotional while looking back at the journey.
Initially I did not have the courage to publish an article. But after pushing myself I finally wrote my first article. After publishing it I received the Writing Debut badge which made me very happy. Around thirteen people liked the article and that small appreciation made me enjoy writing even more.
After that I started writing more articles for Dev Challenges hoping that someday I might win one.
But my next few articles did not perform well and I began to feel that maybe technical writing was not for me. I did not know whom to ask for guidance, so I took a break from writing and started reading other amazing articles on the platform.
On New Year’s Eve I challenged myself to write thirty articles in thirty days, but again I did not have the courage or ideas to continue.
Then in February the Dev Challenge called New Year New You Portfolio Challenge appeared and I thought this would be the perfect opportunity to start again. I wrote about it and slowly started publishing more articles.
Though I could not complete the challenge, writing gave me more clarity about how to write, what to write, and what works and what does not.
Then something unexpected happened. I wrote the article Vibe Coding Reality Check . I did not expect much from it but it turned out to be a turning point for me. That article made me more serious about writing and sharing my experiences.
Reflection
Writing my first article showed me that sometimes courage is the hardest step. Once I pressed the publish button, everything else became easier. The small appreciation I received gave me the confidence to keep writing and sharing.
Learning to Network at Tech Events
I am an introvert by nature, but I wanted to overcome my hesitation in talking to strangers. Attending tech events alone became one of the best ways for me to learn and network. I lost count of the events I attended because each one taught me something new.
If you have the ability to listen, you can learn from anyone.
At first it was difficult because many people at these events were either students or professionals with great jobs while I was unemployed. That made me feel like a misfit sometimes and I overthought a lot before talking to anyone.
But things slowly changed. In my last few events I realized that I could talk to people, crack jokes, and introduce myself to strangers.
Even today I still feel hesitant at first, but I set a small goal for myself at every event which is to talk to at least one person.
For an introvert like me, this has been a big step forward.
Reflection
Attending tech events helped me realize that networking is not about being the most confident person in the room. It is about being curious and willing to talk to people and learn from their experiences.
Sharing My Work on LinkedIn
Earlier I was not comfortable posting things on LinkedIn. It always felt like boasting about achievements. But once I started learning about personal branding I began to see LinkedIn differently.
My goal is not to boast but to share content that helps people grow. Many people already do this, but I want to find my own way of sharing experiences and learnings.
Posting the articles I write and sharing about events I attend gave me confidence to express my thoughts publicly. It also helps recruiters see that you are building and learning something rather than leaving your profile empty.
And honestly, the first like on a post always feels great.
Reflection
Posting on LinkedIn helped me understand that sharing your journey is not about showing off. It is about documenting your learning and connecting with people who might benefit from it.
Learning by Building Projects
I never thought I would build many projects because I felt new to the tech stack.
But with my existing knowledge and some vibe coding, I built a few projects that I really like. They might not solve big real world problems but I am proud of how they turned out.
Turning an idea into a project takes time, effort, and many errors. For me it was time, effort, and sometimes dealing with hallucinations from AI tools.
More than the projects themselves, I feel proud about writing about them. Writing helps me transform what I learned into words and explain errors, solutions, and outcomes.
Building projects and then writing about them helped me remember problems better and understand solutions more deeply.
Reflection
Building projects reminded me that ideas only become real when you actually start working on them. Every bug and every error teaches something new.
Dealing With Rejections
I applied to many jobs. Some applications were rejected while some progressed to interviews and multiple rounds.
Editing my resume, applying for roles, and getting shortlisted felt exciting. It sometimes felt like waiting for a big opportunity to arrive.
I learned a lot during this phase about job applications, referrals, resume feedback, and interview preparation.
I once had an in person interview which lasted two days. Day one had technical rounds and day two included an interview with the CEO.
Since there were many candidates, my interview was moved to the second day which meant I was the only candidate that day. Instead of overthinking I decided to approach it with confidence.
I went in with the mindset of Veni Vidi Vici. I came, I saw, I conquered.
The conversation lasted around an hour and I left feeling confident. I was hopeful about the result but unfortunately I was not selected.
It was disappointing, but life moves forward. I continued applying and the cycle continued.
Reflection
Rejections were difficult at times, but they also taught me resilience. Every interview helped me understand where I could improve and how to prepare better for the next opportunity.
Learning From the McKinsey Forward Program
Through tech events I came across the McKinsey Forward Program.
It is a multi week learning program designed to equip people at different career stages with practical skills for the future of work. The experience was very different from traditional learning. The program focused on teamwork, sharing ideas, feedback, and practical problem solving.
Many of the concepts were things I already knew, but the program taught me how to apply them in real situations. I still keep my notes from the program and plan to review them before joining a new company someday.
Reflection
The Forward program helped me understand that technical skills alone are not enough. Communication, teamwork, and feedback are equally important in the workplace.
Learning Through Google Arcade
Google Arcade was another interesting experience for me.
It combines learning with a game like environment. I participated from July to December.
Programs like Arcade Adventure, Arcade Voyage, Arcade Trail, Sprint, and Skill Badge give you points for completing learning tasks. The more points you earn the more Google swag you unlock.
Through this program I learned about Terraform, BigQuery, Google Cloud Platform, and several other tools. It made learning cloud technologies feel fun and engaging.
Reflection
Google Arcade showed me that learning can also be fun. When learning feels like a game, it becomes easier to stay curious and keep exploring new technologies.
Looking Ahead
My biggest milestones are still ahead of me.
Getting a job in tech and contributing to open source are the two goals I want to achieve next.
A special thanks to everyone in this community who helped me and made me feel like a part of it. The support and kindness of this developer community has meant a lot to me.
There are also many amazing writers on this platform whose articles helped me learn new things every day like @pascal_cescato_692b7a8a20, @sylwia-lask, @ujja, @francistrdev, @dannwaneri, @hadil, @maame-codes , @the_nortern_dev, @luftietheanonymous, @itsugo and many more. You should definitely check them out.
Over the past year I faced uncertainty, learning curves, rejections, and many small victories. But each experience helped me grow a little more.
This year taught me persistence, curiosity, and the importance of sharing what we learn. Even when progress feels slow, every step still moves you forward.
What is one lesson the tech industry has taught you that changed how you approach your work or learning?
Top comments (47)
Thank you for the mention — and for the company you put me in. Every name on that list is someone I follow and read closely.
That includes you. I read your articles and always find something worth taking away.
What strikes me most in this one is the honesty. A year of uncertainty, rejections, small wins — and you document all of it, without trying to make it look better than it was. That takes more courage than most people realise.
The Veni Vidi Vici mindset going into that CEO interview — that's the right call. You went in, regardless of the outcome.
Keep writing. Keep building. The right opportunity will come.
Thank you so much for you kind words. Your articles always provide me a new perspective to look at tech.
Thank you so much for being so awesome and giving such awesome articles.
Thank you, Konark. That means a lot — especially coming from someone who documents their own journey with as much honesty as you do.
Keep writing. The perspective you bring matters.
Thank you so much Pascal for such an honour. I'm really blessed to have wonderful supporter like you.
You also keep shining and bringing new knowledge to everyone on this platform.
The 2-day interview that ended in rejection and you still left feeling confident. That's the right read of it. The outcome and the performance are separate things. Most people conflate them and come away doubting the wrong thing.
The lesson that changed how I work: shipping something broken in public teaches you faster than building something perfect in private. Every article I've written that flopped told me something the ones that landed didn't. You already know this — the Vibe Coding piece wasn't the one you expected to matter.
Keep going. 👊
Yes, I always believe in giving your best because even if you don't get that opportunity. You will not have the guilt that if I had given my best then I would have gotten that opportunity.
Wow, that is such cool line 'shipping something broken in public teaches you faster than building something perfect in private'. Building in public helps you gather the knowledge or the perspective that you never thought of. Yeah that's something every writer gets after every article that it worked or not and with the reasons. The more you write the more pattern you understand.
Same to you brother. Keep shining and writing such awesome content.
"The more you write the more pattern you understand". That's the thing nobody tells you upfront. You don't get better by writing more carefully. You get better by publishing enough times to see what lands and what doesn't, and eventually you stop being surprised by which is which.
The guilt-free mindset going into that interview is the same principle. You gave what you had. The outcome is separate data.
'That's the thing nobody tells you upfront.' I think people don't tell things upfront at all. They wanna hide their knowledge and skillset that led them to where they are. If you ask how they do it they will say they just did it. So, yeah not by publishing enough times but by publishing what matters. If you and 10 others wrote about same topic then it will be repetition only. Everyone needs to find their voice and their own unique way to represent.
Yeah we should have guilt free mindset. For me, the guilt would be for not writing on this platform. I like to write so I will write on the topics and see how well it is received and work on my way of representing. Like, you also have a way of presenting AI to us in terms of stats and numbers so that the connection is there.
Hey @konark_13! Hope you are well! I am honored that you mentioned me and was honored that my articles helped you! I am glad you are making the progress you are making right now and I can say your post on Interviews does help me (been practicing! :D).
With your question on "What is one lesson the tech industry has taught you that changed how you approach your work or learning?". It basically comes down to the mindset of a Student Vs. Engineer.
When I was working, I noticed that the mindset change since I am not doing tasks as a student where I have to memorize and complete exams, I was shifting towards into thinking as a engineer where it is to accomplish tasks and where there are risks. I am not thinking "course is done", I am thinking of "I fixed a bug where the user does this and that". Overall, it taught me the mindset of an engineer and how it is different when thinking as a student. A student learns while an engineer applies.
Thanks for sharing your journey! Stay tuned for mine this month! Have a lot to talk about and a lot of mentions :D
Great post and hope your journey continues to go well for you!!!
Thank you for such a well thought and meaningful comment it means a lot.
Definitely, the student vs Engineer mindset is a must for everyone now. Like you said we don't have to memorize and complete exams now but rather apply that knowledge in use. Like, how to vibe code and build the idea that is in our mind and transform that idea into an app.
Yeah, can't wait for your journey as well. I am really excited for it and drop it soon kindly. Would love to know how tech helped you.
I’m truly honored to be mentioned among the amazing writers who’ve inspired your journey! 💙 It means a lot that my articles could help you learn and grow. Thank you for including me.
I love how you turned uncertainty into learning, building, and writing. It’s inspiring to see your persistence, curiosity, and courage shine through every step.
Yes, Hadil. Your articles about final round AI and the your questions series are amazing to read. I love to read and save them and re-read them before an interview. You write such awesome content.
Thank you so much hadil for your kind words.
I really felt it when you talked about attending tech events alone. It takes a massive amount of courage to do that, especially when you feel like a 'misfit' in a room where everyone else seems to have their life together. I personally have been doing that for a while this year and I always leave with something beneficial along the way! Seeing your growth through the Google Arcade and how you’ve pushed through those rejections is inspiring. You are clearly carving out your own path. Keep sharing your journey, your story is definitely going to be the lightbulb moment for someone else who feels stuck right now :)
Thanks you so much for your kind words.
I have read your article about attending this Tech Workshop and turning into a Summer Internship. Congrats on that and you wrote an amazing article. It is like you said something beneficial along the way.
I stop expecting from the events and started just attending and enjoying the vibe there and see where it takes me. It is amazing for me to see many 1st year students and working professionals attending it and though I feel bad sometimes for being unemployed but yeah keeping the hope alive.
On a sidenote, I would love to meet you and attend a Tech show with you and learn about you and your story or maybe attend a workshop where you are a speaker. Keep shining and writing amazing articles.
Thanks Konrak! Lots of tech events go on in London just let me know
Konark, I can really relate to the struggle of feeling the need to have it all figured out before sharing your work with others. It's so refreshing to see someone being honest about imperfections and learning from them. Your post really made me think about my own approach to sharing my own work - thanks for mentioning, the encouragement and the reminder that it's okay to start imperfect.
Thank you so much Aryan.
You are a writer with immense knowledge and your articles reflect that. Every word in your articles is well written and well thought. So, thank you so much for inspiring me and many other like me.
Keep writing and building amazing ideas.
Thanks for the mention, Konark❤️
your path to tech kinda reflects mine.
being introverted, skipping participating in hackathon because you thought you are not good enough, have the courage to participate but prefers working solo, later to realize you have to come out of the comfort zone by attending more hackathons, building more projects and most important and hard, networking.
one lesson from my past experience in tech that has helped me is building more projects, ultimately you get this one project that opens doors for you. networking seemed to be hard for me before but now I can just go to someone tell him/her I have this project I would like your thoughts on.
all I can say is being in tech is a continuous learning experience
Yes, Cian you are very right. Tech is a continuous learning experience.
Congrats on overcoming your networking fear. What was you the project that you least expected but turned out to be awesome.
Great article, Konark. You have the right mindset, and it’s just a matter of time until you get your job.
Also, check out Google Summer of Code (GSoC), where you can contribute to open-source projects and still get paid.
Keep posting your content and sharing knowledge with the world.
Thank you so much Raffael for your kind words. I will definitely look into GSoC and see what are the projects I can contribute to.
What is your favorite project to contribute?
I've never participated, tbh, but I was planning on doing this program this year. Unfortunately, I don't have enough time to do it.
Great read. The persistence through hackathons, writing, and rejections really stood out.
I think a lot of developers underestimate how much growth comes from simply building things and sharing them publicly. Even small projects can evolve into something bigger once you start using them.
I’ve been experimenting with building tools myself recently (one of them is a small anomaly-detection tool for spreadsheets called ThresholdIQ), and the learning from actually building something real is very different from just studying concepts.
Thanks for sharing such an honest reflection of the journey.
I'm glad you liked it.
Yes, Todoist is one of the example. It is just a todo app but everyone uses it and it is turned into something bigger now. Same goes for us, what projects we build thinking it is small might solve a problem for someone else.
I would love to try and use ThresholdIQ. Keep breaking and building Vignesh!
Thanks Konark , I would love to hear what you think after trying ThresholdIQ — especially if something feels confusing or doesn't work the way you'd expect. That kind of honest feedback at this stage is worth more than any feature request. Drop me a message anytime. I wish best wishes for you app too.
try it at thresholdiq.app
Some comments may only be visible to logged-in visitors. Sign in to view all comments.