diff --git a/events.xml b/events.xml
index 8dff058..fc92f10 100644
--- a/events.xml
+++ b/events.xml
@@ -4,6 +4,21 @@
 <eventdefs>
 
 <!-- Winter 2010 -->
+<eventitem date="2010-03-26" time="7:00 PM" room="MC7001" title="A Final Party of Code">
+  
+    <short><p>There is a CSC/CMC Code Party Friday starting at 7:00PM (1900) until we get bored (likely in the early in morning). Come out for fun hacking times, spreading Intertube memes (optional), hacking on open source projects, doing some computational math, and other general classiness. There will be free energy drinks for everyone's enjoyment. This is the last of the term so don't miss out.
+</p></short>
+  
+  
+    <abstract><p>There is a CSC/CMC Code Party Friday starting at 7:00PM (1900) until we
+get bored (likely in the early in morning). Come out for fun hacking
+times, spreading Intertube memes (optional), hacking on open source projects,
+doing some computational math, and other
+general classiness. There will be free energy drinks for everyone's
+enjoyment. This is the last of the term so don't miss out.
+</p></abstract>
+  
+</eventitem>
 <eventitem date="2010-03-23" time="4:30 PM" room="MC5158" title="Memory-Corruption Security Holes: How to exploit, patch and prevent them.">
   
     <short><p>Despite it being 2010, code is still being exploited due to stack overflows, a 40+ year old class of security vulnerabilities. In this talk, I will go over several common methods of program exploitation, both on the stack and on the heap, as well as going over some of the current mitigation techniques (i.e. stack canaries, ASLR, etc.) for these holes, and similarly, how some of these can be bypassed as well.