ryancheley / djangocon-us-2023 Goto Github PK

Just some preliminary stuff since I don’t have my computer with me

• I’m personally not a big fan of the emojis, but that may be an age thing, I would ask someone whose more in line with whose going to the conference about that, but I personally found it kinda cringy

• For bullet points, I recommend spacing them out so that they look like this:

• blah blah blah

• blah. It takes up more space and makes it look cleaner

• you may need to make your font bigger on the bullet points

• stay consistent.

  • Either use full sentences or clauses.
  • Either use periods or don’t

1. Does the intro story about Mt. Whitney make sense to keep? I'm trying to convey that sense that the community surrounding you when you do a hard thing can make all of the difference in the world, and I'm not 100% sure that I'm getting that message across

• Yes, keep it. I would change how you present it though. You don't have to say "And what does this story have to do with contributing to Django? Stay until the end to find out 😀", it's implied. Especially if you were to start with your title slide, then go straight to the story, then follow with explaining your title slide.

• I would also want to know a bit more about your trip: is the photo yours from near the summit? What year was it, and have you had time to re-prepare and do a similar hike since? Have you been turned off hiking completely? Were you able to make it the 7 days back out again? Having one photo while describing the story in text is fine. When you bring it back, having the same photo helps bring back the topic, and if there was a future hike you were successful on, or even planning for, add a second photo.

2. Does the presentation flow from your perspective?

• Mostly, yes. I can see you trailing off at the end, so I can't see the full narrative yet.

3. Are my slides with only a single word on them too little?

• They're fine, but at the moment you have ~10 seconds of words in the notes. For the date slides, I'd do something like a progressive introduction, like striking out the dates and adding new dates at the bottom, rather than replacing all context. For some of your later slides (24-29) it works a bit better, but see my answer for 5 for more.

4. The section where I try to encourage people to contribute to Django by saying "It's just Python" ... I'm trying really hard to not turn people off, and I'm concerned that by saying, "It's just Python" some people might not appreciate it, but since it's DjangoCon maybe I'm too worried about it 🤷‍♂️

• I've had the same realisation, and it was an epiphany for me. I think it's important.

• I would also focus on how you tried to solve the one problem, and after focusing on the one bug, at the tail of your story, share that this was x months ago, and since you've helped with Y bugs and closed Z of them, or whatever (your slides are still very sparse so I don't know the end of the story)

5. Is there enough emoji in the presentation 😀?

• From q3: if you wanted to add more, you could add emoji for 24-29 instead of words, but words are also fine.

6. Anything else you see that you're like, wow that's good, or, maybe stay away from that would also be helpful.

• You include many QR codes that imply you want people to scan them, but based on the notes they're barely on screen enough to take a photo. You have links at the end I presume you want people to follow, but any QR codes you include throughout should be on the last slide. If, after doing this, you find there's too many QR codes, then you have too many QR codes. Having some sort of blog post QR code ready to go with a collection of all the links would help.

• You also have many screenshots of various sizes, resolutions, etc. Having consistency is useful, but you're also presenting a lot of text on screen and people will try and read it all. If you want people to read stuff, include the important stuff, either by only including the good words, fuzzing out the unimportant stuff, etc. If I have many many screenshots in the same CSS style I tend to be a bit fancy and make slide templates where I can replicate the CSS style in text, which helps readability for slides, but I'm a bit extra.

• I also imported these slides into Google Slides, and half your speaker notes were unreadable in light grey color. This will be handled in #4

• Your Paulo photos are also super fuzzy and I can't tell which one is you.

• Results of Research needs more context for each of the bullet points. potentially one slide per current bullet point
• maybe have the diff of the PR from Nick to give a better idea of what he suggested
• slide 78 add emoji
• Still only at 25 minutes

A dry run version of the presentation was give on Friday September 8th with the Web Dev team (Chris, Jason, and Jon)

Feedback:

• make sure to indicate what 'the bird site' is (i.e. state Twitter)
• I was talking too fast at the start
• need to add more context for the slide (Nick Pope's feedback on Slide 51)
• expand on regular expressions. show example of why it was a bad idea based on the feedback from Shia and Simon
• more details on other contributions (this is similar to Feedback that Katie gave)
• more details on what happened with the bug
• add more to introduction
• include work with Django at DOHC
• the positivity of the experience is really good, but maybe there can be more?

Per #2 there seemed to be an issue with the slide notes when imported into Google Slides. I’ll need to investigate this further

Make sure that the following formatting has been applied:

• headers are consistent in color, font, and size
• body is consistent in color, font, and size
• code is consistent in color, font, and size, and background color

headers

• font-family: Calibi
• font-size: 66
• font-color: sRGB IEC61699-2.1

body

• font-family:
• font-size:
• font-color:

code

• font-family: Inconsoloata NF
• font-size:
• font-color:
• code block background color

• Starting at the "Working on the Ticket" (currently slide 26) need to add screenshots of the Trac conversation
• add screenshots of the public notes as well (starting after the "5. Write" slide)
• Get the title of Simon's Talk from Django Con US 2023 and add it to the "5. Write" slide)
• Add what you learned from each of
  • Nick
  • Shia
  • Simon
  • Mariusz