Introduction
So you’ve written your AWS Article, you’ve created a little demo and shown the code in the article and your thinking: What if no one reads it because they can just go to ChatGPT and find all this information just by a simple prompt?
Is there no hope? Should I just go to Podcasting? Or knock on developers front doors and speak to them in their own homes? Is there any way to beat ChatGPT at technology information sharing?
Title and Graphics
An AI Chatbot can give you suggestions, but they don’t pick up the peculiarities of art which are many times personal to the artist himself/herself. Since AI just picks up patterns that have gone before, it can’t add the ‘provocative touch’. That which goes against the grain and adds meaning to art and writing. This is something that can go so deep it can’t even be taught in the schools. So in picking a title, even a seemingly objective AWS article should have a bit of a spin that feels right.
In the same way, Graphics and even Art can lend an attractive feel to the article that makes it more easy for the developer to read the article. Good graphics can even gamify the reading experience making the developer, in the most optimistic perspective, even read the article over again at least partially for enjoyment. Nevertheless the graphics are also talking and sending a subconscious message. A subtlety that ChatGPT could only come up by chance.
Personal Journey
Your personal journey will attract other developers to read your article. People love stories, they’re all around us and without them the world is boring and stagnant. So even subtly it’s important to turn your article into a storyline of some sorts. ChatGPT also has a story of its own, but it’s not a developer story, and that’s who your audience is. They will bond more easily with the story of other developers than the story of an AI Chatbot.
MIstakes
Tell us about the mistakes you’ve made and how you’ve learned from them. Hopefully you’ve learned from them otherwise, you won’t be able to tell us how you’ve learned from them. And just by telling us what you’ve learned and the steps that got you to that enlightenment, other developers can learn something as well. That proves you’re not just intelligent like an AI bot, but you’ve got a soul as well.
Successes!
Describe real-world projects that were a success, but don’t forget to tell us the stakes and the dangers that were involved in getting to that tremendous victory. Even make it a series of article. Don’t talk about just what you’ve built, but the sweat and tears that got you there and the surprising technological innovations that you didn’t even plan but that just showed up. ChatGPT can’t do anything like that.
Advanced Features
Tell us about advanced features and new and lesser-known facts about AWS. Things that the AI Chatbot may have trouble with and give forth hallucinations. Here the concept of authority comes into play. So make sure your facts are correct so that you are deemed trustworthy.
Have a series of articles on a particular AWS subject that goes in-depth into material, one thing following the other. But there all the facts are checked and then updated as times goes on. Have code samples that go along with explanations so that each small thing in the article being quality checked adds up to an authority on the subject that will be greater than what an AI Chatbot is capable of.
Theories and Opinions
Even in the most objective and factual article, you can always add in your own opinion or theory. People love to hear criticisms that make sense to them or theories that excite their imaginations. This will personalize your article even more, giving a ‘human touch’ and creating greater community when people are comforted by honesty and see a striving for greater excellence. And even humor targeted at other developers can lend that light touch to the doldrums of tech engineering.
Conclusion
There is hope to beat AI even in online tech articles. AWS is a wide subject matter with continuous changes and while AI is powerful and Amazon Developer and Business Q even more powerful for AWS, AI is still no match for your personal journey or your jokes or your art and well-chosen graphics or the strange things you do with the finer elements of AWS.
Perhaps the greatest of these elements of the ‘personal touch’ is the ‘personal journey’ in which your tech journey can be recorded and told to others. Your journey is a true story and not something AI has fabricated. Your personal journey is not a hallucination (hopefully!) and because of that writing it down and telling others about it will make it an even greater learning experience for yourself, and then for others as well.
Top comments (0)