text stringlengths 0 2.35k |
|---|
**Kris Brandow:** \[56:04\] Yes. Or as I like to call it, queer new year. \[laughter\] We can't be contained to a month, so this is like the beginning of it, especially in the US too, because I think people have this assumption that's like, "Hey, Pride month is June, and there's Pride in June." I'm like, "No, no, no. T... |
**Natalie Pistunovich:** And for those who don't know what's whitewashing? |
**Kris Brandow:** So whitewashing is-- I guess it's easiest to describe it with an example, something that prominently happens in Hollywood, where you're casting a movie where the cast should be predominantly Asian, yet somehow, all of the main characters are white people. That's whitewashing. So it's just like, "Oh, w... |
The same thing usually happens where all these companies that very much do not support queer rights and any other month of the year comes around and they're just like, "Hey, we like queer people. We're going to celebrate you now. Here's a bunch of discounts." And then there's this perfect-- I don't know if it started o... |
**Natalie Pistunovich:** So maybe another follow -up question... For companies who do think how to celebrate queer new year, what would be a better thing to do, other than just changing your logo to something within a Pride flag? |
**Kris Brandow:** There's always the monetary support you can give to organizations that help queer people, especially queer youth, especially trans youth, people in danger, so things like donating to Trevor Project are immensely helpful. |
**Natalie Pistunovich:** We'll add links at the end of the notes for those who listen. |
**Kris Brandow:** But yeah, I think it's just like, if you're doing it so that you get recognition for it, I think you're just doing it for the wrong reasons, and I don't know if there's anything at the end of the day that will help fix that or repair that. I don't know. |
I remember I was working at one company and there was this thing that happened that was basically supporting anti-queer organizations, and a lot of employees were like, "We don't feel great about this." And one employee was like, "Hey, how about we take all of the money we get from these anti-queer organizations and we... |
**Natalie Pistunovich:** Yeah. |
**Kris Brandow:** I mean, we're going to have to retitle this episode like "Gay Time" or something, because this-- |
\[laughter\] |
**Natalie Pistunovich:** Special edition for Queer New Year. |
**Kris Brandow:** Yes, exactly. Happy Queer New Year, everybody out there. We'll put lots of rainbows around it. |
**Natalie Pistunovich:** Can you somehow-- I'm missing like one or two links, but something about generics and being gender fluid... |
**Kris Brandow:** Oh... |
**Natalie Pistunovich:** There must be something there, right? \[laughs\] It fits all sorts of things. |
**Kris Brandow:** Generics, a new feature rolled out for our generically-gendered friends out there. It's like, your gender doesn't have to be static. It can be whatever you want it to be. |
**Natalie Pistunovich:** And it's fine if your decision is different from the decision of your language of choice. |
**Kris Brandow:** Okay, we're down a rabbit hole now. \[laughter\] We're drinking tea with the Mad Hatters... |
• What is GraphQL |
• Solution to classic difficulties of REST APIs (query language for fetching data and spec for implementing GraphQL servers) |
• Nested queries and fields (client can select specific fields needed) |
• Normalizing data (client doesn't have to select field if not needed) |
• Server-side work vs client-side work in GraphQL |
• Comparison with REST APIs (baked-in nested resources, query complexity) |
• GraphQL's complexity on the client-side is manageable with libraries like Mat Ryer's Machine Box GraphQL client library |
• Server-side implementation of GraphQL can be complex due to resolving data and handling nested fields |
• gqlgen is a server library that helps generate resolver functions for each field in the schema |
• Client libraries can simplify query generation, such as shurcooL's GraphQL client which uses struct tags to generate queries |
• GraphQL allows for optional resolvers and reduces complexity on the client-side by allowing clients to request only the necessary data |
• Server implementation of GraphQL requires handling database interactions, including joins in SQL databases or document databases |
• GraphQL is beneficial for solving problems related to API design, such as reducing the number of requests needed from clients and making it easier for frontend developers to modify queries. |
• Problem of deciding what data to load when using a public API |
• Comparison between GraphQL and SQL for simplicity and complexity |
• Discussion of empowering clients with flexibility in querying data |
• Mention of alternative approaches like Remix and static query rolling |
• Trade-offs between client empowerment and potential performance losses |
• Strategies for optimizing queries and protecting against denial of service |
• Discussion of GraphQL features and benefits |
• Complexity approach for public APIs with complexity limits instead of rate limits |
• Federation in GraphQL and its implementation |
• Data structure impact on query performance |
• Schema-first libraries like gqlgen and their benefits |
• Importance of API design and documentation |
• Comparison between GraphQL and JSON APIs |
• GraphQL is a typed language that encourages designing schemas to clearly define data types |
• The challenge of matching client and server types was overcome by writing a code generator (genclient) that creates correct Go types from the schema |
• Having both server and client use type systems allows for better collaboration and error checking across the stack |
• GraphQL's benefits extend beyond just small projects, including improved confidence in API design and evolution |
• The relationships and traversability capabilities of GraphQL are particularly useful for modeling complex data structures |
• When to start using GraphQL: wait until REST becomes frustrating due to complexity and scalability issues |
• Benefits of GraphQL: simplifies data retrieval, reduces complexity, and improves query flexibility |
• Relational data: most data has relationships between entities, making GraphQL valuable for querying related data |
• Public APIs: releasing a GraphQL API may deter some developers due to learning curve and increased cognitive effort |
• Federation: a method for connecting multiple services and allowing them to work together seamlessly |
• Automation: manually doing tasks first can lead to better understanding of the problem and more effective automation later on |
• Developers often make the mistake of trying to automate tasks unnecessarily |
• Automation can be part of a solution, but not always the best approach for every task |
• Union types in programming languages would be a useful feature |
• Running fiber internet is ideal, but may not be feasible for everyone |
• ISPs and rural internet infrastructure can be unreliable and frustrating |
• The hosts discuss the topic of internet speed, with Mat Ryer joking that a slow connection is only possible if people use it. |
• Jon Calhoun shares an anecdote about his uncle who worked at Comcast and joked about the internet getting slower as users moved back to a particular town. |
• The idea of "phoning someone's uncle" for an interview or discussion segment is introduced, with Mat Ryer suggesting they do this in a future episode. |
• The conversation touches on the potential for uncles to have unpopular opinions and interesting views. |
**Jon Calhoun:** Hello, and welcome to Go Time. Today we're gonna talk about GraphQL, and we are joined by two guests. The first is Mark Sandstrom. Mark is an engineer on the platform infrastructure team at Khan Academy. Mark, how are you? |
**Mark Sandstrom:** I'm great, thanks. |
**Jon Calhoun:** Well, thanks for joining us. Our other guest is Ben Kraft. He is the creator of the genclient, and he also used to work on the platform and infrastructure team at Khan Academy. Ben, how are you? |
**Ben Kraft:** Doing well, thanks. |
**Jon Calhoun:** Awesome. Well, hopefully Ben's internet sticks with us... We've had some issues before we've started, so if he cuts out, keep that in mind. Alright, so let's go ahead and just jump in... |
**Mat Ryer:** I'm here too, Jon... |
**Jon Calhoun:** Mat, you want me to introduce you? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.