text stringlengths 0 2.35k |
|---|
[3615.58 --> 3616.58] to just create a |
[3616.58 --> 3618.36] plugin for github |
[3618.36 --> 3619.48] that will just run |
[3619.48 --> 3620.26] whatever you want to |
[3620.26 --> 3621.76] say through that to |
[3621.76 --> 3622.94] sound more empathetic |
[3622.94 --> 3624.82] and more something I |
[3624.82 --> 3625.82] don't know but I |
[3625.82 --> 3626.50] love that by the time |
[3626.50 --> 3627.38] this episode is out |
[3627.38 --> 3628.04] maybe it will be on |
[3628.04 --> 3628.52] the marketplace |
[3628.52 --> 3629.72] incredible this will |
[3629.72 --> 3630.42] be really really |
[3630.42 --> 3632.18] useful for everyone |
[3632.18 --> 3633.04] yeah send it my |
[3633.04 --> 3633.42] way |
[3633.42 --> 3636.18] action item for |
[3636.18 --> 3636.94] everyone listening |
[3636.94 --> 3638.70] make it happen |
[3638.70 --> 3640.02] come on put our |
[3640.02 --> 3640.66] heads together we |
[3640.66 --> 3641.44] can make it happen |
[3641.44 --> 3643.08] well it has been an |
[3643.08 --> 3645.18] absolute joy talking |
[3645.18 --> 3646.22] to you all genuinely |
[3646.22 --> 3646.96] I can't wait to get |
[3646.96 --> 3647.96] you all back I have |
[3647.96 --> 3649.26] so many more episode |
[3649.26 --> 3650.64] ideas I'm sure you |
[3650.64 --> 3652.50] do too Natalie I |
[3652.50 --> 3652.94] hope you have a |
[3652.94 --> 3653.76] wonderful rest of |
[3653.76 --> 3654.82] your days but for |
[3654.82 --> 3657.00] now adios and |
[3657.00 --> 3657.52] goodbye |
[3657.52 --> 3663.66] all right that is |
[3663.66 --> 3664.32] go time for this |
[3664.32 --> 3665.24] week thanks for |
[3665.24 --> 3667.00] listening now is the |
[3667.00 --> 3667.68] best time to |
[3667.68 --> 3668.62] subscribe if you |
[3668.62 --> 3669.88] haven't yet head to |
[3669.88 --> 3671.18] go time dot fm for |
[3671.18 --> 3672.70] all the ways and if |
[3672.70 --> 3673.96] you are a regular go |
[3673.96 --> 3675.10] time listener check out |
[3675.10 --> 3676.10] our membership program |
[3676.10 --> 3677.42] directly support our |
[3677.42 --> 3679.00] work save yourself some |
[3679.00 --> 3679.92] time by ditching the |
[3679.92 --> 3681.34] ads and get bonuses |
[3681.34 --> 3682.86] like exclusive content |
[3682.86 --> 3684.82] and free stickers check it |
[3684.82 --> 3686.50] out at changelog.com |
[3686.50 --> 3687.58] slash plus plus |
[3687.58 --> 3689.12] thanks again to our |
[3689.12 --> 3690.58] partners at fastly for |
[3690.58 --> 3692.32] CD ending for us to |
[3692.32 --> 3694.02] fly.io for serving up |
[3694.02 --> 3694.96] our app to the |
[3694.96 --> 3696.00] mysterious breakmaster |
[3696.00 --> 3696.98] cylinder for these |
[3696.98 --> 3698.44] dope beats and to you |
[3698.44 --> 3699.44] for being part of the |
[3699.44 --> 3700.74] go time community we |
[3700.74 --> 3702.34] appreciate you that is |
[3702.34 --> 3703.54] all for this week we'll |
[3703.54 --> 3705.24] talk to you next time on |
[3705.24 --> 3705.90] go time |
[3705.90 --> 3724.42] hello |
• Maintaining open source code and pulling in external contributions |
• Evaluating and testing pull requests from outside contributors |
• Achieving a state of flow in software development with the right tools and information |
• Using Sourcegraph for universal code search and navigation |
• Discussing pull requests, including their complexities and challenges |
• Anderson's background and experience with Go programming language |
• His current role at Elastic working on the Elastic agent and stack |
• Pull requests: terminology, frequency of use, and implications for code review |
• The relationship between seniority and level of involvement in pull request reviews vs. writing code |
• Differences in company culture and team dynamics that affect the balance between reading and writing code |
• Reviewing vs writing code |
• Difficulty in guessing seniority from graph data |
• Balance between reviewing and writing as preferred tasks for engineers |
• Importance of code review for knowledge sharing and improvement |
• Techniques for providing effective feedback through categorization (suggestion, question, blocker) and prioritizing critical comments |
• Deciding when to use written communication vs. spoken conversation in code reviews |
• Distributed company communication methods |
• Types of feedback: writing in pull request, Slack, and calls |
• Importance of documentation and self-explanatory code |
• Giving positive feedback in PRs for junior engineers |
• Balancing error correction with praise in the review process |
• Pain points in the current PR process, including slow pace and GitHub notifications |
• The challenges of reviewing pull requests (PRs) on GitHub |
• The need for multiple commits to facilitate proper review |
• Reviewing PRs in different languages and the importance of expertise |
• Conventions specific to Go programming language, such as formatting and imports |
• The role of team conventions in enforcing coding standards |
• Common mistakes in concurrency, including misuse of channels and mutexes |
• Discussion of Go language features and their adoption rates |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.