Enhancing Technical Skills by Writing: Learn in Public
Tags: beginners, writing
Published: 2024-06-23 21:20:03

## Overview
- In this article, I will share the reasons why I write technical blog posts and my approach. I hope this will motivate and guide you to start writing about topics you are studying or already familiar with!

## Table of Contents

- [Reasons why I write technical blog posts](#reasons-why-i-write-technical-blog-posts)
- [Learn in Public vs Content Creator](#learn-in-public-vs-content-creator)
- [Do I use ChatGPT or other AIs when writing? Yes, and no.](#do-i-use-chatgpt-or-other-ais-when-writing-yes-and-no)
- [Steps I follow to create my technical blog posts and suggestions for you](#steps-i-follow-to-create-my-technical-blog-posts)

## Reasons why I write technical blog posts

- To learn/improve technical knowledge.
- To learn/improve storytelling.
- To learn/improve writing.
- To learn/improve English.

## Learn in Public vs Content Creator

- These terms are different. As a learner in public, you share what you've been studying technically.
  - The purpose of a learner in public is to document and share their studies.
  - The purpose of a content creator is to entertain. (This is not my focus, and probably not yours if you are here.)
- Some advantages of learning in public:
  - Builds accountability and consistency.
  - Reinforce your learning through teaching and practicing.
  - Provides opportunities for feedback and improvement.

## Do I use ChatGPT or other AIs when writing? Yes, and no.

- No, AI does not create my content.
  - **If AI did, I wouldn't learn anything during this process**, and it would be a **complete waste of time**, which I can't afford.
- Yes, I use ChatGPT and AI to review my English and minimize typos. I also use GPT to improve my markdown, as I write all my posts using a `file.md` on VsCode.
  - But I still try to maintain my writing style, even if it means committing "mistakes" and not being the best English writer.
  - "Mistakes" because I'm referring to my writing style, which may not be perfect, **but it's mine, not an AI's**.
  - "Mistakes", because I'm talking about the writing style, that's probably not the best, **but it's mine** not of an AI.
  - As I mentioned before: **My main purpose is to learn** and to do that the content creation follows [certain steps](#steps-i-follow-to-create-my-technical-blog-posts).

## Steps I follow to create my technical blog posts:

- There are some types of posts that I used to write, some more informal, others more formal. Sometimes practical tutorials, and sometimes theoretical content about something that I'm studying for the first time or reviewing.
- But in all of them I follow a "basic algorithm":
  - 1. **Select the subject you will learn or review**
      - Here you will select the content, but more than that, ensure it is something you are genuinely interested in or that solves a problem you have or have encountered before.
  - 2. **Write the article with your own words and understanding of the content**
      - How do you know if you understand something? By teaching others and practicing.
      - To teach others, you can't be reading something and writing at the same time, because you will just copy the words you've read without realize. Instead, try to do it naturally, read first, practice, create examples for yourself, and then write just what you've learned.
          - But don't get too attached to it, sometimes it's important to use the actual definition and avoid your own words, be sure to do this at the right moment.
  - 3. **Review written content, typos, and also markdown.**
      - Ensure that what you've written is not a misunderstanding of the subject.
          - In the future, if you see something wrong you can re-write about this subject, why not?
      - For typos, you can use AI, Grammarly, read again, or even hire a professional. (Probably paying someone it's not your idea, right?)
      - To review markdown and improve formatting you can use AI.

## Thanks for Reading!

- Feel free to reach out if you have any questions, feedback, or suggestions. Your engagement is appreciated!

## Contacts

- You can find this and more content on:
  - [My website](https://godinhojoao.com/)
  - [GitHub](https://github.com/godinhojoao)
  - [LinkedIn](https://www.linkedin.com/in/joaogodinhoo/)
  - [Dev Community](https://dev.to/godinhojoao)