| • Background of guest Katrina Owen
|
| • Exercism.io platform for practicing programming in multiple languages, including Go
|
| • MIPS Assembly language support and its use in university courses
|
| • Idiomatic Go and learning patterns from examples
|
| • Exercism's non-competitive approach to coding challenges and katas
|
| • Feedback and review process on Exercism
|
| • Importance of emotional support and positive reinforcement in code reviews
|
| • Asymmetry between wanting feedback and giving feedback in open-source communities
|
| • Code review as a learning experience
|
| • Importance of empathetic and constructive comments in code review
|
| • Recognizing the difference between intentionally rude comments and those resulting from lack of knowledge or practice
|
| • The difficulty of solving problems, vs. refining existing solutions
|
| • Value of human feedback in simplifying complex code
|
| • Refactoring as its own skill set, requiring a fresh perspective
|
| • Importance of taking small steps when refactoring to avoid "commit bombs"
|
| • The benefits of using a statically typed language like Go for safety and predictability
|
| • Exercism: submitting exercises, helping with reviews, and contributing to the GitHub repository
|
| • Katrina Owen's GopherCon talk on breaking into the Go language
|
| • Idiomatic Go: resources such as the Effective Go document and Google's code review comments section
|
| • Learning and teaching programming effectively, avoiding barriers for people to learn
|
| • Importance of breaking down complex tasks into small wins
|
| • Overwhelming new programmers with too many concepts at once
|
| • Need for mastering basic tools such as text editors and Git
|
| • Difficulty in determining the order to teach various topics
|
| • Importance of Linux knowledge, SSH, firewalls, and security basics
|
| • Evolution of web development requiring knowledge of protocols like HTTP and TLS
|
| • Potential for using Exercism-style exercises to learn systems-level concepts
|
| • The importance of reading error logs and not making assumptions when trying to solve coding problems
|
| • How it takes experience and self-discipline to learn to prioritize debugging over searching for solutions online
|
| • Avoiding pre-planning learning flow by only researching and learning new things when necessary, such as when encountering an error or due to curiosity
|
| • The benefits of GraphQL APIs, specifically in reducing the N+1 problem when making multiple API requests
|
| • Using GitHub's GraphQL integration to design queries upfront and retrieve relevant data in a more efficient way
|
| • Developing a tool to provide feedback and analytics for maintainers of open-source projects
|
| • Using GraphQL APIs to improve scalability and data accuracy
|
| • Creating a checklist or dashboard for contributors to assess project health
|
| • Identifying unhealthy behavior in issue closures, such as dismissing issues without responses
|
| • Discussing the challenges of contributing to large projects and the need for tools to help manage open-source workloads
|
| • Sharing news and announcements, including congratulations on a new baby and showcasing creative uses for Go programming (e.g. the Primitive project)
|
| • Discussion of a tool to create animated GIFs from pictures
|
| • Promotion of Go language and its potential in university courses
|
| • Introduction to Better Go Playground Chrome Extension
|
| • Overview of Gallium framework for building native web apps in Go
|
| • #FreeSoftwareFriday feature on Go and its contributions to Brian Ketelsen's work
|
| • Project stalled due to lack of bandwidth
|
| • Discussion on Exercism and its benefits
|
| • Praise for GoConvey, a testing tool with features such as code coverage tracking and browser notifications
|
| • Concerns about gamifying code coverage and the potential for meaningless tests
|
| • Importance of writing meaningful tests and the benefits of fast test times in Go
|
| • Discussion on mocking and stubbing techniques to facilitate testing
|
| • Mention of a project (Qpid) to automate barbecue grilling using Raspberry Pi and electronics
|
| • Project updates, including Erik St. Martin's work on Bosun, a monitoring library
|
| • Discussion of Kubernetes monitoring and alerting using a specific tool
|
| • Shout out to the Hoodie team for their open source community management and tools
|
| • Comparison of Katrina's approach to community building with Jan Lehnardt from Request for Commits episode #4
|
| • Brief discussion of Exercism and its community engagement strategies
|
| • Wrap-up and closing remarks, including thanks to listeners and sponsors |
