[lamida]

Hi, Maximilien. I really like the structure of the books. It starts with "what we will learn" and ends with "test yourself" and key takeaways. The structure can help the reader to really conscious in understanding the learning goals and validating the understanding.

I also always want to write a programming language book or some other technical topic book in general, which the writing process will I use as learning process for myself. But I always wonder in deciding the topic to cover. How do you decide the topics to cover? Do you start from following existing books or online documentation topic sequences? Or just write whatever topic you are interested first and structure the content afterward?

[maximilienandi]

Thanks for your comment ! If you want to do it, just pick a language and start to write.

Writing is not easy but it becomes easier if you transform it into a habit.

In my experience I forced myself to write regularly like every day of the week. I usually worked one hour approximately by session.

By doing so you will see that you will achieve a lot.

Do not force youtself to write for one entire day then do nothing for a week.

Concerning the topics to cover I will recommand using a mind map to build the table of content. This is interesting because you can drag and drop sections easilly.

I would suggest first to define your targeted audience. Having this audience you can begin building the plan.

My approach was to teach notions progressively. Sometime I needed to rework the sections order. Use an editor that allow you to do that easilly like Lyx (love it).

Students generally love rituals and adding some introduction ritual/section and conclusion section is a plus.

Hope those recommendations will help you :)

Writing something is really a great way to make sure you understand something !

Good luck