Novice To Expert: My freeCodeCamp Writing Journey
Tags: writing, coding, webdev
Published: 2023-12-22 02:22:04

---
title: Novice To Expert: My freeCodeCamp Writing Journey
published: true
date: 2023-12-22 01:20:13 UTC
tags: #writing #coding #webdev
series: Musings of a Coding Enthusiast 
canonical_url: https://chrissycodes.hashnode.dev/novice-to-expert-my-freecodecamp-writing-journey
---
![With freeCodeCamp's logo as a background, the blog's title "Novice To Expert: My freeCodeCamp Writing Journey" is written in white and bold](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/gjm8snsl7vfbu20w4ap2.png)
## An Unexpected Surprise

I was doing my usual GitHub scroll when a ping from LinkedIn grabbed my attention. It was Quincy Larson sharing his list of [Top Open Source Contributors for 2023](https://www.freecodecamp.org/news/top-open-source-contributors-2023/) on freeCodeCamp News. As I casually flicked through the article, something in the **Publication Top Contributors'** section jumped out at me:

![Screenshot of the Publication Contributor's section where my name is circled in red.](https://cdn.hashnode.com/res/hashnode/image/upload/v1703203154196/f3eba18c-3bd3-406f-9c89-0c61dba512b3.png)

Yup, thats right! 😊 I'm officially one of the Top Publication Contributions for 2023! 🎉 As I sit here basking in this victory, I cant help but realize how much writing for freeCodeCamp has shaped my writing style. So, grab your drink of choice, and join me as I dive into how far Ive come in my journey.

## Keeping Titles Simple

When I began penning tech blog posts, I aimed for quirky yet SEO-friendly titles to engage readers. Here are a couple of examples:

- [DevOps' Secret Sauce: 5 Uncommon Productivity Tips](https://dev.to/cbid2/devops-secret-sauce-5-uncommon-productivity-tips-1npn)

- [Save Your Head and Your Data: 3 Do's and Don'ts for Backing Up Your Devices](https://dev.to/cbid2/save-your-head-and-your-data-3-dos-and-donts-for-backing-up-your-devices-663-temp-slug-1296166)

But when I started writing for freeCodeCamp, I discovered that straightforward "How To" titles are just as powerful. For example, I used the title [How to Collaborate on Pull Requests for Beginners](https://dev.to/opensauced/how-to-collaborate-on-pull-requests-for-beginners-434a) for an article where I provide tips on creating collaborative Pull Requests, and this happened(shout-out to @bekahhw for being my inspiration! 😊):

![Screenshot of the stats of my blog. Its 10617.](https://cdn.hashnode.com/res/hashnode/image/upload/v1703204442035/5c3dd4a8-d957-4f62-9584-540b30a73afd.png)

10k views in just two weeks after hitting publish? Talk about exciting! 😊 But you know what made me even more elated? Reading through the comments. It was heartwarming to see people share how my content inspired them to start contributing to open source projects. Now, freeCodeCamp didnt just influence my writing with simple titles, they also changed how I implement other sources. Let's look into it! 😊

## Less Use Of GIFs

Contrary to the saying "A picture's worth a thousand words", sometimes words are worth more than the picture. In my earlier FreeCodeCamp articles like [How to Give Good Feedback for Effective Code Reviews](https://www.freecodecamp.org/news/code-review-tips/) and [Save Your Head and Your Data: 3 Do's and Don'ts for Backing Up Your Devices](https://dev.to/cbid2/save-your-head-and-your-data-3-dos-and-donts-for-backing-up-your-devices-663-temp-slug-1296166), I used to add a lot of GIFs, thinking they'd make the tech learning experience fun and keep readers engaged. But as time rolled on, I found myself gradually favoring code snippets and resource links, realizing they could convey my message better. It's like outgrowing one approach and smoothly transitioning to another. Speaking of change, lets delve into another way FreeCodeCamp revamped my writing style! 😊

## Add More Resources

In earlier blog posts like ["How to Create an AR Widget with No Code"](https://dev.to/cbid2/how-to-create-an-ar-widget-with-no-code-2lkc-temp-slug-3408896), I used to conclude them with a link to my social profiles. Then, it hit me: "What if someones all set to build but needs a starting point after reading my article?" Thats when I began adding project links and resources to my conclusions. Check these out:

- [How to Write Commit Messages Maintainers Will Like](https://www.freecodecamp.org/news/how-to-write-commit-messages-maintainers-will-like/)

- [How to Create Small Yet Powerful Pull Requests](https://dev.to/godspowercuche/how-to-create-small-yet-powerful-pull-requests-3ml3-temp-slug-5878896)

As seen in those articles, I started embedding project links, giving readers a way to put their newfound skills into practice. Its like having dessert after a good meala sweet way to wrap things up. And speaking of wrapping up, theres one more way freeCodeCamp reshaped my writing.

## Don't Name The Obvious

In the past, I'd title my last section Conclusion. But an editor pointed out it made posts less lively. Since then, I've simply started my conclusion. Its akin to a movie revealing its main plot in the trailersome things are better left a bit subtle.

It's been an amazing journey writing for freeCodeCamp, and I can't wait to see what I'll write next. If youre looking to level up your tech writing skills and be part of the community, I highly recommend reading [Kealan Pars guide on how to write a winning application](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). And if you need more application tips or just want to read my other content, find me on [Hashnode](https://chrissycodes.hashnode.dev/) and [BioDrop](https://www.biodrop.io/CBID2). I'm glad to connect with you! 😊👍🏾

## Credits

Logo by [freeCodeCamp](https://www.freecodecamp.org/)