text stringlengths 0 2.35k |
|---|
**Jingle:** \[55:49\] to \[56:04\] |
**Natalie Pistunovich:** Right, so get ready, guests, we're gonna jump right on in. Jeff, what is your unpopular opinion? |
**Jeff Hernandez:** I don't know how I'm gonna top my last unpopular opinion, but... I don't know, I feel like I'll just spark a -- it's not a big unpopular opinion, but it'll start like a war... Kind of like Playstation vs. Xbox. I'm gonna go with "Dogs are the better pet than cats." I know there's lots of cat people.... |
**Sarah Duncan:** Whow... \[laughter\] |
**Jeff Hernandez:** So it'll be the unpopular opinion in this group, but... I have three dogs, and... |
**Natasha Dykes:** Okay... Those are fighting words. |
**Sarah Duncan:** \[unintelligible 00:56:38.03\] |
**Natasha Dykes:** Just put it in your next PR. |
**Jeff Hernandez:** \[laughs\] Exactly. They're fighting words, you know? |
**Natalie Pistunovich:** I've got your back, Jeff. I'm team dog. |
**Jeff Hernandez:** Team dog, all the way. Yeah. |
**Natalie Pistunovich:** Sarah, what is your unpopular opinion? |
**Sarah Duncan:** Yeah, I'll be interested to see how unpopular this is or not, but I think aspiring software engineers would be better off taking more writing and philosophy courses, and fewer computer science theory courses. |
**Natalie Pistunovich:** Yes... |
**Natasha Dykes:** Interesting. |
**Natalie Pistunovich:** No, that's intriguing. Why is that? Can we dig one level deeper? |
**Sarah Duncan:** Yeah, I think a lot about being a successful software engineer is kind of this ability to be able to make a concise argument, be able to understand other arguments and perspectives, and incorporate it, and use that to kind of revise your opinion and put forth another concise argument. We see this in a... |
\[58:16\] My sister is getting her Ph.D. in English, so I'm maybe a little biased, because I see how much work she has put into this skill... And I myself was -- my major was in the philosophy department, even though it was a logic and computer science interdisciplinary degree... So I use the skills that I got from my ... |
**Natalie Pistunovich:** Hm. Okay. Jeff... I didn't know you renamed yourself Natasha, Jeff... \[laughter\] |
**Jeff Hernandez:** I was gonna say, it sounds like you did a Go Time episode debating the value of a computer science degree vs. a dedicated software engineering... Because they're two different fields, essentially, right? |
**Sarah Duncan:** Invite me back for that one... |
**Natalie Pistunovich:** Shameless plug - I think we did one that was beating around the bush of that. I'd say a few months - maybe it was years ago - ago. Me and Kris Brandow, who's another Go Time host. We did one around English literature and its value to software engineering... But I think that was a while ago, so ... |
**Natasha Dykes:** My unpopular opinion I think might be accepted in a computer science, like this kind of circle, but who knows...? I feel like the world doesn't need another superhero movie. There's too many of them already. I'm done with it. There's so many other stories we could tell... So yeah, \[unintelligible 00... |
**Natalie Pistunovich:** There are so many more bugs that need to be superheroes. We've gotta have Beetleman, Ladybird Lady, Catterpillar Kazam! There's so many opportunities. |
**Natasha Dykes:** They could do something with the gopher... Like Gopherman, or something... |
**Natalie Pistunovich:** Gopherwoman. |
**Natasha Dykes:** Okay, yes. |
**Angelica Hill:** Sarah, I loved what you said. You gave me an idea to see my -- next time I have some free time to hack, I'm gonna use something like GPT-3 to just create a plugin for GitHub that will just run whatever you wanna say through that, to sound more empathetic and more... Something. I don't know. |
**Sarah Duncan:** I love that. |
**Angelica Hill:** By the time this episode is out, maybe it will be on the marketplace. |
**Sarah Duncan:** Incredible. |
**Angelica Hill:** This will be really, really, really useful for everyone. |
**Sarah Duncan:** Yeah, send it my way. |
**Angelica Hill:** \[laughs\] |
**Natalie Pistunovich:** Action item for everyone listening... Make it happen. C'mon. Put our heads together, we can make that happen. |
Well, it has been an absolute joy talking to you all, genuinely. I can't wait to get you all back; I have so many more episode ideas... I'm sure you do too, Natalie... I hope you have a wonderful rest of your days, but for now, adios, and goodbye. |
• Discussion about pull requests taking two episodes |
• Anderson Queiroz joins from GopherCon U.K. in London, discussing his experience with the city |
• Anderson's background in Go programming and work at Elastic |
• The concept of pull requests vs. merge requests and other names for it |
• Anderson's experience reviewing and writing pull requests at different companies and stages of their career |
• Giving feedback in pull requests through comments |
• Categorizing feedback as blockers, suggestions, or init (minor issues) |
• Using tags to clarify feedback and avoid overwhelming others |
• Balancing written feedback with in-person communication (e.g. Slack chat or call) based on situation and relationship |
• Providing positive feedback and recognition for good work |
• Considering changes to the PR process to address pain points, such as speeding up the review time |
• Pull request synchronization challenges |
• Difficulty in reviewing code changes after multiple revisions |
• Benefits of allowing multiple commits during the review process |
• Language-specific considerations for code reviews (e.g. Go conventions) |
• Importance of enforcing language-specific guidelines and team conventions |
• Adoption of new features and libraries (e.g. generics, empty interface) in pull requests |
• Review process |
• Commit history vs diff view in review |
• Commenting on code during review |
• Testing changes during review |
• Scope of change and length of PR affecting review process |
• Prioritizing understanding over perfection in review |
• PR review timelines: discussions on reasonable expectations for PR reviews, varying from within a day to a week |
• Queue management: implementation of a "column policy" to manage PRs and prevent delays, as well as creating a sense of accountability among team members |
• External contributions: handling external PRs from teams that contribute to the service, including prioritizing reviews based on importance and code consistency |
• Code conventions: importance of maintaining consistent coding conventions for external contributors |
• Waitgroups and buffering: explanations of technical concepts related to concurrency |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.