100 things I learned as a blogger and online course maker by reading 100 things @viebel learned from writing his book. (Thread)
blog.klipse.tech/book/2021/12/1…
#blogging #BloggingTips
[1/100]
"Writing a technical book is much harder than writing blog posts."

Definitely agree. A much larger part of content needs to be extremely coherent and well-linked.
#bloggingTips
[2/100]
"Writing a blog post is like running a sprint while writing a book is like running a marathon."
@viebel true, but I think you should compare writing a book to writing a successful blog. This also feels like a marathon. We don't compare a class to a startup.
#BloggingTips
[3/100]
"Each piece of the book content must be clear and interesting. Each part, each chapter, each section, each paragraph, each sentence"

This is a good advice for all creators. Keep it all clear, coherent and interesting. Challenging? Yes. Worthy? For sure!
#BloggingTips
[4/100]
"Clear is more important that interesting. If something is not clear, it cannot be interesting."

Again, this is sth that should be applied everywhere, including even a written code.

#BloggingTips
It's also easier to work on our writing skills this way. work on clarity, then focus on adding more interest and fun to the Content.

#BloggingTips
[5/100]
"A possible way to make things clear is to go from concrete to abstract"

Whenever I Try to explain sth I try to put a strict example first and then use it to prove my general idea or thesis.

#BloggingTips
[6/100]
"A possible way to make things interesting is to teach the material as a story with fiction characters and a bit of drama."

@viebel this is an awesome tip, not often seeing in technical writing. #inspired

#BloggingTips
[7/100]
"The 'why' is more important than the 'what'".
"The 'what' is more important than the 'how'.

Note: this is general truth of how to live a successful life.

#BloggingTips
The "why" is the mission - reason to run a blog or course.
The "what" is about the content.

Tooling is the least important part.

#BloggingTips
[8/100]
"An average writer makes the reader think the author is smart. A good writer makes the reader think the reader is smart."

Having fun of my own mistakes is good. Learning from own mistakes are beneficial to me, so can be for others.
#BloggingTips
Example: hanamimastery.com/episodes/12-au…

Here I told a story of my ridiculous naming mistake to show that naming can be hard. I wish more people was comfortable with talking about their setbacks.

#BloggingTips
[9/100]

"A technical book is written for MQRs (Minimal Qualified Readers)."

It's extremely important to think about your audience before you start writing. If your post is for another audience, use guest blogging.

#bloggingtips
[10/100]
"Figuring out the qualifications of your MQRs is important"

It's hard to find a balance. If you set your MQR expectations too high, you'll get too small of an audience. This is the key reason why there is so little content published for experts and seniors
#bloggingtips
[10/100]
"It’s hard to figure out the qualifications of your MQRs (Minimal Qualified Readers)."

Especially without an audience. This is when having a blog already when writing a book is useful.
#bloggingtips
[11/100]
"Checking book sales could be addictive."

So true! But it applies to everything, especially at the beginning. I was addicted to checking my Udemy sales when started with it, then even article shares when started a blog.
#bloggingtips
[12/100]
"Making a good Table of Contents is crucial as it is the first part of the book potential readers will encounter."

This also applies to having a clear structure and neat internal linking in your blog content.
#bloggingtips
[13/100]
"Making a good Table of Contents is hard as you need to figure out what you really want to talk about."

And deciding what you don't want to include in the book is even harder. This is where I see Guest blogging extremely useful.
#bloggingtips
Guest Blogging It's not only a way to monetise your blogging activity at the very early stage, but also a way to keep your blog focused, extracting everything else to external publishers that link back to your blog.

#bloggingtips
[14/100]
> The Table of Contents might evolve a bit as you write your book.

I advice to start blog with no categories nor tags and allow those to evolve as the content appears.
#bloggingtips
I find valuable often revisiting and updating older publications. Updating the content and internal linking as the authors mindset evolves and changes is a precious habit.

#bloggingtips
[15/100]
"You should resist the temptation to write the first chapter before the Table of Contents is ready."

You should resist the temptation to write your blog post without having the about page, with clear reason of what you want to achieve by having a blog.
#boggingtips
[16/100]
"It’s not necessary to write chapters in order. But it’s easier. "

This is where blogging is easier. I can write content in any order, based on interest, to gain traction in early stages.
#bloggingtips
It's useful to fill the content gaps later, only if the interest in the topic is proven by the community built.
#bloggingtips
[17/100]
"Never assume that your readers will read the next chapter only because they have enjoyed the previous chapter."

People who read the most are people who don't read whole books but focus on extracting the information that they need at the moment.
#bloggingtips
[18/100]
It's useful to remember how people read on the Internet - scans, not full reads.
#bloggingtips
Also never assume your readers will read all your blog posts. Most will read a small part of the article they looked for or was important for them, never comming back.
#bloggingtips
By narrowing down the focus of content, you increase the chance your readers will come back.
#bloggingtips
[19/100]
"You should always convince your readers why what you are teaching is important and relevant for them."

@viebel, Awesome tip!
#bloggingtips
[20/100]
"Before writing a chapter, you should formulate to yourself what is the main objective of the chapter."

Before writing an article, think about title and excerpt. then the outline, and then the actual content
#bloggingtips
[21/100]
"If a chapter has two main objectives, it’s a sign that you should split it into two chapters."

Never hesitate to extend topic in a new article. Nothing prevents you from extracting a part and update the old one by referencing to a new content.
#bloggingtips
[22/100]
"A chapter should be treated like a piece of software. You should resist the temptation of writing the chapter contents without a plan"

Don't do anything without a plan! unless it's a pure entertainment!
#bloggingtips
[23/100]
"A possible way to make things interesting is to use concrete examples."

I believe this is the correct way of making conclusions. Based on example form a thesis, then think if it applies to other examples.
#bloggingtips
"A possible way to make things clear inside a chapter is to start with the easy stuff and increase the level of difficulty as the chapter goes on."

Good tip!
#bloggingtips
[24/100]
"A possible way to make things clear inside a chapter is to start with the easy stuff and increase the level of difficulty as the chapter goes on."

Good tip
#bloggingtips
[25/100]
"Do not hesitate to highlight sentences that convey an important message."

This is an advice that can be applied also when CONSUMING content for research. Don't hesitate to make highlights. don't hesitate to make notes.
#bloggingtips
[26/100]
It’s OK to engage in writing a technical book without mastering every topic you want to cover in your book.

Books are not written by experts - the process of writing a book makes you an expert. The same applies to blogging.
#bloggingtips
Disclaimer: I started blogging about @hanamirb after making only one API application with four endpoints in total: useo.pl/blog/2021/07/t…

Now I drive @HanamiMastery and work full-time on Hanami projects. Because of blogging. #bloggingtips
[27/100]
"Writing technical book involves a decent amount of research even if you consider yourself as an expert in the field."

Video, course, or article - all that require a lot of research. It's important to be able to do research quickly and effectively.
#bloggingtips
Tools like @obsdmd are priceless help here.
#bloggingtips
[28/100]
"Finding attractive but accurate titles to book chapters is an art."

There are tools to help choosing the best article title or thumbnail, with a/b testing, etc. It's wise to decide on article titles before writing the actual Content
#bloggingtips
[29/100]
"You can learn a lot from a failed attempt to write a book, provided that you put your ego aside."

@HanamiMastery is my fourth blog and the first successful one. I learn A WHOLE LOT from my previous attempts though!
#bloggingtips
@HanamiMastery Highly recommend putting ego aside and just learn from mistakes! everybody make mistakes, just not everyone talks about it!
#bloggingtips
[30/100]
"If you try to write a Wikipedia article about the topic of your book before it is mentioned by other sources, it'll be rejected."

If you write about a piece of software being the only blogger in the world focusing on writing about it, better be patient.
#bloggingtips
[31/100]
"It’s possible to write a tech book while keeping your day job as a dev, if you are willing to wake up early or sleep late."

It's also possible to record a course and write a blog while keeping a day job. Just optimize everything.
hanamimastery.com/articles/secre…
#bloggingtips
[32/100]
"Writing a technical book takes between a year and two. "
Impressive. Recording first technical online course takes between a year or two. And be prepared to re-record it after publishing.
#bloggingtips
Disclaimer: Yeah, I know some people do it in 4 weeks.
[33/100]
Don’t rush! Enjoy the journey…

This is a receipt for success also in blogging. Enjoy the journey, and focus on adding value with every piece of work you do! Improve step by step. Get an ongoing value for yourself to keep motivation.
#bloggingtips
[34/100]
"It makes lot of sense to use a source control software for your manuscript."

I write using markdown files kept in git repository. It makes sense to keep copy of everything you do. Do backups. And backups of backups. don't let your 2-year work to be lost
#bloggingtips
Learn from great youtubers in this field... and don't let your #Minecraft world to be gone forever when your hard disk crashes! (Best regards: @docm77 )
[35/100]
"AsciiDoc rocks!"

Markdown with @obsdmd also rocks!
#bloggingtips
@obsdmd [36/100]

"PlantUML rocks!"

😍! Need to check this! Thanks for the tip!!! I found that the more things we keep in just a text make it easier to refactor.
#bloggingtips
@obsdmd [37/100]

"NeoVim rocks!"

@obsdmd is extremely helpful to keep published content in sync with WIP ones and with all other random notes, inspirations, ideas and content researched.
#bloggingtips
@obsdmd [38/100]
"People on @Reddit could feel hurt by opinions that take them out of their comfort zone."

In general people mostly feel bad when facing a fact or opinion taking them out of their comfort zone or requiring to change mind.
#bloggingtips
@obsdmd @Reddit [39/100]

"On @Reddit, when people feel hurt, they could become violent."

I experienced bad and offensive comments just because the commenter had a bad day. Blogger needs to keep the distance and emotions aside.
#bloggingtips
@obsdmd @Reddit [40/100]

Positive comments can be as harmful as negative ones. Compare to trading. Too quick of a success can be a disaster next day because of emotions. Keep emotions aside.
#bloggingtips
@obsdmd @Reddit [41/100]
"Being mentored by an experienced writer is a blessing."

Oh, amazing! Feel inspired! And congrats on this one!
#bloggingtips
@obsdmd @Reddit [42/100]

"If you are lucky enough to be mentored by an experienced writer, ask them to be hard with you. That’s how you are going to improve your book!"

Just remember that they want the best for you.
#bloggingtips
@obsdmd @Reddit [43/100]
Keep this mindset that hard feedback is given because there is a potential in you and your work! Nobody would waste their time on giving feedback if there is no chance for improvement.
#bloggingtips
@obsdmd @Reddit [44/100]
"A good technical reviewer is a representative of your MQRs. They can tell you upfront if sth is going to be unclear to your readers."

It's good to publish parts of your work as early as possible to get feedback loop.
#bloggingtips
@obsdmd @Reddit [45/100]
"A project manager that pays attention to the details is important."

If you are writer, don't try doing everything by yourself. It's only 24 hours after all.
#bloggingtips
@obsdmd @Reddit [46/100]
"Your publisher is your partner."

The same applies to your content sponsors (companies) - make sure they get benefits from sponsoring you, then they will make sure you get what you need!
#bloggingtips
@obsdmd @Reddit [47/100]
"Asking early feedback from external reviewers is a great source of improvement."

Allow access to your beta releases, and suggest content. Allow people to have an impact in which direction you go.
#bloggingtips
@obsdmd @Reddit [48/100]
"You could make more dollars per copy by self-publishing but you’d probably sell much less copies."

@udemy is the best place to start with course publishing. Once you make the audience, you can go to self-publishing.
#bloggingtips
To get meaningful selling partner for your next courses you need to first prove you can deliver quality content. That comes down to the fact that @udemy is the best place to start with course publishing.
#bloggingtips
@udemy [49/100]
"Releasing an early version of the book allows you to find out if the topic of your book is interesting."

Earlier to market, the better. Perfectionism is your enemy.
#bloggingtips
@udemy [50/100]
Things like book or online course are never perfect, but you can always improve in the next version. Internet has a very short memory. My Rails API course (udemy.com/course/ruby-on…) is already at v3 and in the middle of publishing v4
#bloggingtips #ruby
@udemy [51/100]
"Finding a good book title is hard."

Finding good blog name and domain is also hard.
#bloggingtips
@udemy Names that means nothing have their merits because you can give them any meaning, but require tremendous amount of work to do it. Names engaging your audience are the best but you risk to get bad feelings from competitive part of market.
#bloggingtips
@udemy [52/100]
"You need to be very careful not to hurt the sensitivity of any of your readers."

That's mission impossible. I hurt some people just by having @hanamirb in my @hanamimastery blog name. I hurt others by having @rails name in my Rails Rest API course. 😅
#bloggingtips
@udemy @hanamirb @HanamiMastery @rails [53/100]
"Having your book featured on @newsycombinator home page doesn't mean selling lots of copies."

High quality content is a long term investment. Better is to have 2k sales with high rates than 10k with bad reviews.
#bloggingtips
@udemy @hanamirb @HanamiMastery @rails @newsycombinator [54/100]
Your first content creation project I s not the best one. If done well, can attract partners, influencers, other sellers. Can open gates for partnerships you never imagined when you started.
#bloggingtips
@udemy @hanamirb @HanamiMastery @rails @newsycombinator [55/100]
"Twitter is a great medium to share ideas from your book."

It's important to know where your audience is. I used to post on #Facebook , but developers don't like facebook. @Twitter and @Reddit are the way to go. I never used Reddit before @hanamimastery.
#bloggingtips
@udemy @hanamirb @HanamiMastery @rails @newsycombinator @Twitter @Reddit [56/100]
"My real motivation for writing a book was neither to be famous nor to be rich. I only wanted to accomplish a child’s dream."

It's important to know yourself, and your motives.
#bloggingtips
@udemy @hanamirb @HanamiMastery @rails @newsycombinator @Twitter @Reddit This is where fun begins.

I always liked to teach and learn.

And I quickly learned that the best way to learn is to teach.

I do want to achieve financial freedom, but never want to stop being a programmer. I just love it.

#bloggingtips
@udemy @hanamirb @HanamiMastery @rails @newsycombinator @Twitter @Reddit [57/100]
Figuring out the way to never start from a blank paper is important skill.
#bloggingtips
@udemy @hanamirb @HanamiMastery @rails @newsycombinator @Twitter @Reddit [58/100]
"Usually readers stop reading after reading the middle of the book. If you want them to read the second half of your book, you need to find a way to hook them."

Amazing tip! @viebel would love to hear more on this.
@udemy @hanamirb @HanamiMastery @rails @newsycombinator @Twitter @Reddit @viebel [59/100]
"Inspiration is not linear. It’s OK to stop writing for a couple of hours."

For SEO and growth it's important to publish regularly. But it's important to take breaks too. Figuring out the way to backlog articles ready to be published is a great advantage. #bloggingtips
@udemy @hanamirb @HanamiMastery @rails @newsycombinator @Twitter @Reddit @viebel [60/100]
"Motivation is not linear. It’s OK to stop writing for a couple of weeks."

Productivity gurus lie. People are people. If you don't sleep because of your children cry at nights, it's a torture to force yourself to write.
#bloggingtips
@udemy @hanamirb @HanamiMastery @rails @newsycombinator @Twitter @Reddit @viebel [61/100]
"You should make sure your readers will never frown while reading your book."

Hmmm, @viebel, I frowned here :D
@udemy @hanamirb @HanamiMastery @rails @newsycombinator @Twitter @Reddit @viebel [62/100]
"Be open to critics - even when they hurt your ego."

People rarely want to hurt you. Sometimes they do, but your will quickly learn to ignore those.
#bloggingtips
@udemy @hanamirb @HanamiMastery @rails @newsycombinator @Twitter @Reddit @viebel [63/100]
Most of bad comments I get is either correct but too hard due to the lack of commenter's comunication skills, or because my content was not clear enough and there was misunderstanding.
#bloggingtips
@udemy @hanamirb @HanamiMastery @rails @newsycombinator @Twitter @Reddit @viebel [64/100]
"The more you write, the more you like it."

The more you do anything, the better you get in it, it becomes easier and higher quality with lower effort. Yes, you'll like it more and more.
#bloggingtips
@udemy @hanamirb @HanamiMastery @rails @newsycombinator @Twitter @Reddit @viebel [65/100]
It’s a great feeling to mention the work of other authors.

This is why I give so much appreciation everywhere. I love to highlight other peoples work.
hanamimastery.com/articles/givin…
#bloggingtips
[66/100]
"When you are blocked in the middle of a chapter, it might be a sign that you need to rest and come back later."

Keep the balance. Rest is more important than streak.
[67/100]
"You should make sure that each and every code snippet - that appears in your book - runs as expected."

And this is problematic. libraries get updated, new language/framework releases happen. code breaks over time and this is the dark side of writing technical content.
@viebel could you share how do you ensure that?
[68/100]
"Writing in a coffee shop makes me feel like a famous author, but in fact I am much more productive at home."

To keep productivity at home I need to change environment from time to time.
#bloggingtips
[69/100]
"Use headlines, highlights, call outs and diagrams to make sure it doesn’t look boring.

It's hard. but also important to both: writing articles and making screencasts. Keeping video about writing a code interesting is a challenge!
#bloggingtips
[70/100]
"Working on your book is a good reason to wake up early. Even in summer before sunrise."

Unless you work for timezone -9, where no matter how early you wake up, it's never too early!:). but I like writing in evenings, when my kids are sleeping.
#bloggingtips
[71/100]
"Include at least 2 or 3 diagrams in every chapter. It makes the material fun to read and easier to grasp."

Include images and diagrams to show your reasoning and visualize thoughts. Don't hesitate to go back and update/replace/add those.
#bloggingtips
[72/100]
Don't use too many gifs. Those are distracting to a lot of people even though they're cool.
#bloggingtips
[73/100]
"Remember that the print version of the book will be not be in color."

It's wise to remember about accessibility. Some of your readers can't see colors.
#bloggingtips
But a lot of your readers will use reading apps that make content looking way different, much simplified. It's important to remember that some reading apps don't show images. Your content needs to be clear without them.
#bloggingtips
[74/100]
"Mind maps are a great visualization tool. Use them smartly."

I definietly need to learn making use of them! @obsdmd mind map is an amazing plugin. Allows to create mind maps from text right in obsidian.
#bloggingtips
[75/100]
"When a section is more difficult to read than the others, let your readers know about it."

Your article is about solving people's problem. make it as easy as possible. If article os too long, TLDR section is great tool. Wrap-up is very important too.
#bkoggingtips
[76/100]
"When a section is more difficult to read, make it skippable."

TLDR is a good thing. Your reader's time is precious. If they spend 30 min on reading sth they don't need, it's really bad for you, even though it looks good in google analytics.
#bloggingtips
[77/100]
"Throwing away some (good) ideas is sometimes necessary. Not easy but necessary."

"I am at least as proud of things I didnt do as from those I did." - Steve Jobs.

#bloggingtips
[77/100]
"When you are blocked in the middle of a chapter, it might be a sign that you need to rethink the chapter."

If you get a title but can't proceed with the code examples or content, it may be too early for you.
#bloggingtips
[78/100]
Keep your drafts and ideas in your note taking system, and come back later.
DO. NOT. DELETE.
#bloggingtips
[79/100]
"Don’t worry if your English is not perfect. Your manuscript will be proofread later."

Use tools like @Grammarly to reduce your grammar mistakes, typos and improve content quality.
#bloggingtips
[80/100]
"“Not being a native English speaker” is not an excuse for your lack of clarity."

Not being a native speaker is not an excuse for anything. Maybe except being slower than natives.
#bloggingtips
[81/100]
"Using humour in a technical book is possible. Hopefully, it’s well appreciated."

Using humour in programming screencast and technical articles is possible. I wish more people would do it so I could learn faster and get inspired more
#bloggingtips
[82/100]
"Getting positive feedback - even from people who are easily enthusiastic - feels good."

Getting positive feedback is motivating.
#bloggingtips
[83/100]
"Writing my first technical book without a publisher would have been a MISSION: IMPOSSIBLE!"

Creating my first online course without a publisher would be Mission impossible. 🙏, @udemy!
#bloggingtips
[84/100]
"Invoking “it’s so obvious I don’t need to explain it” is not an acceptable argument."

Obvious for me doesn't mean obvious for you. And vice versa.
#bloggingtips
[85/100]
"Resist the temptation to impress your readers with “cool stuff” if you think it might confuse them."

If sth is not applicable to your online course main content, create the "extras" section, where you link your blog articles.
#bloggingtips
[86/100]
If something is not applicable for your blog's main content, create "stray" category and make use of guest blogging. Finally, social media are good to share random thoughts. #ruby #bloggingtips
hanamimastery.com/c/stray
[87/100]
Your readers often are smarter than you. If you write in a spirit to impress them, you can look silly.
#bloggingtips
[88/100]
"It feels great when someone with lots of followers tweets about the fun they had reading your book."

It feels great when you see your work is needed and people say "thank you"! to you. Especially if those are people who inspire you.
#bloggingtips
[89/100]
"You should make sure your readers will never frown while reading your book"

Hmmm, @viebel, I frowned here😅.
#bloggingtips
@viebel Mostly because I can immediately think about at least a few examples of my own video/article content where readers probably got confused.
@viebel [90/100]
"You should write the chapter introduction after all the other parts of the chapter are written."

You should read your articles after a while, even after publication, and tweak them to improve quality.
#bloggingtips
@viebel [91/100]
As your skills improve, you will see more possibilities to improve on old parts. Threat your blog as a garden, not "publish and forget"
#bloggingtips
@viebel [92/100]
"Adapting parts of your book to blog posts could be a good idea."

Blog articles are also good way to extend topics, driving your audience to your book/course, but also allowing book readers to dig even deeper into the topic.
#bloggingtips
@viebel [93/100]
"Draw your diagrams on a sheet of paper before using drawing software."

It's sooo important!
#bloggingtips
@viebel [94/100]
"Brainstorming with a friend or a colleague about a difficulty you encounter might be a productive idea."

Making articles based on notes from pair programming and brainstorming is an amazing thing.
#bloggingtips
@viebel [95/100]
Having a fallback strategy on content creation is helpful when you're running out of ideas. Example.
1. Cover all gems from the gem family.
2. Write review of each book you've read.
#bloggingtips
@viebel [96/100]
"Asking a friend or a colleague to read your work in progress is not a productive idea. The best feedback comes from people you don’t know."

I stopped pinging friends about my publications as I rarely got any useful feedback from them.
#bloggingtips
@viebel Those that gave me valuable feedback at the beginning were interested in the topic enough to follow me and give me feedback regardless of my pings.
#bloggingtips
@viebel [97/100]
"Questions that an imaginary novice would ask could be tough. Don’t ignore them. It’s an opportunity to make your book better."

There are no stupid questions except:
- are you sleeping? HEY! ARE YOU SLEEPING? Not anymore? So go to sleep, it's late!
#bloggingtips
@viebel [98/100]
When writing, focus on helping a single person. This person MAY BE YOU. Then your content is always successful.
There is a chance in 7B of people there is someone else you'll help anyway.
#bloggingtips
@viebel [99/100]
Documenting your journey from being a newbie to become an expert is priceless, as it allows you to come back to this early days mindset and always understand your audience.
#bloggingtips
@viebel [100/100]
"Writing a hundred things you learned from writing a technical book is not as difficult as it may seem."

@viebel It's amazing how hundred things others learned can trigger tons of your ideas and inspirations and help to sort out your existing thoughts.
#bloggingtips
@viebel [101/100]
I wrote probably 150 tweets since yesterday including those not numbered. What I learned is that @Twitter threads are #Weird .
A nice example of this is @avdi who publishes courses and content as #ruby guru, by using @WordPress as a backend. Nobody cares about tooling. Use what works for you.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Sebastian Wilgosz

Sebastian Wilgosz Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(