diff --git a/slides/kernel-intro-sources/elixir.svg b/slides/kernel-intro-sources/elixir.svg
new file mode 120000
index 0000000000..81b3a952f0
--- /dev/null
+++ b/slides/kernel-intro-sources/elixir.svg
@@ -0,0 +1 @@
+../sysdev-linux-intro-sources/elixir.svg
\ No newline at end of file
diff --git a/slides/kernel-intro-sources/kernel-intro-sources.tex b/slides/kernel-intro-sources/kernel-intro-sources.tex
index 6107621744..a89e7b834f 100644
--- a/slides/kernel-intro-sources/kernel-intro-sources.tex
+++ b/slides/kernel-intro-sources/kernel-intro-sources.tex
@@ -81,6 +81,35 @@ \subsection{Linux kernel sources}
   \end{itemize}
 \end{frame}
 
+\begin{frame}
+  \frametitle{Going through Linux sources}
+  \begin{columns}
+    \column[t]{0.4\textwidth}
+    \begin{itemize}
+    \item Development tools:
+      \begin{itemize}
+      \item Any text editor will work
+      \item Vim and Emacs support ctags and cscope and therefore can help
+        with symbol lookup and auto-completion.
+      \item It's also possible to use more elaborate IDEs to develop
+        kernel code, like Visual Studio Code.
+      \end{itemize}
+    \end{itemize}
+    \column[t]{0.6\textwidth}
+    \begin{itemize}
+    \item Powerful web browsing: Elixir
+      \begin{itemize}
+      \item Generic source indexing tool and code browser for C and C++.
+      \item Very easy to find symbols declaration/implementation/usage
+      \item Try out \url{https://elixir.bootlin.com}!
+      \end{itemize}
+    \end{itemize}
+    \begin{center}
+      \includegraphics[height=0.5\textheight]{slides/kernel-intro-sources/elixir.pdf}
+    \end{center}
+  \end{columns}
+\end{frame}
+
 \begin{frame}[fragile]
   \frametitle{Need for long term support}
   \begin{itemize}