Changed my talk

accepted/day2/call-to-action.md

@@ -0,0 +1,18 @@
+Speaker: hoegrammer
+Tags: refugees, digital exclusion
+
+This talk is a call to action, and a cry for help.
+
+Digital exclusion is a huge problem for refugees. Without passports, they can't buy mobile data. Money is also a problem for many. Wifi cafes only go so far.
+
+The psychological necessity of communicating with family and friends is only part of it. Rumours, misinformation and lies spread like wildfire. People are not getting the information they need to make decisions about their future. They don't know what is legal and what is not. And now, unbelievably, the Greek government has decided to offer asylum registration ONLY THROUGH SKYPE, FOR FUCK'S SAKE.
+
+I'll talk about how I failed them at Ritsona camp in recent weeks, and how I hope to do better. About the problems we face, politically and technologically.
+
+I have only basic knowledge of networking technology, but now seems like a perfect time to learn. I'll be asking for advice on quick, simple ways to get people online, and wisdom about the politics involved as well.
+
+Secure communication is also an issue - for volunteers working outside of the law, as well as the refugees themselves.
+
+The ISPs, the mobile networks, the corporations will not deliver to these vulnerable people the connectivity which has become almost a human right.
+
+If anyone's going to help them, it can only be people like us.

accepted/day2/stealth-refactoring.md

@@ -1,14 +0,0 @@
-# How Stealth Refactoring is Wrecking our Codebases
-
-Speaker         : naomi rosenberg  
-tag             : refactoring, micro-management, professionalism  
-
-Because management are perceived not to value refactoring, developers fear being “told off” for doing it. So we refactor less than we’d like to, and when we do, we often sneak it in, hidden amongst functional changes.
-
-We know insufficient refactoring leads to technical debt. Stealth refactoring creates problems, too. Reviewing a diff mixing functional and non-functional changes is time-consuming and error-prone, costing money and introducing bugs. Also, stealth refactoring tends to focus only on the “geographical area” - the function, file or module - that we are “touching” at the time. What are the implications of that for the coherence and consistency of our codebases?
-
-I will make some technical suggestions for optimising how we refactor, but the main issue is cultural. Is our shame around refactoring entirely due to management, or are devs responsible too? How can we sell simplicity to people who may not be aware of its value? Can we create a culture that legitimises - or even rewards! - a practice that is, after all, essential to developing good software?
-
-need travel fee : N  
-need room       : Y  
-Location        : Planet Earth