diff --git a/presentation.md b/presentation.md
index b7b6642..642e4d4 100644
--- a/presentation.md
+++ b/presentation.md
@@ -1,96 +1,147 @@
 % 34C3recap
 % Jean-Baptiste Aubort; EPFL//SI//SCITAS
 % \today
 
 # 34C3
 
 ![](./res/34C3.png)
 
 # 34C3
 
 ## Chaos Computer Club & Communication Congress
 
 * 34th Chaos Communication Congress in Leipzig
 * First time in Leipzig, had to leave Hamburg because the congress center was
   being rebuilt.
 * This year venue was HUGE !!!
 
 ![](./res/venue.png)
 
 # 34C3
 
 ![Congress is +15k visitors, +2.3k volunteers, 50k clubmate bottles](./res/congress.png)
 
 # 34C3
 
 ## Network
 
 * Uplink: 400Gbit/s, peak usage: 42.2 Gbit/s
 * Peak wifi users: 7673, APs deployed: 179
 * But the network was sometime very shitty because of SSID spam for instance
 
 ![SPAM](./res/ssid-spam.png)
 
 # 34C3
 
 ## Network
 
 * Some strange patterns appeared on the network graphs.
 
 ![strange patterns](./res/bandwith-morse.png)
 
 # 34C3
 
 ## Network
 
 * Some strange patterns appeared on the network graphs.
 
 ![34C3 in morse code](./res/bandwith-morse2.png)
 
 # 34C3
 
 ## Science is broken
 
 * Generating random experient data and have significant results
 * Publication bias, only the significant results are published
 * Mostly subconscious. What can we do to prevent p-value hacking ?
     * Usually nothing is done
     * Replicating studies
     * Talk about failure
     * Decouple study and data gathering
     * Preregristration for publication (and later check that publication is in
       line with the methodology presented in registration) -> already the case
       in drug study
     * Create the protocol first then publish it before the experiment. Publish
       the result indenpendently of the outcome
     * Sharing (data, methods, code, ...)
 * Good results (or negative results) are often boring,
   less attractive to the press but closer to the truth
   -> TED Talk science VS Boring science ?
 
 * The presentor blog https://betterscience.org/
       
 
 # 34C3
 
 ## Ecstasy 10x yellow Twitter 120mg Mdma
 
 * Bullet points
 
 # 34C3
 
 ## The Ultimate Apollo Guidance Computer Talk
 
-* Bullet points
+* Presentation of the computer that was used to control the command and the lunar modules
+* It was more of a how computers works talk :-D It's computer rocket science !
+* The talk is segmented into 4 parts: Architecture, Hardware, Peripherals and Software
+
+![AGC](./res/agc.png)
+
+# 34C3
+
+## The Ultimate Apollo Guidance Computer Talk - What does it do ?
+
+* Maintain State Vector
+* Stabilize Attitude
+* Calculate Burns
+* Control Burns
+* Monitor/Control Launch
+
+![](./res/agc-system.png)
+
+# 34C3
+
+## The Ultimate Apollo Guidance Computer Talk - Architecture
+
+* Von Neumann architecture
+* 15 bit word + 1 parity bit
+* 36 instructions (performance vs complexity)
+* Single address space for code and data, 12 bit address
+* 1 accumulator register (most instructions use it)
+
+![Instructions set](./res/agc-instructions.png)
+
+# 34C3
+
+## The Ultimate Apollo Guidance Computer Talk - Hardware
+
+* 1024 MHz clock
+* asd 
+
+![Hardware](./res/agc-hardware.png)
+
+# 34C3
+
+## The Ultimate Apollo Guidance Computer Talk - Peripherals
+
+* asd
+* asd 
+
+# 34C3
+
+## The Ultimate Apollo Guidance Computer Talk - Software
+
+* asd
+* asd 
 
 # 34C3
 
 ## How to drift with any car
 
 * Bullet points
 
 # 34C3
 
 ## UPSat - the first open source satellite
 
 * Bullet points
diff --git a/res/agc-hardware.png b/res/agc-hardware.png
new file mode 100644
index 0000000..c4b110a
Binary files /dev/null and b/res/agc-hardware.png differ
diff --git a/res/agc-instructions.png b/res/agc-instructions.png
new file mode 100644
index 0000000..3243004
Binary files /dev/null and b/res/agc-instructions.png differ
diff --git a/res/agc-system.png b/res/agc-system.png
new file mode 100644
index 0000000..3ae6a06
Binary files /dev/null and b/res/agc-system.png differ
diff --git a/res/agc.png b/res/agc.png
new file mode 100644
index 0000000..bb960b7
Binary files /dev/null and b/res/agc.png differ