text stringlengths 0 1.82k |
|---|
• 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 |
**Erik St. Martin:** We are back for another episode of GoTime. This episode is number 19. Today on the show we have myself, Erik St. Martin, we have Carlisia Campos also here... |
**Carlisia Thompson:** Hi ! |
**Erik St. Martin:** ...and Brian Ketelsen... |
**Brian Ketelsen:** Hello! |
**Erik St. Martin:** ...and our special guest today is none other than Katrina Owen. |
**Katrina Owen:** Hello! |
**Erik St. Martin:** Why don't you go ahead and give everybody a little bit of background about yourself before we get started. |
**Katrina Owen:** I work as a developer advocate at GitHub on the open source team there. I do a lot of community stuff - I go to conferences, meet people, and a lot of open source work. I have a project named exercism.io, which is a platform for practicing programming in a number of different languages, including Go. |
**Erik St. Martin:** Yeah, Exercism has been taking off recently. I look probably like two weeks ago and was completely astonished by the number of languages that are supported there now. |
**Katrina Owen:** Yeah, we hit 32, which was kind of a big number - two times two, times two, times two, times two, I think... \[laughter\] We passed that a few weeks ago when we launched I believe MIPS Assembly, which was kind of cool. |
**Brian Ketelsen:** So is there big deband for MIPS Assembly? |
**Katrina Owen:** It turns out that Assembly language courses at universities often use a textbook that uses MIPS Assembly. |
**Brian Ketelsen:** Ah-ha! |
**Erik St. Martin:** Interesting. I would actually like Assembly, because... I mean, most Assembly books that I've read or seen are very much documentation and not "How do you write idiomatic Assembly?" I don't think anything I've looked at with Assembly does more than teach you the individual instructions and what the... |
**Katrina Owen:** It is pretty cool. |
**Erik St. Martin:** And all my free time to learn new languages... \[laughter\] |
**Katrina Owen:** A language a year. You've got the next 33 years all laid up for you. |
**Erik St. Martin:** Right, but by then, how many new languages will you have? |
**Katrina Owen:** Yeah, that's the problem. |
**Brian Ketelsen:** Yeah, your hockey stick growth is slowing us down, I can't live that long. |
**Carlisia Thompson:** Actually, I just remembered that a lot of people and myself included keep wondering what is idiomatic Go, because there is no such thing as a listing of what idiomatic Go is, and it sounds like it's a mythical thing to me. Exercism actually guides you through that. The comments that you get back ... |
**Erik St. Martin:** So let's actually step back for a second for anybody who's not familiar with Exercism.io. Do you wanna give a brief introduction to what that is, Kristina? |
**Katrina Owen:** Sure. It's basically a platform for practicing. It's different from a lot of other places where you do coding challenges and katas in that there is not competition; you're not competing with anyone, there's no leaderboard, there are no prizes or badges or anything like that. This is really about the d... |
**Erik St. Martin:** \[04:24\] This is basically bite-sized problems to be solved that you submit and then are reviewed by people who have more experience in the language, that kind of guide you through how you might do that. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.