Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Writing an Interpreter in Go: The Paperback Edition

thorstenball.com

Post reply on HN
Print view View original

21–30 of 78 posts

Re: Writing an Interpreter in Go: The Paperback Edition

#21

Post by misternugget »

zerr wrote: post #19
happy-go-lucky wrote: post #17

Earlier quoted context omitted.

My belief is that writing about a topic that one is trying to come to grips with helps ensure they achieve the best possible learning outcomes.

The best learning outcomes for the author I believe. But I'm more interested in the prospective reader's PoV.

I recently read a comment (I think it might have been on HN, but I can't find it) that said something like this: if you recently learned/mastered a topic, you're in a far better position to teach that topic than an expert, who's so deep into it, that they can't understand the beginners.

I wish I could find the source for this, because it was much better put, but that comment contains the gist of my motivation behind writing the book.

Re: Writing an Interpreter in Go: The Paperback Edition

#24

Post by andrewbinstock »

misternugget wrote: post #21
zerr wrote: post #19

Earlier quoted context omitted.

The best learning outcomes for the author I believe. But I'm more interested in the prospective reader's PoV.

I recently read a comment (I think it might have been on HN, but I can't find it) that said something like this: if you recently learned/mastered a topic, you're in a far better position to teach that topic than an expert, who's so deep into it, that they can't understand the beginners. I wish I could find the source for this, because it was much better put, but that comment contains the gist of my motivation behind…

The great benefit of experts over I-just-learned-this authors is that experts know how design x or feature y relates to other designs and features not implemented in the given project.

In other words, they know a lot more context and can tell whether something that appears totally normal in the project is actually done in an unusual way that has limitations, etc.

Re: Writing an Interpreter in Go: The Paperback Edition

#27

Post by fnord123 »

misternugget wrote: post #21
zerr wrote: post #19

Earlier quoted context omitted.

The best learning outcomes for the author I believe. But I'm more interested in the prospective reader's PoV.

I recently read a comment (I think it might have been on HN, but I can't find it) that said something like this: if you recently learned/mastered a topic, you're in a far better position to teach that topic than an expert, who's so deep into it, that they can't understand the beginners. I wish I could find the source for this, because it was much better put, but that comment contains the gist of my motivation behind…

The comment is probably correct. There is a concept called "the curse of knowledge" which is basically the same issue.

Re: Writing an Interpreter in Go: The Paperback Edition

#28

Post by roberte3 »

xenihn wrote: post #22

I will definitely be grabbing a copy of this and going through it, thanks!. Anyone have recommendations for a book or tutorial for creating a REST API with Go?

This book is a pretty good tutorial on getting web service with rest up and running. https://www.manning.com/books/go-web-programming

Re: Writing an Interpreter in Go: The Paperback Edition

#29

Post by happy-go-lucky »

misternugget wrote: post #21
zerr wrote: post #19

Earlier quoted context omitted.

The best learning outcomes for the author I believe. But I'm more interested in the prospective reader's PoV.

I recently read a comment (I think it might have been on HN, but I can't find it) that said something like this: if you recently learned/mastered a topic, you're in a far better position to teach that topic than an expert, who's so deep into it, that they can't understand the beginners. I wish I could find the source for this, because it was much better put, but that comment contains the gist of my motivation behind…

> if you recently learned/mastered a topic, you're in a far better position to teach that topic than an expert, who's so deep into it, that they can't understand the beginners.

Most experts I come across are generous when it comes to sharing what they know and their generosity may sometimes get in the way of a beginner's learning, but this is not always the case.

Re: Writing an Interpreter in Go: The Paperback Edition

#30

Post by msie »

misternugget wrote: post #21
zerr wrote: post #19

Earlier quoted context omitted.

The best learning outcomes for the author I believe. But I'm more interested in the prospective reader's PoV.

I recently read a comment (I think it might have been on HN, but I can't find it) that said something like this: if you recently learned/mastered a topic, you're in a far better position to teach that topic than an expert, who's so deep into it, that they can't understand the beginners. I wish I could find the source for this, because it was much better put, but that comment contains the gist of my motivation behind…

Completely agree. Currently reading a book authored by the creator of a framework and having a hard time of it. So many newbie questions. There is extra stuff I don't need to know as a beginner - put that in another book or another section. Don't interleave it with the basic material. There is stuff that make assumptions that I am an expert in the language, the code needs to be fully explained, line by line.
Post reply on HN