| • Introduction and show notes for GoTime episode #28
|
| • Interview with Thorsten Ball about his book "Writing An Interpreter in Go"
|
| • Background on Thorsten Ball and his work as a software developer from Germany
|
| • The language featured in the book, called Monkey, is a fictional language created by Thorsten for educational purposes
|
| • Discussion of the value of learning about compilers and interpreters, including fun aspects and gaining a deeper understanding of programming languages.
|
| • Importance of understanding the lower-level workings of software
|
| • Abstraction leakages: how high-level abstractions can hide complexity
|
| • Benefits of learning command-line interfaces and manual tool usage
|
| • Trade-off between productivity and understanding implementation details
|
| • Value of understanding operating systems, databases, and other low-level technologies
|
| • Complexity of modern programming tools and systems
|
| • Importance of abstraction in programming
|
| • Limited time and mental capacity for learning all aspects of programming
|
| • Value of understanding low-level concepts like compilers and interpreters
|
| • Difference between compilers and interpreters
|
| • Interpreters can be thought of as compilers that execute source code in real-time
|
| • Compilers produce executable artifacts that can run independently
|
| • Grey areas between compilation and interpretation, such as just-in-time compilation
|
| • Just-in-time (JIT) compilation and its relation to compilers and interpreters
|
| • Difficulty of explaining compiler concepts due to scope and complexity
|
| • Importance of understanding assembly language, virtual machines, and bytecode for compiler development
|
| • Recommendation of the book "The Elements of Computing Systems" (Nand2Tetris)
|
| • Comparison of this book with other compiler books (e.g. Dragon Book) and its intended audience
|
| • Discussion on the need for handholding and clear explanations in technical writing
|
| • The book on Go interpreters has 200 pages of code snippets
|
| • Code in other compiler books is often outdated or pseudo-code and cannot be compiled
|
| • Author recommends typing out or following along with code to get a better understanding
|
| • There's a Coursera course available for learning about compilers and interpreters
|
| • The topic of impostor syndrome was discussed, particularly in relation to learning hardware and low-level development
|
| • Impostor syndrome and its effects on individuals, particularly in a community where others may seem more knowledgeable
|
| • The importance of self-improvement over comparing oneself to others
|
| • How conferences can perpetuate the perception that certain individuals are experts in their field
|
| • The reality behind writing books or creating complex projects, including research and revision involved
|
| • Examples of how people's perceptions can be misguided due to lack of knowledge about the process involved
|
| • Damian is the Head Gopher and has an extensive knowledge of whitepapers
|
| • The Go Blog has a survey to gather information on company use cases and adoption reasons
|
| • JetBrains has released a new IDE for Go called Gogland, which has been tested by participants
|
| • Discussion about Vim mode plugins in other editors
|
| • Conversation about using Notepad or basic text editors for coding
|
| • Syntax highlighting issues in Vim
|
| • Performance of Vim and syntax highlighting
|
| • Potential benefits of disabling syntax highlighting
|
| • Shout-outs to various projects:
|
| + Buffalo Web Framework by Mark Bates
|
| + Vim Go plugin by Fatih Arslan
|
| + gitQL, a Git query language tool written in Go
|
| • Sponsor shoutout to Backtrace and StackImpact
|
| • Promotion of show's social media handles (Twitter and GitHub) for guest inquiries or questions |
