diff --git a/README.md b/README.md
index cd5eaf9..4d5db81 100644
--- a/README.md
+++ b/README.md
@@ -49,6 +49,8 @@ Preferably use the following link.
 ## Talks 🎥
 
 - [CppCon 2018 — *Simplicity: Not Just For Beginners*](https://www.youtube.com/watch?v=n0Ak6xtVXno)
+- [CppCon 2019 — *Naming is Hard: Let's Do Better*](https://www.youtube.com/watch?v=MBRoCdtZOYg)
+- [CppCon 2015 — *Give me 15 minutes & I'll change your view of GDB*](https://www.youtube.com/watch?v=PorfLSr3DDI)
 
 ## Useful References / Tools
 
diff --git a/exercises/README.md b/exercises/README.md
index 46e56fa..fd51a2f 100644
--- a/exercises/README.md
+++ b/exercises/README.md
@@ -59,9 +59,13 @@ Look for tools (e.g. static code analysers) which help discovering such faulty c
 **Note:** If you run the executable and everything seems normal, try changing the initial content of `xs`, using different optimisation flags, or a different compiler.
 The actual behaviour of this executable depends on various factors.
 
+See [Iterator Invalidation](https://en.cppreference.com/w/cpp/container#Iterator_invalidation).
+
 ## Task 05
 
 You are given the program [`strange.cpp`](task05/strange.cpp).
 Compile it with different compilers and optimisation flags.
 What do you notice?
 What is really happening here?
+
+See [Undefined Behaviour](https://en.cppreference.com/w/cpp/language/ub) and [Defining the undefinedness of C](https://dl.acm.org/citation.cfm?id=2737979).