Keynote: Emails from my Grandad with Sarah Boyce

This video features Sarah Boyce at DjangoCon US 2026 in Chicago, Illinois, USA.

Keynote: Emails from my Grandad with Sarah Boyce
0:41:41
Published October 26, 2026
109 views

Code review can be a painful and anxiety-inducing experience. As developers, our work is regularly scrutinized by our colleagues. Comments about bugs, edge cases, or “code smells” are a normal part of the process, but when you’re the author, it can sometimes feel like you’re under attack.

I learned at a young age that my grandad would light up if I involved him in my work. When I told him about a presentation I was preparing, a few days later an email would arrive (often with a Word document attached titled something like “Sarah ideas” or “Sarah extra ideas”). Inside were pages of suggestions. Sometimes they were small. Sometimes they were big...

And yet, through those emails, I always felt something else: love.

In this talk I’ll explore how we receive feedback and our relationship with it. Drawing on lessons from those emails and experiences in code review and mentorship, I hope to invite you to reconsider criticism, not as an attack, but as a gift.

This talk was presented by Sarah Boyce at DjangoCon US 2026 in Chicago, Illinois, USA
https://2026.djangocon.us/talks/keynote-tuesday-emails-from-my-grandad/

LINKS:
Follow Sarah Boyce 👇
On GitHub: https://github.com/sarahboyce
On Mastodon: https://mastodon.social/@sarahboyce

Transcript

6,349 words · auto-generated · en Show

Automatically transcribed, so expect mistakes in names and technical terms.

0:14

Speaker 1: I'm super excited to be here today. So as Peter mentioned, my name is Sarah Boyce. I'm a Django Fellow. I've been a fellow for a couple of years now. That means I'm one of the uh paid contractors who are helping to maintain the Django web framework. We mostly do things like handle security reports, uh review PRs, and um Triage tickets, issue the releases, all this kind of stuff. I've also been a Django developer for a number of years, fairly unsurprising.

1:00

Speaker 1: I'm a very competitive and very enthusiastic Bummarton player. I'm a member of my local team, which is very fun. I'm also a new mum. I don't know if anyone's noticed a nine-month-old baby crawling crawling around sometimes. That's my baby. I want to thank the conference organizers for providing childcare at this conference. makes it so much more accessible for people like me. And I want to thank the sponsors as well for making that a possibility. Alright, I'm gonna start with a disclaimer. I'm gonna talk about code review a lot in this presentation.

1:45

Speaker 1: And uh I think it's worth mentioning that occasionally code review can be awful, like really, really awful. Um a former colleague of mine uh once had a situation where The experiences that he had during code review were so bad that he often had to take uh time off work from stress and anxiety from getting that kind of feedback on his um PRs. And that's not normal. Uh and nothing that I'm gonna talk about is gonna uh be relevant in those kind of situations. If you're being bullied or harassed, um the advice that I talk about is is not going to really apply. Uh

2:31

Speaker 1: fortunately in Django we have a code of conduct Dan took us through this beautifully the other day. If you are ever experiencing the kind of behavior that just doesn't belong in our community, please report it to the Code of Conduct team so that they can handle it. And hopefully that can be resolved so that you don't have these quite terrible experiences in your free time, which would be horrible. All right, with that out of the way, I'm going to talk about the star of the show, which isn't going to be Django, it's going to be uh my granddad. This is my grandad, his name is Eric. He sent this video to me and he was like, oh, you should include this in your presentation.

3:19

Speaker 1: He's turning 90 this year. Uh thank you. He thinks it's about time that someone did a presentation about him. So, you know. This is for you. And for the past ten years or so, I've been exchanging emails with him. And I will send him um some information on a piece of work that I'm doing. It could be a presentation, it might be a blog article. And then he will send me an email back telling me what he thinks. Okay. And the very first email I sent him was uh I was doing a painting at the time and he was like ah send me a picture when you're done and I'll I'll I want to see it. So this was the painting.

4:07

Speaker 1: Sent it to my granddad. And he came back to me saying, Sarah brilliant. Alright Great start. He could have stopped there. He didn't I can only offer, I hope, one constructive comment. Here we go. Okay. The reflection in the sunglasses. You took on a very difficult task. Reflection versus eyes. Brave step I'm only trying to be help.

4:52

Speaker 1: And then he sent the email like this, literally mid-sentence. I have no idea if he was gonna say something positive again at the end of it to kind of sandwich what he really thought, but And I've gone through all of these emails I've received from my granddad recently. He will often say something nice and something positive, but he will always, always, always, always tell me at least a few things that he thinks I could be doing better or what I could uh improve with that piece of work that I've just done. And now I I really love getting these emails. Um and I love them even though they are surprisingly critical. Um And I've been reflecting on why I enjoy getting them

5:38

Speaker 1: because if someone commented on my PR saying, hey, brave step I don't think I'd be thrilled. I think they'd say, oh hey, this is kind of terrible, but I can't say that, so I'm gonna say this instead. If they said, oh, this is this is interesting, I would also have a similar kind of feeling of like, oh, I think I think they're trying to hide their true feelings here. And this is interesting because as software developers, our work gets commented on all the time, right? We we go through the process of reviews all the time. And people have opinions about the work that we do, and they share those opinions with us.

6:24

Speaker 1: And especially in open source, And I'm very biased. My world is very open source right now. We don't have a lot of control about who is going to review our PR. We don't have a lot of control over how they're going to communicate with us. how often they're going to do a review. In your workplace you might have a little bit more control over this. You might have some kind of guidelines. Maybe you've talked to people beforehand about the work you're doing. But in the open source space, you kind of just get what you're given and you have to deal with it So I kind of want to talk about something we have a little bit more control over, because we don't have control over the types of reviews we get.

7:11

Speaker 1: We don't have control over How the people comment or express themselves in this slightly unusual way. But we have a bit more control over how we respond to reviews and how we then take it forward. And in particular, I want to talk about when we're struggling with the kind of comments that we've received, the ones that we're finding a bit more challenging than than usual. And then as a side note, I want to first talk about, I'm assuming that you're doing some kind of contribution to an open source project. A lot of what I'm going to talk about is going to apply in most situations, but I'm going to go with that kind of lens. And people contribute to projects for very different reasons.

7:56

Speaker 1: And uh it might be that you've done a piece of work that you're really proud of, right? And you want to get some kind of recognition about it. Um And you think that what you've done is really neat and you you're actually not that interested in how it could be done other ways because you think this is really, really cool. And that's fine. But you m in that case, you might not actually be willing to take on these changes, and you might not be willing to collaborate with the maintainers involved in the project. And I would say there are there are other things you could do other than contributing to that that project where you could release your own package, you could blog about the approach you've talked about, you could do a lightning talk, you could do a whole conference talk about it

8:41

Speaker 1: You don't have to have your code land in that kind of upstream project for you to get the recognition for what you've just done. There are other ways that you can publicize it and get recognition. Therefore, I'm now only going to talk about if you want to contribute because you actually want to collaborate with the project, you want what's best for the project, in which case Let's start talking about uh why does the project itself do code review at all? What is the goal of code review? Why do we why do we bother? Okay. And then I think the first reason is fairly obvious. Uh we want to check that the code itself works. Okay, so

9:27

Speaker 1: if you're doing some form of tickets and maybe you're fixing a bug or you're um making a new feature, if you're fixing a bug, the bug should actually be fixed It should be fixed without causing issues elsewhere. If it was a feature, it's fully implemented, it hasn't got some holes in the implementation here and there. Whatever, whatever, whatever. This is the main meat of it, right? It should actually be a viable, suitable, working solution. And that's what people are going to check in the code review. The next piece is we're checking whether it fits the project itself. So a lot of projects have kind of like guidelines about how contributions should look when it's part of that project.

10:14

Speaker 1: Django, for example, has guidelines on coding style, for example. So people will check that it conforms to those kind of guidelines. It could be that a contribution expects documentation, it expects full test coverage, etc. All of these things are checking that it fits what we want out of this contribution. And that might be beyond whether it works. Perhaps the the solution itself is fine, but for it to be part of this project, you need to do X, Y, Z, and you haven't done those things yet. And that will also come up hopefully in the code review process. Okay, also hopefully

11:00

Speaker 1: makes sense to everybody. And then the last one, which I think is also really important, is The whole another reason we are doing it in the first place is we want to go through a process of knowledge exchange. We want to make sure that the um Knowledge that exists in the original author of that change has been distributed to the wider community, to the other people who are going to contribute to the project. And if it's clear to multiple people, we hope that it's going to be clear to other people in future, and that this piece of work is going to be maintainable going forward. And that's important for a project like Django, but it might also be important at your works places and things like this because

11:47

Speaker 1: Perhaps the person who created the code may not be maintaining it going forward. When we actually get feedback that there's some issues here and there, we want to make sure that other people can fix those issues, can extend the feature when necessary in a in a an appropriate way, which without having to ask the original author because perhaps we just can't ask them. And we don't want to just revert good work because we just didn't understand it well enough. And that is another good reason that we do code Review. Oops, sorry. Oh. Okay. Sorry. All right, so now Let's discuss some

12:32

Speaker 1: some review that we've received. Okay, we've done we've opened a PR, we've received a bunch of comments, and uh perhaps it was to Django or maybe it was to some other project, but I'm very biased, so let's say it was to Django. Okay. Um and we've read through those comments and for whatever reason it's left some kind of bad taste in our mouth, where either we're frustrated or we're confused or you know, it just makes us We're struggling with this review for whatever reason. And I'm gonna lean heavily from a book, which is called Thanks for the Feedback. It's by Douglas Stone and Sheila Heen. And uh they believe that we can categorize when we are struggling with some kind of critical feedback

13:19

Speaker 1: into three categories of what's kind of triggering us, what's actually making us struggle with that feedback. And those categories are uh we're getting some kind of truth trigger, we're getting a relationship trigger, or we're getting some form of identity trigger. And I'm gonna go through each of them. So Truth. Uh this is when you've received a piece of feedback and you just disagree with it completely. You think what that what they've said is just wrong and therefore uh you know how can you take that on board? What they've said is It's completely wrong. They've done a uh perhaps they've done a comment on your PR and they said that this line of code should be X. And if you were to make that change, everything would break.

14:05

Speaker 1: You know, it's not valid. And that's really frustrating because now you have to engage with that comment itself. It's slowing you down and you feel like it's wrong. It may even be stupid, and it's it's just very annoying. And it feels like it has no value at all. And in that case, I think it's good to remember the third goal, which was we want to make sure that it's clear to other people So even if their suggestion was wrong, they came to that conclusion somehow. And perhaps other people in the community would come to a similar conclusion. And it's worth engaging in that discussion and figuring out if there is anything that we can do to

14:50

Speaker 1: make that clearer for other people. If you made that change and tests fail, you could just share, okay, here were the test failures when I do this, blah, blah, blah. And they might go, oh, hey, okay, sorry about that. In Django, for example, we have different Tests get run about different databases. It could be an honest mistake that perhaps it only fails on MySQL and they run the tests on SQLite or whatever. Easily done. But it may also mean that that perhaps it was still wrong, but no tests fail And it might be a sign that perhaps you could write another test. It could be a sign that there is still some value that could be added here. Perhaps you want to kind of cover this a bit better.

15:36

Speaker 1: Or Perhaps you need to add a bit more of an explanatory comment in your code. Or it may be that they made a mistake when writing the comment, perhaps they've written it against the wrong line of code. or they did a typo when they did it, or they just didn't explain themselves very well. And it really helps to just be a little bit open and curious about what they what they mean there. because they might have just done a mistake and there might still be value in what they're saying. It just might take a little while for you to unearth that value. The next one is is a bit juicier, I think. Um this is the relationship triggers This is, you can kind of tell you're getting a bit of a relationship trigger when you get a review from perhaps a particular person, maybe not your favorite

16:25

Speaker 1: person, and you're like, oh, you again. Or it could even feel like, oh, who who who even is this person? I'm not sure why they've come and randomly put some comments on my PR. Or um again it could even feel like who am I to question this person? This person is uh considered very high and mighty and y and you don't feel like you can engage in that review fully because th that this person person knows all. And so that's a telltale sign that this is a bit of a relationship trigger. If you've if The way that you're engaging in this review is majorly impacted by who has just given you this review, then the relationship is really coming into play here.

17:14

Speaker 1: And as I I want to mention that mergers, the people who have certain higher privileges in the projects can also make mistakes when they're reviewing your PR and you should feel confident and capable to to question what they're saying and you still engage with it in a in a way like you would engage with everybody else. It's definitely the relationship trigger that that gets me with my granddad. He's supposed to tell me that I'm wonderful and I'm talented and just give me me chocolate rather than uh send me word documentations that are several pages long about how this presentation could be better But hey. And if I got that feedback from a different person, perhaps I would engage with it differently.

18:02

Speaker 1: It's that kind of like mismatch of expectations that's that's getting me there. And there's another relationship that's kind of going on nowadays that I I don't know if other people feel this too. But we we certainly get a a feeling that perhaps it's not just the person itself, it's also our own relationship with AI and how How heavily we feel like this person is using it may impact how you feel about the kind of comments that you've received. My relationship with AI is really complicated. I both love it and hate it at the same time. And although my grandad's emails are not very clear, um and put they're quite poorly worded

18:49

Speaker 1: and he sometimes sent it like finished mid-sentence uh But i they're really human and it's quite refreshing to to see these really imperfect kind of co communication with me rather than something like super duper polished. Um Anyway, I'm getting kind of uh and you may have noticed I'm getting slightly sidetracked. I've gone on to a different topic entirely. And that's usually what happens when we've got some kind of relationship trigger. Some something feels really related, but it's slightly unrelated to the review at hand is is pulling us in that direction and then we're not engaging with the feedback that we've just received.

19:37

Speaker 1: And and I think it's worth noticing when it happens. because ideally we try to put that kind of previous experience, previous feelings aside for now. They can be a they can It's might be worth addressing these things, but probably in this PR review is not the best, most productive forum to address these problems. And as I mentioned earlier, Django does have a code of conduct. And if what you're receiving is truly problematic, you can report it, and that is a better forum to address these things rather than addressing them in the PR review itself.

20:24

Speaker 1: So that's the that's the goal here. We're trying to still get the same level of value out of the uh review itself despite where it's come from. And our relationship with the individual that's given us that review. Okay, the last trigger is the identity trigger. uh or how I prefer to call it, it's the ah it's um basically you're experiencing this when The piece of feedback you've received, it it suddenly feels a lot bigger than what it actually is. Um when you Are grounded and you're um thinking rationally, it's only a piece of feedback about one piece of work you've done out of the hundreds, maybe thousands

21:13

Speaker 1: of pieces of work that you have done or will do. And it doesn't truly reflect uh all that much on who you are as a person or who you are as a developer. Uh but if you're starting to feel like I don't belong here. I'm not good enough to do this. I'm a terrible, terrible developer. I should have known these things. That it this is this is kind of like your identity is coming. into question. And there's a few pieces of ex advice in this space. The classic is to try and develop a growth mindset where you uh take on criticism in your stride because you know that you can learn and grow all the time.

21:59

Speaker 1: But my favorite piece of uh advice is You may not be pleased with your uh what you've just done, okay? But it's worth remembering that this is just your first draft. And you could give your first draft quite a poor score. Maybe you got maybe there's a lot of issues with it. You got a lot of problems that you need to fix. But you can give yourself another score, a second score, based off how you respond from to that feedback. You can fix those problems, you can engage in with those conversations beautifully And you might still be proud of the end result that ends up landing in the project or or that that end contribution. And it's the end result that really matters. What what you first did

22:46

Speaker 1: i i it was just a means to the end and you shouldn't you shouldn't worry too much about um any mistakes that existed in that first draft. So in summary, truth. This is when uh the feedback just feels completely wrong. And you need to remember that there is an element of uh Knowledge transfer, the goal is grouped, we want this joint understanding amongst the contributing community, amongst the community of developers who are working on this project. And it's worth being curious and open that there might still be value in what this person's just said, even if it doesn't feel right to you at that moment. The next one is the relationship trigger. Like I said, we're going to try and avoid getting sidetracked by our previous

23:34

Speaker 1: experience and from that individual. And I uh I just remembered now I forgot to mention this when I was going through the slide, but it's very useful to get a neutral perspective on this. Um you can always ask A trusted individual, uh whether they think that they agree with some of the comments that they've just you've just received And that that's really nice to get that that other perspective when, especially when you're dealing with a person that You're almost blind to what this person has to say based off the past experience you've had with that individual. And finally, there's the identity trigger.

24:22

Speaker 1: And with this, we want to shrink the feedback back to size, remembering it's just feedback on one contribution that you've done out of the many that you'll do in your life. And that we can give ourselves a second score based off how we respond to that feedback, that we can still be proud of this piece of work, even if we're not proud of it initially. And I'm a little bit conscious that after all that, I do want this talk to be quite encouraging and uh uh Uh shock, I have a hidden agenda. I would love more people to do uh PR reviews to Django. And I'm slightly concerned that um We're all nice people. I don't think anybody wants to give anyone an identity crisis when they do some kind of review of their PR.

25:13

Speaker 1: But uh it would be such a shame if I've put anyone off because however hard it is receiving a review, I actually think there's another experience which is Just as bad or potentially worse, and that's receiving no review at all. This is a screenshot of the review queue to contributions in Django. And it's quite common that PRs take not days, not weeks, but months before they get another review or they get seen to at all. And I think that's quite, it's not a pleasant feeling, especially if you've spent a really long time working on this contribution. Because a review that you're struggling with

25:58

Speaker 1: is still someone investing in your work, whereas this silence means nobody has the the time or the capacity to invest in it right now. Now, why is there this really long review queue? Why is there this lack of capacity Well, in Django, we're receiving more PRs uh than ever before. Uh every month we're receiving about 75% more PRs than we used to. And the reviewing community is mostly a volunteer community, people doing it in their spare time. And that community is just simply stretched too thin. When that's we need to remember that these are mostly volunteers, it's mostly uh unpaid

26:47

Speaker 1: uh attention. And I think human attention is such a limited commodity. And with the more AI-generated PRs that we receive, against Django, but also against other open source projects as well, the more that these people are stretched thin and these kind of very long. uh waiting times are going to become more and more the norm. And that's a shame. Because I think most people would rather receive quite a imperfect maybe a bit clumsily worded review um but from a human than just have their PR sit untouched for for months Because we want somebody to look at our

27:33

Speaker 1: work. That's really part of the reason that we do it. It's part of the joy is having this kind of collaboration with our peers. And it 's the joy that I receive with the emails from my granddad. And I'm not getting these emails anymore. My granddad, unfortunately, is too poorly to engage with me in my work. And I'm misreceiving them. And it's not because all of the suggestions that he gave me were that good Or that I used all of them, or that this was such a career game changer for me. But I really miss that I could feel the care that I got from it. I could feel the care that someone's giving me that attention And they're giving me feedback on the work I've done.

28:19

Speaker 1: So next time you get a review that you're struggling with, I want you to also remember that someone in our community gave up their limited free time. to give your work this care and attention and that they're trying to collaborate with you on this piece of work. And they're sharing those thoughts with you. They've looked at that piece of work, they've thought about it, and they're sharing that with you. And when you think about it, every code contribution is the result of many different people collaborating with each other on an issue. In Django, these are people who may never meet in person.

29:05

Speaker 1: And this is this global collaboration which I think is quite beautiful, really. Djago has over 34,000 commits, and I want you to imagine how many thousands of hours have just been this exchange of people gifting attention to other people in our community. Because I think that's quite a nice thought, that our project is just a byproduct of this generous gifting of attention to other people. And there's learning and growth to be had in this in this process. Even when you get a review that's very human and it's messy and it's difficult to deal with, it's still a really nice process, and I think that's

29:52

Speaker 1: what we should remember. And so what I want to finish with is I want to finish with a a request. If you're going to the sprints at the end of the conference I instead of um perhaps working on a ticket, I would love you to uh review a PR to Django. I'd love you to gift your attention to to another person in the community. It would really help the project. Because even if you what you do is not perfect and perhaps uh you've made a look a couple of mistakes in the in the review review process itself. It doesn't really matter, I think it's still something that people can get value out of, people will appreciate,

30:39

Speaker 1: and I think that's really important. Thank you very much. You want to take any questions? I can take questions.

31:02

Speaker 2: We have a few minutes for questions.

31:08

Speaker 3: Thank you, Sarah.

31:09

Speaker 1: Hello, Will.

31:10

Speaker 3: I have a question. So you were on the reviews and triage team before becoming a fellow. Is there a way to make that team bigger? And do you think if we put more of a light on the people doing the contributions that would help them find the time? Or do you think like how do we get is it people need more attribution or I guess I'm just thinking out loud, how do we get more people to take the path that you did? And I guess sorry, to be specific, is it an attribution problem or just people just are too busy to bother?

31:40

Speaker 1: Um it's a good question. I don't know what Exactly is the the correct solution. You're right that um I do think that I mean I originally said people contribute to Django for different reasons. And I do think that the recognition that you get when you are the author of the commit is a lot more than just being a reviewer of of the piece of work that happened, even though that is a similar amount of work. And we could get better at making people we could agree that perhaps Django should have a policy that when people review a PR, they can become a co-author of the commit, right? These things are slightly complicated sometimes because

32:26

Speaker 1: there might be a little bit of policing as to what is a a valid review here because you can just randomly have a a random person in the world just randomly approve a PR saying I'm gonna get the acronym wrong, but looks good to me. No panics. And and you you go, okay, does that mean that they should be a co-author here when they've not necessarily put in the time and then blah blah blah blah. So it it can be hard Um but there is probably an element that we should try to celebrate. Uh Uh the reviewers because fundamentally nothing happens without them. And um whereas the the co-code authors get a lot more celebration, it's a lot easier to track.

33:13

Speaker 1: uh at the end of a release we usually have a like a a list of the people who were authors of commits. So it it's definitely a problem. I don't know the correct solution. But you're right, there is probably a motivation Um problem that we can try and solve. I'd be interested in hearing people's opinions. You're welcome to just chat with me about it. Yes, I can't remember if that completely answered your question. There was a couple of parts, but okay. Good enough.

33:44

Speaker 4: Thank you. Thank you, Sarah. Brief statement. Um talking about code review.

33:49

Speaker 1: Thank you.

33:50

Speaker 4: Yeah. No, joking aside, I want to add that um in addition to the uh trigger you showed us maybe it can be also um a cultural one.

34:00

Speaker 1: Yes.

34:01

Speaker 4: I remember when uh the first time I tried to contribute uh with Apple requests uh I spent months before being uh not so shy to try to open my first pull request and the blocking comment I received was about the wording I used in English.

34:19

Speaker 1: Yeah yeah

34:19

Speaker 4: And the time it was very bad. Now bad too, but at the time was worse. And uh I was struggling and to try to say please help me in that because I spent months

34:30

Speaker 1: Yeah.

34:31

Speaker 4: The technical part, I'm sure what I'm proposing.

34:33

Speaker 1: Yeah, yeah, yeah.

34:34

Speaker 4: And on the other side, people that are uh native English speaker don't realize that they were asking me something very huge for me. it's impossible to do without studying for months English and r uh rephrasing something.

34:48

Speaker 1: Yeah.

34:49

Speaker 4: So maybe sometime we can also add a cultural aspect in coding review or also on the other side people don't not have to be shy to ask for help in this type of task. It's true that Django is a English first project but uh the community is not. The vast majority of people live everywhere in the world and they don't speak English as a primary language

35:14

Speaker 1: Yeah, absolutely. And it would be such a shame for us to not have um certain contributions land uh just because the the documentation's not quite at the the standard that we want it. Um and Of course, we still want the documentation to be to be good, it's part of the thing that we're proud of in Django. But um I think there are a few things that we could be doing there. It would be nice to have more people collaborating or pairing together with a couple of people working on a single contribution. I think people find that difficult because usually even though we have a few forums like we have the Django Forum, we have the Discord.

36:00

Speaker 1: We have a few areas where people can um say, hey, I'm working on this. I'd I'd be happy to uh work on it with other people, perhaps with a English speaker who who can Help me here with a couple of these things. I don't know how successful people are at doing that. I know that the in-person events are a lot easier. to get this to be done. The sprints at the end of the conference is a fantastic way that you can just go, hey, I'm thinking about working on this. Do you want to work on one of the and they're like, yeah sure, blah, blah, blah. And you can collaborate. I think it's a good convenient time to mention that there is the Django on the Med event, which is I think each year we're hoping to do more in-person

36:47

Speaker 1: sprints. And I think that's a fantastic event which is encouraging more people to work on things together in a group because there is value to be had there. I th I would like to think that if it is just um some tweaks of some wording that uh at that point Uh we as mergers, uh often the the Django fellows, we we can we can take over once we feel like okay, if it's just here, there, whatever. Um we can uh hopefully polish some PRs with just the final tweaks to still land in um pieces of work. The

37:32

Speaker 1: only issue is that there is some limited capacity and attention. And I think it's just knowing the um Uh Django 's release timeline that we have like certain deadlines for features to get in to get in the release and certain deadlines for uh books to get in for the release. It's really valuable for a person to be strategic about when they ask for the help because uh I think if there is a feature that is really nearly there and it just needs some tweaks with the docs. coming towards the future deadline is a very good opportunity to ask for the help um because we have that motivation. We know that if we don't get it done now it's not it's not going to be in and that's a good way to try and

38:19

Speaker 1: give a strategic strategic prod uh that you might get a little bit more help at at those times. I hope that that answered part at least partially my question. Thank you. Thank you.

38:32

Speaker 5: Hi, sir, over here. Thanks. This is kind of extending Paolo's question a little bit too, but for people who might be considering taking your heeding your call to do reviews. What advice would you give people to help them in doing the review avoid triggering these three different things that you talked about for the original contributor?

39:00

Speaker 1: So in the in the book itself, part of the reason that they're talking about how we need to learn to get better at um uh receiving feedback is a lot of the advice that we give people is how to give feedback better. A lot of the advice you get is about, oh hey, there's these techniques to to give feedback better and hopefully people will listen. But usually in the process you can still upset people. And um uh I would say that it is it is Uncommon. I don't think, even though I went over a difficult review, I think if you thought about the the past 50 PRs that you you've done recently, I'd like to think that it is only a couple of them that you found challenging

39:45

Speaker 1: kind of thing. I don't think it's so common that it you're you're annoyed all the time, otherwise you're probably in the wrong career. Your life would be miserable. I think trying to be very, very clear about uh why you're saying the comment that you're saying. Um I think Trying to be as polite as possible and trying to uh bear in mind that the person may uh have a different background such as what Paolo said, and perhaps they're not a native English speaker, etc. is all really useful. So again, if you um if you're giving specific suggestions, you can also add a little bit of

40:31

Speaker 1: Curiosity or openness to show that you are willing for that person to say why they did it that way and perhaps to disagree with you. There'll be certain things where you're like, actually this isn't really a topic for debate because uh according to our guidelines we you should do XYZ. And I think it's really nice to just um link that guideline and it just to be clear and I think clear is Kind. I think you can still be you can still say things that someone needs to do, but just do so in a in a very clear and honest way. Um but yeah I wish I wish I knew I I I've not I've not done every review perfectly in my life and and uh we can handle

41:16

Speaker 1: uh you can tell when a person is upset and you can try and handle it when when And it happens. Um ,

41:25

Speaker 2: all right. Well thank you very much, Sarah.

41:27

Speaker 1: Thank you

41:28

Speaker 2: for the round of applause. Krykys.

Presenters

Conference

DjangoCon US

August 24 - 28, 2026

Chicago, Illinois, USA

Note: We understand that names change, people change, and bodies change. We respect each individual's journey and privacy. If you have any concerns about a video or need us to remove content, please don't hesitate to contact us. We will handle your request with care and promptly address any issues.

More videos by Sarah Boyce

More videos from DjangoCon US