ο»Ώ
Getting 10 Likes on Your Comments
At first, it sounds easy.
βJust write a good comment and get 10 people to like it.β
In reality, getting meaningful engagement on a comment is much harder than simply leaving a comment.
You need to contribute something that people actually find useful.
Why is this challenge so difficult?
AWS has a huge community, and there are already thousands of discussions happening.
A short comment like:
βGreat article! Thanks for sharing.β
probably isn't going to create much engagement.
Instead, you need to add something valuable to the conversation.
For example, if someone writes about AWS Lambda, you could share a practical experience, explain a concept they missed, or ask a thoughtful follow-up question.
The goal shouldn't be:
βHow do I get 10 likes?β
It should be:
βHow can I write a comment that deserves 10 likes?β
That's a completely different mindset.
My Strategy for the 21-Badge Challenge
If you're trying to complete all 21 badges, I think the best approach is to treat AWS Builder Center like a real community rather than a checklist.
1. Comment consistently
Don't wait for the perfect discussion.
Find AWS topics you're actually interested in and participate regularly.
A few useful comments every week can be much more effective than leaving dozens of generic comments.
2. Add something new
When commenting, try to include at least one of these:
- A useful AWS service or feature
- A question that continues the discussion
- Something you learned from your own experience
That's what turns a comment into a contribution.
3. Write articles
Publishing articles is another great way to participate in the AWS community.
You don't need to write a 5,000-word technical tutorial.
A focused article explaining something you recently learned can be valuable.
For example:
β5 Things I Learned While Learning AWS Lambdaβ
can be more useful than trying to write an extremely complicated AWS architecture guide.
4. Don't obsess over the badge
This might sound strange in an article about collecting badges, but it's probably the most important point.
Badges are a nice way to show participation.
But the knowledge you gain while earning them is much more valuable.
If you're learning AWS Cloud Practitioner concepts, experimenting with Lambda, exploring S3, or studying for Solutions Architect, document that journey.
The badges will follow naturally.
The Final Badge Feels Different
When you already have 20 badges, getting the final one can feel frustrating.
You've completed almost everything.
You've written articles.
You've participated in discussions.
You've built your profile.
You've completed the required activities.
And then you're staring at that one remaining requirement:
10 likes on a comment.
That's when you realize that this isn't really a technical AWS challenge.
It's a community challenge.
You can't simply click a button and finish it.
You have to create something that other people genuinely want to engage with.
What I've Learned
The biggest lesson from chasing AWS Builder badges is that consistency beats intensity.
You don't have to spend hours every day.
Instead:
Learn β Share β Comment β Help β Repeat
Over time, your profile becomes a record of your AWS journey.
And eventually, that difficult 21st badge becomes just another milestone.
Are you also trying to complete all 21 AWS Builder badges?
Which badge has been the hardest for you?
And if you've already completed the 10-likes-on-a-comment challenge, what kind of comment did you write?
I'd love to hear your strategy. π
Loading article