Live data from Hacker News

Show HN: I wrote a book about Go

practical-go-lessons.com

121–130 of 160 posts

Re: Show HN: I wrote a book about Go

#121
This is fantastic. I just learned the basics of Go by building an SDK for a friend’s REST API. I’ll tell you what, you want to learn a language, build a client SDK. You’ll hit so many crazy issues, you’ll be forced to learn how things work.

That said, I’ve got a long ways to go, and I’ve already plowed through six chapters of the book. Nice work!

Re: Show HN: I wrote a book about Go

#122

Hello all, After 2.5 years of writing, countless weekends and evenings, I released a book about the Go programming language. The book is available for free on the website because I wanted to give something back to the developer's community :) It is composed of 700+ pages, 41 chapters, and approximately 405 drawings/screenshots. I tried to cover all the important topics that a new Go programmer should know. At the end…

A very minor point (sorry): please could you search-and-replace all “advices” to “advice” in the text? Advice is its own plural form.

I just pushed a new release with that fix

Re: Show HN: I wrote a book about Go

#123
post #109

Earlier quoted context omitted.

I will take a look at it, thanks for your suggestion. I will check if Lyx has an option to export to this format.

MkDocs isn't a "format" as such. It requires you to write Markdown and then configure the mkdocs.yml file to define the website's properties, such as the navigational structure.

Thanks for this clarification I will check this.

Re: Show HN: I wrote a book about Go

#125

This is fantastic. I just learned the basics of Go by building an SDK for a friend’s REST API. I’ll tell you what, you want to learn a language, build a client SDK. You’ll hit so many crazy issues, you’ll be forced to learn how things work. That said, I’ve got a long ways to go, and I’ve already plowed through six chapters of the book. Nice work!

Thanks jhunter1016 ! This is so true, My first Go program (for work) was to build a web server and it was so intense :)

I'm happy that you like the book

Re: Show HN: I wrote a book about Go

#126

Hello all, After 2.5 years of writing, countless weekends and evenings, I released a book about the Go programming language. The book is available for free on the website because I wanted to give something back to the developer's community :) It is composed of 700+ pages, 41 chapters, and approximately 405 drawings/screenshots. I tried to cover all the important topics that a new Go programmer should know. At the end…

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?

Re: Show HN: I wrote a book about Go

#127
post #126

Hello all, After 2.5 years of writing, countless weekends and evenings, I released a book about the Go programming language. The book is available for free on the website because I wanted to give something back to the developer's community :) It is composed of 700+ pages, 41 chapters, and approximately 405 drawings/screenshots. I tried to cover all the important topics that a new Go programmer should know. At the end…

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 p…

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

Post reply on HN