How Beginners Should Think When Learning and Writing About Technology
A beginner-friendly guide to learning and writing about technology by focusing on simple questions, practical examples, and hands-on experience. Learn how to turn technical concepts into clear, useful content that other beginners can easily understand.
When I started learning new technologies, I often thought that learning meant understanding definitions and remembering important terms.
For example, when I first learned about Cloud Computing, I knew terms like IaaS, PaaS, and SaaS. I could explain their definitions, but I didn't really understand why we need them or how they are used in real applications.
Over time, I realized that learning technology is not just about knowing what something is. It is about understanding the problem it solves and seeing how it works in practice.
This also changed the way I think about writing technical articles.
Start With the Questions a Beginner Would Ask
When learning a new technology, I try to start with simple questions:
What is it?
Why do we need it?
How does it work?
Where is it used?
Can I try it myself?
These questions create a simple learning path.
For example, instead of only learning that Amazon EC2 is a virtual server, I can ask:
Why would I need a virtual server?
Then I can learn how to launch an EC2 instance, connect to it using SSH, install a web server, and host a webpage.
The concept becomes much easier to understand when I actually use it.
Don't Learn Technology Only Through Definitions
Definitions are useful, but they should be the starting point rather than the destination.
A beginner can easily memorize:
"Amazon S3 is an object storage service."
But a better learning approach is to ask:
"Why would I need storage in the Cloud?"
Then try uploading an image, storing application files, or using S3 with a real application.
This is where hands-on learning becomes important.
1
2
3
4
5
6
7
8
9
Learn the concept
↓
Understand the purpose
↓
Try it practically
↓
Build something
↓
Explain what you learnedWrite What You Understand
When writing a technical article, I don't think we always need to explain everything about a technology.
As a beginner, it can be more useful to explain one concept that you have actually understood and experienced.
For example:
- What I learned about AWS Cloud
- How I launched my first EC2 instance
- Why IAM is needed
- How I understood S3
- How I connected an application to RDS
This makes the article more practical and relatable.
Write for the Person You Were Yesterday
This is one of the biggest things I have learned.
When I write an article, I try to imagine myself at the beginning of my learning journey.
What question did I have?
What confused me?
What explanation helped me?
What did I wish someone had told me earlier?
These questions can help create useful content for other beginners.
Instead of trying to make an article sound highly technical, I can explain the concept in the simplest way I understand it.
Use Simple Examples
Technical concepts become easier when they are connected to familiar situations.
For example, IAM can be explained through a company where developers, testers, and database administrators need different levels of AWS access.
Similarly, EC2 can be explained as creating a virtual server that we can configure and use to run an application.
Simple examples help connect theory with real-world use cases.
Don't Be Afraid to Say "I Learned This"
A technical article doesn't always have to sound like documentation written by an expert.
If you are learning AWS as a beginner, you can share:
"This is how I understood it."
That makes the article more personal and honest.
It also allows other beginners to follow the same learning path.
My Simple Approach to Learning and Writing
Today, I try to follow a simple process when learning a new technology:
1
2
3
4
5
6
7
8
9
10
11
12
13
Question
↓
Concept
↓
Purpose
↓
Hands-on Practice
↓
Small Project
↓
My Understanding
↓
ArticleThe article then becomes a reflection of the learning process rather than just a collection of definitions.
Final Thoughts
I am still learning technologies such as AWS Cloud, Cloud Computing, and GenAI, so I don't consider myself an expert.
But I have learned that being a beginner can actually help when writing beginner-friendly technical content.
We know what it feels like to be confused by a new concept.
So instead of trying to explain everything, we can focus on one question at a time:
What is it? Why do we need it? How does it work? And how can I try it myself?
For me, that is a better way to learn technology, build projects, and share knowledge with other beginners.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article