Title adjustment; new proposal.

site/content/events/2014-minneapolis/proposals/Culture is a By-product of Individuals/index.txt

@@ -0,0 +1,25 @@
+---
+extension: html
+filter:
+- erb
+- markdown
+dirty: true
+proposal: true
+talk: true
+selected: false
+layout: event
+author: Speaker 15
+title: "Culture is a By-product of Individuals"
+---
+
+**Abstract:**
+
+Everyone is hiring. Interviewing is hard. Hiring is harder. With all of these dynamics being an employer or an employee can be difficult. Our field can be the most difficult, stressful and draining at times. Stressful? Ever patch a production database and it fails to come back...ever deploy the businesses most important feature ever (today) and it doesn't work because it's 2014 and the internet hasn't figured out how to have production data usable for development.
+
+One of the most difficult aspects to a job is having an evolving culture that employers and employees can love together. This talk will dive into theories on hiring, interviewing and supporting a culture that employees can enjoy and forget about the stressful nature.
+
+It all starts with you; every employee of a company has responsibility over the culture and every employeer has responsibility for supporting that culture. 
+
+**Speaker:**
+Speaker 15
+

site/content/events/2014-minneapolis/proposals/Rub a little Ops on it/index.txt

@@ -9,9 +9,12 @@ talk: true
 selected: false
 layout: event
 author: Speaker 14
-title: "Rub a little Ops on it: Leveling up your development skills with some lessons from operations"
+title: "Rub a little Ops on it!"
 ---
 
+**Description**
+Leveling up your development skills with some lessons learned from operations.  
+
 **Abstract:**
 
 Building software is hard. Building maintainable quality software is incredibly hard. You know what else is hard? Running software. Operations has learned quite a bit from the development side of the house, a solid Ops person understands the basic principles of software development. But the reverse should also be true for developers. Coming from the perspective of someone who's done both, operations gives you an interesting view on how to run and ship software. Operations forces you to become an expert in recovering from failure. How to debug a problem when the only data you have are symptoms of that problem. It's a constant loop of continuous improvements to prevent the same problem from happening again. It's risk assessment, if something is a high risk how can you reduce that risk and still accomplish the desired goal? Operations requires understanding the impact of a change to your system, it could be the difference in shipping the nastiest hidden regression your software has ever seen versus shipping the new hotness feature that becomes it's number one selling point. But the most important thing developers can learn from operations is that everyone has the same goal, to ship and run maintainable quality software for your customers.