惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

L
Lohrmann on Cybersecurity
Martin Fowler
Martin Fowler
Engineering at Meta
Engineering at Meta
腾讯CDC
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Microsoft Azure Blog
Microsoft Azure Blog
G
Google Developers Blog
TaoSecurity Blog
TaoSecurity Blog
博客园_首页
Vercel News
Vercel News
Hugging Face - Blog
Hugging Face - Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
Last Week in AI
Last Week in AI
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
T
The Exploit Database - CXSecurity.com
量子位
Project Zero
Project Zero
A
Arctic Wolf
小众软件
小众软件
NISL@THU
NISL@THU
C
CERT Recently Published Vulnerability Notes
有赞技术团队
有赞技术团队
MongoDB | Blog
MongoDB | Blog
博客园 - 聂微东
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
N
News and Events Feed by Topic
宝玉的分享
宝玉的分享
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
T
Troy Hunt's Blog
P
Privacy & Cybersecurity Law Blog
Security Latest
Security Latest
B
Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
D
DataBreaches.Net
Schneier on Security
Schneier on Security
The Hacker News
The Hacker News
K
Kaspersky official blog
C
Check Point Blog
Hacker News: Ask HN
Hacker News: Ask HN
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Webroot Blog
Webroot Blog
www.infosecurity-magazine.com
www.infosecurity-magazine.com
人人都是产品经理
人人都是产品经理
AI
AI
Cisco Talos Blog
Cisco Talos Blog
MyScale Blog
MyScale Blog
Cloudbric
Cloudbric
B
Blog RSS Feed
S
Schneier on Security
P
Palo Alto Networks Blog

CSS Wizardry

Front-End’s Missing Metric: The TBT Window Meet Your Users Where They Are with Obs.js Better Browser Caching with No-Vary-Search font-family Doesn’t Fall Back the Way You Think What Is CSS Containment and How Can I Use It? When All You Can Do Is All or Nothing, Do Nothing Obs.js: Context-Aware Web Performance for Everyone Low- and Mid-Tier Mobile for the Real World (2025) The Fastest Site in the Tour de France Making Sense of the Performance Extensibility API Why Do We Have a Cache-Control Request Header? HTML Is Not a Programming Language… Build for the Web, Build on the Web, Build with the Web Licensing Code on CSS Wizardry A Layered Approach to Speculation Rules Designing (and Evolving) a New Web Performance Score Core Web Vitals Colours The Ultimate Contract Templates for Tech Consultants: Protect Your Business and Get Paid Optimising for High Latency Environments Cache Grab: How Much Are You Leaving on the Table? blocking=render: Why would you do that?! Correctly Configure (Pre) Connections The Three Cs: 🤝 Concatenate, 🗜️ Compress, 🗳️ Cache What Is the Maximum max-age? How to Clear Cache and Cookies on a Customer’s Device The Ultimate Low-Quality Image Placeholder Technique Core Web Vitals for Search Engine Optimisation: What Do We Need to Know? The HTTP/1-liness of HTTP/2 In Defence of DOM­Content­Loaded Site-Speed Topography Remapped Why Not document.write()? Speeding Up Async Snippets Critical CSS? Not So Fast! Measure What You Impact, Not What You Influence Optimising Largest Contentful Paint Measuring Web Performance in Mobile Safari Site-Speed Topography Speed Up Google Fonts Real-World Effectiveness of Brotli Performance Budgets, Pragmatically Lazy Pre-Browsing with Prefetch Making Cloud.typography Fast(er) Time to First Byte: What It Is and How to Improve It Self-Host Your Static Assets Tips for Technical Interviews Cache-Control for Civilians Bandwidth or Latency: When to Optimise for Which ITCSS × Skillshare What If? CSS and Network Performance The Three Types of Performance Testing Getting to Know a Legacy Codebase Image Inconsistencies: How and When Browsers Download Images Identifying, Auditing, and Discussing Third Parties My Digital Music Setup Measuring the Hard-to-Measure Finding Dead CSS The Fallacies of Distributed Computing (Applied to Front-End Performance) Ten Years Old Relative Requirements Airplanes and Ashtrays Performance and Resilience: Stress-Testing Third Parties Refactoring Tunnels Little Things I Like to Do with Git Writing Tidy Code Configuring Git and Vim Base64 Encoding & Performance, Part 2: Gathering Data Base64 Encoding & Performance, Part 1: What’s Up with Base64? Code Smells in CSS Revisited Typography for Developers Moving CSS Wizardry onto HTTPS and HTTP/2 Ack for CSS Developers A New Year, a New Focus Preparing Vim for Apple’s Touch Bar Choosing the Correct Average CSS Shorthand Syntax Considered an Anti-Pattern CSS Wizardry Newsletter Nesting Your BEM? Improving Perceived Performance with Multiple Background Images Continue Normalising Your CSS Pure CSS Content Filter Pragmatic, Practical, and Progressive Theming with Custom Properties Refactoring CSS: The Three I’s Improving Your CSS with Parker The Importance of !important: Forcing Immutability in CSS Mixins Better for Performance Managing Typography on Large Apps White October Events Workshop Partnership BEMIT: Taking the BEM Naming Convention a Step Further Travelling Like You Want to, When You Have To Contextual Styling: UI Components, Nesting, and Implementation Detail Subtleties with Self-Chained Classes Cyclomatic Complexity: Logic in CSS Immutable CSS Can CSS Be Too Modular? More Transparent UI Code with Namespaces When to use @extend; when to use a mixin The Specificity Graph CSS Wizardry Ltd.: Year 1 in review CSS Guidelines 2.0.0
Speaker’s Checklist: Before and After Your Talk
Harry Roberts · 2016-06-21 · via CSS Wizardry

Written by on CSS Wizardry.

Table of Contents

Independent writing is brought to you via my wonderful Supporters.

  1. Before the Talk
  2. After the Talk

I’ve been speaking at conferences for just over four years now, and have spoken at 14 in the past five months alone. It helps me (and indeed anyone) to have a pretty regimented checklist of things to do before and after your talk in order to help things run as smoothly as possible.

This post isn’t intended to help you research, write, prepare, or deliver a talk well—that’s an entire series of blog posts in itself—but it should help you to run things a little more consistently and predictably. There’s nothing worse than being stressed out before a talk.

Before the Talk

  • Follow the conference on Twitter. You can see any last minute logistical announcements or changes in real time. It also allows the conference to DM you if they need to.
  • Turn up well ahead of time. Turn up at least the break before your slot. Ideally—really—you’ll arrive first thing in the morning and be present for the entire event, but at the very least you need to arrive with enough time to test your slides, familiarise yourself with the venue, etc.
  • Let the organiser know you’ve arrived. Being a speaker is stressful; being an organiser is doubly so. As soon as you arrive, go straight to your main point of contact and let them know that you’ve arrived. It will put their mind at ease, as well as giving them the opportunity to let you know any final bits of information.
  • Bring your own water. Nine times out of 10, conferences will provide plenty of water for speakers. However, you really don’t want to take a gamble on it. Bring your own water (lots of it) and make sure it’s bottled. Conferences often provide jugs and glasses of water on-stage, and whilst this might look a lot smarter, it’s far less practical: pouring yourself water whilst nervous is difficult, you’re leaving yourself prone to spillages and accidents, and if you’re anything like me, you’ll be drinking a lot of it. A couple of plastic bottles of your own tucked out of sight are a good idea.
  • Get mic’ed up ahead of time. Turn up in plenty of time to get your microphone fitted and tested. Ask your AV person if the microphone is controlled by them remotely, or if there’s something you need to turn on yourself.
  • Remove your lanyard. Don’t wear your lanyard on-stage. It’s distracting, will likely look bad in photos, will get in your way, and can cause annoying noises if you’re wearing certain types of microphone.
  • Turn off your speakers. Unless you need audio for your talk, mute your machine completely.
  • Turn off your wifi. Unless you need it for your talk, turn it off. You don’t want any FaceTime, Skype, etc. notifications.
  • Turn off any notifications. In fact, just turn any and all notifications off completely.
  • Enable Caffeine. You do not want your screen going to sleep by accident.
  • Put your phone in airplane mode. Simply putting your phone on silent mode isn’t good enough, you’ll still feel it vibrating in your pocket if you get a call.
  • Wait off-stage. If you’re being introduced by someone, try to wait slightly off-stage whilst they introduce you. Naturally, this isn’t always possible, but try avoid standing awkwardly close to them whilst they’re talking about you.
  • Thank the MC for their intro. And shake their hand if appropriate. I find this moment of human interaction just before beginning to speak puts me at ease.
  • Get out there and enjoy it. If you’re the type to get nervous, there’s not much to be done about that; you’re gonna be nervous. Just get out there and do a great job. Have fun.

After the Talk

  • Thank the audience for their time. This isn’t about you, it’s about them. Let them know that you’re grateful for their time, that your slides are online at [location], and that they can grab you during breaks for questions.
  • Take questions. If there’s a Q&A session, begin taking questions. If you get a question, take time to listen to it fully; if you don’t hear or understand it first time around, do not be embarrassed to ask for a repeat or reword. Repeat the question back to the audience—you can use this as an opportunity to paraphrase the question to better suit your stance/answer. If you don’t have an answer, do not try to blag it; let the person know you’re not sure right now, but you’re keen to look it up and you’ll get back to them.
  • Pack up your things efficiently and tidily. Close your laptop lid, pack up your clicker etc. on top if it, carry if off-stage like a tray.
  • Get off stage swiftly and smartly. Even if you’re not sure where you’re meant to head, walk off stage quickly and confidently. If you’ve headed the wrong way, you can recover from that on your own time; don’t bumble around on stage in front of everyone.
  • Return your mic. Stay silent in case it’s still turned on, and make your way straight to the AV team. Return your mic and thank them for their help and support.
  • Share your slides. If the slides are only really of use the attendees who are in the room, tweet a link to them directly at the conference’s Twitter @account. This means you don’t end up spamming the rest of your followers who aren’t present, and the conference can retweet the resources to the attendees.
  • Thank everyone. The AV team, volunteers, organisers, venue staff, and a whole lot of other people are jointly responsible for your presence and success on stage; take the time to thank them for looking after you. As you leave the venue, smile at and thank as many venue staff as you see: their work tidying up etc. isn’t over yet.
  • Go to the afterparty. If there’s an afterparty, even if you don’t feel up to it, turn up for at least one drink. Show your face, answer any questions that you can, take feedback (positive and negative) graciously, and just hang out with people. It’s another of your responsibilities as a speaker.
  • Give feedback. Let the conference know what you thought of the event, good or bad (just remain honest, polite, and constructive). Let them know what they got right; be enthusiastic about sharing the positives. If there are, unfortunately, any negatives, make sure they’re actually worth bringing up, and share them privately in an email after the fact. Don’t go bringing down the mood unless something absolutely needs immediate attention.

These lists are by no means exhaustive, but they’re a pretty easy-to-follow set of tasks that you should try to follow any time you give a talk. It’ll make your life easier.