AWS Builder Center
Welcome to AWS Builder Center: Why I Decided to Start Writing Instead of Just "Lurking"

Welcome to AWS Builder Center: Why I Decided to Start Writing Instead of Just "Lurking"

Why I stopped just "lurking" on tech blogs and started writing about my cloud learning journey on AWS Builder Center as a Computer Science student.

If you're studying Computer Science or dipping your toes into the cloud, your browser probably looks a lot like mine: dozens of tabs open with official docs, Stack Overflow threads, Medium guides, and random tech blogs.
For a long time, I was purely a consumer of all that content. As a CS student trying to keep up with classes, projects, and new technologies, I was the classic "lurker." I’d search for an error message, grab the solution, patch my code, and move on to the next assignment without giving it much thought.
So why am I here on AWS Builder Center writing my very first post instead of staying quietly in the background? A few things made me want to change my approach.



1. Realizing "Understanding" and "Just Reading" Are Different Things

During lectures or while reading tutorials, it’s easy to feel like everything makes total sense. But whenever I tried to rebuild something from scratch or explain a cloud concept to a classmate, I’d suddenly hit a wall.
Writing things down forces me to slow down. When I sit down to draft a post about how I set up a project or configured an AWS service, I quickly spot the gaps in my own understanding. It pushes me to double-check my facts, re-read the docs, and actually solidify what I’m learning.



2. My Local Notes Were Getting Out of Hand

Like most CS students, I have folders full of random text files, quick terminal commands, and half-finished notes from my coursework and side projects. But let’s be honest—those local files usually turn into a graveyard of forgotten information.
I figured that if I’m already writing down notes while figuring out AWS services, lab exercises, or project setups, I might as well polish them a bit and share them publicly:
  • For me: It gives me a clean, organized log of my own learning path.
  • For others: If another student or beginner runs into the exact same error I spent hours debugging, maybe this post will save them a bit of time.



3. Connecting with Other Builders

Computer Science is vast, and the AWS ecosystem moves fast. Trying to learn everything in a silo feels overwhelming.
Putting my learning process out there is a way to invite feedback. I don't have years of industry experience yet, and I'm definitely going to make mistakes or miss cleaner ways of doing things. Sharing my approach opens up the chance for others to say, "Hey, nice effort! Have you tried doing it this way instead?"—which is one of the best ways to grow.



What I’m Planning to Share

I’m not here to write authoritative guides or act like an expert. I’m simply a student navigating the world of software development and cloud technology.
Here is what you can expect from my posts:
  • Coursework & Labs: Honest notes and breakdowns of what I learn through my classes, cloud learning paths, and hands-on lab practice.
  • Student Projects: Walkthroughs of side projects—including the bugs I ran into and how I worked through them.
  • Concept Breakdowns: Simple summaries of cloud and CS concepts as I try to wrap my head around them.


If you’ve also been on the fence about sharing your own study notes or project logs, maybe give it a shot too.
Thanks for reading, and happy building!
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article