↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

One year of writing a blog post every week: this is what happened

The author says a year of weekly blog posts made writing easier, even though topic selection, structure, and timing remained difficult. He used Grammarly Pro or Google Docs, started series such as CSS Quickies, and tried to balance value, readability, and personal interest.

He also says the challenge brought followers, reactions, views, comments, and interview value, but not much change in his professional life beyond that. He cross-posted on social media, answered comments when he could, and now wants to keep posting regularly instead of weekly.

Reading notes
#

  • A friend and he started a weekly blog post challenge, with a reward of pizza and beer for whoever failed.
  • Before the challenge, he wrote about once a month and found it hard to learn new things consistently.
  • At first, finding topics was easier than writing with structure, and readers often pointed out typos and grammar.
  • Grammarly Pro helped him write with fewer typos, and he recommends it or Google Docs over Microsoft Word.
  • Over time, finding topics became harder because each post had to be engaging, researchable in a week, and interesting to him.
  • Some ideas had to be dropped or split into parts because the research and sample code took too long.
  • He tried to make topics more general and a bit more clickbaity to reach more people, but that also drew criticism.
  • He says there is an art to making titles engaging without making them clickbait.
  • Vacations made weekly publishing harder, so he sometimes prepared posts ahead of time or wrote them while traveling.
  • He created series to generate ideas, including CSS Quickies and a popular VS Code series.
  • A standard workflow for a series helped streamline the writing process.
  • He says every post forces a tradeoff among writing about what he likes, what people want, and what is easy to research and write.
  • He wants to give value and explain things in a way that most people can understand, even if that is never perfect.
  • He prefers examples that are easy to execute and real-world explanations that show how to think like a developer.
  • At the time of writing, he had 32k followers, 11k reactions, and 681k views on dev.to.
  • He says the numbers matter less than what they lead to.
  • He received many messages about help, collaboration, cross-posting, freelance work, and paid posts, but ignored most of them.
  • He was nominated as a top 500 writer for 2019 and used a $50 dev.to shop voucher to buy a backpack.
  • He cross-posted or linked posts on Facebook, LinkedIn, Xing, Twitter, and Instagram, but found Twitter most useful and Facebook least useful.
  • He says Instagram had a lot of low-value content, while LinkedIn and Xing were acceptable.
  • He tries to answer comments and questions when he can, but says some questions cannot be answered honestly without more context.
  • Writing weekly helped in interviews because it shows continued learning and self-improvement.
  • He is thinking about starting a YouTube channel, is creating a course for a company, and wants to keep posting regularly.