I recently applied for the December cohort of the Outreachy internship program, hoping to move one step closer to my goal of becoming a better software developer. Unfortunately, my initial application wasn't approved.
This isn't the first time I've experienced this, so I won't pretend that it doesn't hurt. Every time I apply for an opportunity like this, I hope things will turn out differently. When they don't, it's natural to question yourself, your progress, and whether you're doing enough.
But I'm learning that a setback doesn't have to be the end of the story.
Looking beyond the disappointment
One thing my journey so far has taught me is that becoming a software developer involves more than getting an internship or having an application accepted. It also means continuing to learn, building practical skills, contributing to projects, and becoming comfortable with the fact that there is always more to understand.
I've been exploring open source and working to improve my development skills. Although I still have a lot to learn, I don't want my progress to depend entirely on whether a particular application succeeds.I want to keep building.
My next step: AWS and cloud computing
I've decided to start learning AWS and cloud computing.
I've used technologies to build and deploy projects, but I want to understand more about what happens behind the scenes. How are applications hosted? How do servers work? How do developers deploy applications so that people can access them over the internet? How do cloud services help applications scale?
These are some of the questions I want to explore.
I'm starting from the fundamentals, and I know it won't happen overnight. My plan is to learn the basics, practise with hands-on projects, document what I discover, and gradually build a better understanding of cloud technologies.I'm also interested in working toward an AWS certification when I have built a solid foundation.
I don't want to rush through tutorials just to say I've completed a course. I want to understand what I'm learning and be able to apply it.
Documenting the journey
This article is the beginning of that journey.
I'll share the resources I use, the concepts I learn, the mistakes I make, and the small projects I build along the way. I expect to encounter confusing topics and make mistakes, but I hope documenting the process will help me learn more deliberately.
If you're also learning to code, trying to break into tech, or dealing with a setback of your own, I hope we can learn from each other.
I may not have received the outcome I wanted from Outreachy this time, but I still have the opportunity to work on myself and develop new skills.
One application outcome doesn't define my entire journey as a developer.
For now, I'm taking the next step: learning AWS, exploring cloud computing, and continuing to grow.
Let's see where this journey takes me.
Top comments (1)
"This isn't the first time I've experienced this, so I won't pretend that it doesn't hurt." Respect for saying that out loud. Most people skip that part. When rejections stack up, your brain's filter (it's called the RAS) starts treating each one as proof. It quietly pulls up every reason you're not doing enough and hides the stuff you actually did. That's why you end up questioning yourself even when the facts don't back it up. You applied more than once. That takes something a lot of people never put on the line.
Documenting the AWS work in public is a great move, because every post is new data for that filter. One thing I'd add: give it data away from the screen too. Say something genuine to a stranger, a compliment is easiest. Once that feels easy, add a bit of conversation. How it lands doesn't matter. Doing it is the win. Good luck with the cert.