Write for yourself so that one day you might write for those you look up to
If there's one message to take from this article, take that one.
Blogs are a hot topic.
- Should you start one?
- Are you good enough?
- Who should you write for?
- Where should you put it?
- What should you write about?
- What's my style?
- Did someone already write about that topic?
- Will anyone care?
- When should I post it?
- Will anyone read it?
- How do I write for super-cool-site.com?
Jhey π@jh3yy
Thinking about writing content? π€
Start! βοΈ
Write about things you're interested in and that you enjoy π
Don't be put off because someone else wrote about a topic before you did. It's all about perspectives π―
Your perspective might lead someone to great things! π11:00 AM - 26 Jun 2020
I completely stand by that. It's hard to convey all my thoughts around this subject in 280 characters though.
Let's dig in!
Should you start one?
If you've even considered writing content. Don't keep thinking about it, do it!
And I mean that in the best way possible.
The sooner you start, the sooner you can hone your skills at writing and find your voice as a writer.
Priya@priyacodes98Anyone have tips on starting a tech blog00:38 AM - 26 Jun 2020
Jhey π@jh3yy@priyacodes98 Start.
And I mean that in the best way π
Write things as if they are a ref for yourself and write about things that interest you. Your skills will improve and you never know where it might go π
Also, never EVER, be put off writing about a subject that has been written about!01:11 AM - 26 Jun 2020
Are you good enough?
Yes.
Let's move on.
But, seriously, you are. It doesn't matter what level you're at. People enjoy relatable content. That doesn't only apply to when you write tech content. Share your journey and the things that interest you.
In terms of writing skills? There are some tools out there to help you. My personal combo of choice, Hemingway and Grammarly.
Who should you write for?
Yourself.
Write for yourself. Write as if this is a reference for you and you alone. If you're writing a tutorial or something for other people to follow, the same holds true. Of course, consider that you'll want others to understand it. But, the number one concern is that you understand it. Perspective is everything and can drive your content as you gain more experience. More on this later.
Where should you put it?
This is one I see all the time.
I'm thinking of making a blog. Where should I put it? Should I build something with "Hot spangled new blog platform X"?
If you want to write content. Write content.
Where you put it shouldn't be a blocker to you writing content. If it is? Ask yourself if writing that blog post still interests you?
That said. There's nothing wrong with trying out awesome tech stacks to host your own blog. I'm all for it and I plan on doing it soon. It's awesome to learn things. My first attempt at this was using Jekyll for the record.
But, the purpose of this article is to get writing content. And if that's your primary goal, the platform should be the afterthought.
Heck. You could even create a new Github repository and start writing in Markdown right away!
My personal journey: Self-hosted Jekyll, Medium, CSS Tricks, Dev.to, etc.
One thing I will say is that you're more likely to get engagement on the bigger platforms in my experience. This of course depends on your site traffic if you're self-hosting, etc. But, something to be aware of. If I were to recommend a starting point now? It would likely be here on dev.to.
What should you write about?
Write about things that interest you. Don't write about something because you think it's what other people want to read about. The exception here being if someone says they'd like to read about your take on something. Even then, only do it because you want to.
Write about things you enjoy. Write about things that you'd like to reference later. For example, learn something new on that last thing you made and inline comments won't do the job? Write a post on it so you have something to look back at.
The more you write, the better you will get at writing. Write about different things and you'll find the things you like to write about. That could take you in a direction where you can shine.
My first published posts are about things I learned or things I enjoy. One such post is about Pug(It was then named Jade). The first paragraph is more about me than Pug ha. It's clear I wanted to write things. I've since revisited some of my earlier articles to clean them up a bit. But this article about creating image overlays with CSS was something I wrote for myself. Others found it useful and let me know.
And that's a key point to be aware of. Because you hit "publish", doesn't mean it's set in stone. You can edit it later or update it. If you don't like it, you can take it down completely. I've done that with some of my content.
What's my style?
You'll find this as you go. The more you write, the more likely you'll find a style that suits you.
There's one thing I advocate if you're writing about tech and there's code involved. Please leave a link to some code or a demo.
One format I worked towards for a while was leaving the demo and the code right at the top with a TL;DR.
That might sound counter-intuitive. You want people to read the whole article right? Well, I want to share something. And if people want a quick route to the answer, I provide that. That's what I look for. But there will be those that read the whole thing too. But think that if someone only grabbed the solution, it helped them, and they shared it. Then that might bring more of an audience.
Another style I like for me is "Learn something in X minutes". I guess what I'm getting at is, you won't know your style until you try things. Try different ideas and see what works for you. I quite like the "X minutes" ones because it means I am trying to keep the content brief. But, for an article like this one, I'm sitting here writing my thoughts and enjoying it.
Did someone already write about that topic?
This one is huge! Please don't hesitate on writing a post because someone wrote about the same topic before. This is like the number one rule!
Consider it like this. And please correct me in the comments if this is wrong. The analogy still applies though.
Motorola released the first cell phone in the 80s. Now, if everyone stood back and said "They've made a cellphone, we can't". There would be no iPhone, no Android, etc. Perspective drives innovation. It takes someone to see something a certain way to think about how they might take it to the next level. Does that make sense?
And this can apply to your own writing. Your perspective and the way you write about something might be ideal for someone. They may have read ten articles already. But, yours was the one that gave them the "Aha" moment. And now they could be on their path to something great. How awesome is that?
Perspective is everything. Don't discourage yourself.
Will anyone care?
Don't make this your focus. Flip it on its head. A more important question is, do you care? Because if you don't care about your writing content, why are you writing it?
When should I post it?
I've seen this one a lot recently.
I finally overcame my fears and wrote my first blog post π and Iβd like to publish it on @ThePracticalDev
what is the best time of day and day of week for posting things? any recommendations?
#writing #javascript18:48 PM - 27 Jun 2020
My response goes something like this
Jhey π@jh3yy@chriskalmar @ThePracticalDev IMO, there is no best time. Especially if you're starting out! π
Write for yourself if you're starting out and if the content gains an audience, that's a huge bonus! π
But, don't put pressure on yourself is the main thing π
Content and consistency can be a goal to start19:48 PM - 27 Jun 2020
And I stand by it. There's no formula or "best time" in my experience/opinion. Exactly 15:17 on a Tuesday isn't going to solve your problem. Do what works for you. You could post the same thing 3-4 times on social media and people are still going to miss it. That's how it goes.
Content will always prevail and you never know what that might be when you start. You're finding your way with it.
The first post that worked for me? A thirteen-minute read about creating pure CSS masonry layouts in 2016. I posted it because it was something I enjoyed exploring. A week later it had a spike in views and I had no idea why. It didn't matter when I posted it. It gained an audience a week later.
Before that, I'd been writing about various topics. But because of that post, my other content became seen. Content that I'd posted almost a year earlier gained attention.
It echoes the points from before. Write about things you enjoy. Post them when it works for you. Don't pressure yourself. You never know who might be watching.
Will anyone read it?
Of course, we want people to read our content. Otherwise, we wouldn't publish it. But by not focussing on that, it can happen. That almost sounds counter-intuitive.
But from that previous example. I wrote for myself and it happened that others were watching.
That said, there are some tips for getting your written content in front of people.
Tags.
Most of the platforms support some form of tags. And this must help in some way. I can't vouch for every way of doing this but here's my experience.
Tagging things on Medium helped to get it in front of people. Then publications would request to add the article to their publication. That gains more traction and go from there. With Dev.to, use the tags and make use of "Suggested tweet". You get the opportunity to have your content shared with people by a popular account.
How do I write for super-cool-site.com?
I can't vouch that my journey will work for you. But I do believe being consistent and writing content can lead to great things.
I've been fortunate to write for some of my favorite publications. All because I started writing for myself. I wrote about things I enjoyed and things that interested me. I didn't write because X, Y, or Z was watching.
It took time though. I've been writing content for around 6 years at the time of writing this. Something that I've only realized writing this now.
It's no secret, I love CSS. One of my biggest goals was to write an article for CSS Tricks. At the time of writing this, I've got five published on there now.
How did that happen? I said I'd like to.
A lot of the big publications have guest author programs and info on their sites. Reach out. Propose an article. What's the worst that can happen? They say no? They could decline. But, even if they do, I'd bet they'd be willing to help you. Help you in a direction that will lead to writing content for their platform.
That's it!
Write for yourself so that one day you might write for those you look up to. Be interested in what you write about and share your journey.
The best time to start is now. The best time to share it is when it's ready. If your content interests me, I'll be there to read it, wherever it is.
This is my story. I look forward to reading yours!
As always, I'd love to hear what you have to say. Leave a comment or come find me on Twitter!
Top comments (12)
alright, alright, I will post soon. my post just needs some final polishing π
I really love that cellphone analogy. I've heard "It doesn't matter if someone's written about it already, just write it" before, but I hope it will stick when I remember this analogy.
Great article!
I published a tutorial in Spanish some days ago, thinking no one would read it. But it already has 7 Likes (including 1 unicorn and 2 bookmarks, omg) and it made my entire week. I think everyone has something valuable to show/teach to someone else.
This is a great article. I've set intentions to write more in the past six months and I have to catch myself when I get caught a lot of the traps that you mention.
I tend to put a lot of pressure on myself to do things, which is frequently counter-intuitive when it comes to getting something done because I hate pressure π
I love the point about when to post! I've found myself falling into that trap. Sometimes I'll spend a stupid amount of time looking at when to post, and then realize that I could have been writing content that whole time. Don't optimize for the small stuff. Writing content should be your number one goal.
Great post, thanks for sharing your thoughts!
This is a great post. And it took me less than 8 minutes to read it haha. Thanks a lot for the encouragement. Not sure if I'll be writing a lot about really techy topics but as I find your content interesting, I hope you also find mine interesting π
Couldn't have said it better myself!!!! β€οΈx1000
I've recently started writing and have been enjoying it very much and apparently people have been too. My second post really took off on this site but for those that haven't hit that luck keep going!!
Thanks for the share!
It is indeed very easy to fall into the trap of "there's too much similar content already" or "who am I to teach". But the best way to learn something is to teach it. So even if you don't have many readers, at least you will have learnt something.
This is a beautifully written article. Thanks for all the valuable insights. I feel much better for starting my journey as a technical writer.
Great Article Jhey!
Great article, so positive and encouraging. I will dedicate some time to start working on my first article. Wish me luck π
real talk i tryna write one bug or one project at a time right now even though my writing is bad but it is both a note for myself and those who want to learn thorugh my article