I generally don't post "opinions" on the internet, but this thought provoking tweet by Ashley McNamara did trigger... well, a bunch of thoughts!
Someone told me that their content doesn’t get respect because it’s beginner content.
Do you know how deep your expertise has to be to create great content for a beginner audience? It takes true skill and empathy — I’ll fight anyone who shits on beginner content.02:29 AM - 19 Jun 2020
Also, this topic of "Content" (developer facing tech content in my specific case) is quite relevant for someone like me who has been doing this (mostly in form of blogs and sometimes short e-books) long before it was my day job.
So here it goes....
Please, don't underestimate or downplay beginner content...
Let's not forget that we were all beginners once and "getting started" content is as important as anything else. Think of the audience: a potential customer experimenting with your product, a developer trying to use your API, a potential maintainer trying to wrap their head around the "contributor guide" for an open-source project - all of them need "beginner level" material which make or break the experience.
Content for beginners is invaluable, and it need not always be a blog post or video. Other relevant forms of content include great documentation (for your products), a code sample demonstrating idiomatic usage of a SDK or API etc. All of them need to high quality, clear, easy to follow.
I can't help but mention Linkerd, a (Kubernetes Service Mesh) whose getting started guide is an absolute delight!
Having said that, here are some additional thoughts:
Do you need to have "deep expertise" to create beginner content?
So, personally, I don't think one needs to be an expert to produce content for beginners. In fact, beginners can do it as well - sometimes this can be ideal! A beginner in some area might be an expert in others. While this person is trying to come to grips with a topic/tech, he/she/they might be able to better address the needs of "fellow beginners" while the context and experience is fresh.
For example, I've see a lot of people who live streaming on topics which they are still learning. It's a great experience to see how they go about things - "learning how to learn".
Hats off to you folks!
Beginner content in which area?
For certain areas/topics/technologies, even beginner content might be hard (compared to others). Here is my list: certain programming language concepts (such as concurrency, generics etc.), CAP theorem, distributed consensus protocols (raft, paxos), specific Kubernetes topics (such as networking, Operator development etc.)
Creating beginner content in these areas is quite a task!
For e.g. check out this staggering 19-part blog series (which I don't think is complete yet!)
... or Go by Example - yes, it is "beginner" content!
To provide a counter example, I shamelessly admit that I've given up on Rust multiple times due to lack of material on topics such as async await, lack of examples/guides on certain drivers/SDKs etc.
Not all beginner content is the "same"
(Potentially) Unpopular opinion ahead!
You also need to understand that unlike advanced level material, beginner content is more likely to redundant, repeated, etc. If you are into producing beginner level content, I would highly encourage you to carefully examine whether that area has already been covered extensively by other folks in the community. e.g. "Deploying your [insert favourite language here] app to [insert favourite cloud provider] using [insert favourite DevOps/CI/CD tool here]"
What I am saying is, try and figure "what kind" of beginner content might be "missing" in that specific area, which can add real value. I would suggest trying to add another dimension to it e.g. is there a caveat which you think needs to be highlighted? or that wierd exception you ran into? lay stress on that part. Help uncover that corner case - yes, they exist for beginner level topics as well and are "instrumental in keeping people from quitting" as rightly pointed out by Dona Sarkar!
But, if all you do is just repackage something which has been repeated over and over and over again (doesn't matter if its an awesome live stream about "Deploying your hello world app on kubernetes using minikube"), just to gather clicks, followers and what not, well, I don't know what to say honestly!
PS: I want to be upfront about it and admit that I have been guilty of this as well.. hey I am human!
Of course, there are exceptions to this rule.. say, for example, you're just getting started with blogging, by all means, use areas you're comfortable with to ease into the process, even if it means posting repetitive "beginner" content.. Power to you!
That's it.. For a change, I shared my "opinion". Feels refreshing!
Top comments (7)
I've been a professional webdev for only 3 years, so I'm very much a beginner. Here's my stance on the issue :
The best content is sometimes written by beginners themselves. They know what's easy and what's hard for fellow beginners
The quality of beginner content doesn't depend on how advanced the tech skill of the author is, it depends on the clarity of the author.
The worse content is usually the content hastily written (or worse, plagiarized) in order to increase visitor counts or make money (Looking at you, that-other-website-where-developers-write !)
The best content is usually the content you wished to find as a beginner, but never found; therefore you decided to write it yourself. It is motivated by a genuine desire to help rather than self-interest.
Thanks for chiming in Samuel. Couldn't agree more! Specially #2 and #4
This was a nice read.
As a Junior in tech I consider content for beginners is important because its always overwhelming to understand something you are new too.
For instance I have been opening gobyexample(as you mentioned) almost everyday just to remember stuff.
What stands out is how the creator is expressing themselves, if they are throwing a bunch of code at me without much explanation, i just switch to something else.
Glad you like it Bhupesh! "Go by Example" is amazing isn't it... Since you are already "opening gobyexample(as you mentioned) almost everyday", I would also suggest devoting a little bit of time everyday (even 15 mins if fine) to practice those "examples". After a month or so, you will be surprised by the compounding effect :)
Cheers!
Yes I have been doing this is in form of doing coding challenges in Go, and refer to these examples from time to time
I'm in the camp KISS (Keep It Simple Stupid) partly I had teach kids previously as a coding instructor. I would do my best to reduce the jargon and provide examples that is easy to follow with clear writing.
I believe examples of good beginner content is like Twilio, SendGrid, Digital Ocean or Real Python. Which they focus on setting a high bar for beginner content to make it easy to digest the content and get started.
Thanks for adding your perspective Max :) You're bang on about Digital Ocean and Real Python! I love the tutorials on digitalocean.com/community/tutorials as have been reading up on realpython.com/ content (on and off) as well - been trying to pick up some Python lately ;)