-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdetails.json
307 lines (307 loc) · 31.8 KB
/
details.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
[
{
"apiSpeakerUrl": "https://api.github.com/users/svozza",
"speakerUrl": "https://github.com/svozza",
"title": "Null Can't Hurt You Anymore",
"description": "<p>This talk follows on from @cullophid's session and seeks to build on those foundations with larger abstractions that can help developers to avoid common pitfalls when writing JavaScript such as null references (<code>Maybe</code>s), uncaught exceptions (<code>Either</code>s) and asynchronous control flow (<code>Future</code>s). These abstractions help to encapsulate uncertainty allowing us to code the happy path whilst ultimately enforcing the handling of error conditions and as the data types all share a common interface it allows us to compose them in predictable ways. Stefano Vozza is a tech lead at Trinity Mirror and has a keen interest in functional programming, DevOps and continuous delivery. He is a main contributor to several open source Javascript FP libraries such as <a href=\"https://github.com/sanctuary-js/sanctuary\">Sanctuary</a>, <a href=\"https://github.com/cullophid/date-fp\">date-fp</a> and <a href=\"https://github.com/caolan/highland\">Highland</a>. </p>\n",
"milestone": "November 23rd 2016",
"img": "https://avatars.githubusercontent.com/u/8573472?v=3",
"handle": "svozza",
"name": "Stefano Vozza"
},
{
"apiSpeakerUrl": "https://api.github.com/users/jc888",
"speakerUrl": "https://github.com/jc888",
"title": "Readable Microservices, with functional programming.",
"description": "<p>In the final talk James Chow will talk about how the principles of functional programming aligns itself with modern distributed architectures. Join him as he builds a fully functional microservice application using our new functional programming toolbox. James shows us how all the various parts of functional programming comes together to create safe efficient code that is easily readable and extendable. James chow has been a software contractor for over 10 years. He is currently Devops Engineer for Discovery where he manages Infrastructure, and advises on constructing applications.</p>\n",
"milestone": "November 23rd 2016",
"img": "https://avatars.githubusercontent.com/u/3694261?v=3",
"handle": "jc888",
"name": "James Chow (dsc)"
},
{
"apiSpeakerUrl": "https://api.github.com/users/cullophid",
"speakerUrl": "https://github.com/cullophid",
"title": "Keep calm and curry on",
"description": "<p>In this first talk we will look at the fundamental principles that underpin the functional programming paradigm. We introduce some of basic techniques that makes functional programming so powerful. These are techniques you can easily apply to your codebase to increase readability and reusability. Andreas MØller is a London based full stack JavaScript developer. Andreas splits his time between contracting and his role as CTO of his analytics startup Sentia. </p>\n",
"milestone": "November 23rd 2016",
"img": "https://avatars.githubusercontent.com/u/1183585?v=3",
"handle": "cullophid",
"name": "Andreas Møller"
},
{
"apiSpeakerUrl": "https://api.github.com/users/bookercodes",
"speakerUrl": "https://github.com/bookercodes",
"title": "Write More Resilient JavaScript with Flow",
"description": "<p><strong>Abstract</strong> Flow is a static type checker for JavaScript (an otherwise dynamically-typed language). You can think of it as a productivity tool that catches common errors <em>before</em> they run. Take the infamous "'Undefined' is not a function" error as an example. When writing vanilla JavaScript, you would have to wait until runtime to receive this arduous error. Flow - on the other hand - integrates with your favorite editor and analyzes the correctness of your code as you write it. If you were to reference a non-existent function, Flow would not only tell you immediately but also provide additional context that makes the error easier to fix. Whilst Flow is predominantly used with front-end technologies like React, I have been using it with great success for my Node.js projects and in this talk, I'll not only show you how to get up and running with Flow, I'll also share my experience with you. I'll also take a moment at the end of my talk to touch on the differences between Flow and TypeScript. <strong>Alex Booker</strong> Alex Booker is a Developer Advocate at <a href=\"https://pusher.com/\">Pusher</a>. There, he spends his time learning and writing about interesting, emerging technologies, and representing Pusher at events around the world. In his spare time, he runs a YouTube channel called <a href=\"https://www.youtube.com/c/codecast\">Code Cast</a> where he uploads educational screencasts about Linux and JavaScript. You can find him on Twitter <a href=\"https://twitter.com/bookercodes\">@bookercodes</a>.</p>\n",
"milestone": "October 26th 2016",
"img": "https://avatars.githubusercontent.com/u/11927968?v=3",
"handle": "bookercodes",
"name": "Booker ⚡"
},
{
"apiSpeakerUrl": "https://api.github.com/users/lazlojuly",
"speakerUrl": "https://github.com/lazlojuly",
"title": "How to build a RESTful API",
"description": "<p>Talk agenda: 1. The REST Design 2. Specification 3. Mocking 4. Testing This talk will also look at some popular API tools. Bio: I am a JavaScript Engineer. Connect with me on <a href=\"https://twitter.com/lazlojuly\">Twitter</a>, <a href=\"https://www.linkedin.com/in/lazlojuly\">LinkedIn</a> or <a href=\"https://github.com/lazlojuly\">GitHub</a></p>\n",
"milestone": "October 26th 2016",
"img": "https://avatars.githubusercontent.com/u/7015868?v=3",
"handle": "lazlojuly",
"name": "lazlojuly"
},
{
"apiSpeakerUrl": "https://api.github.com/users/mikemaccana",
"speakerUrl": "https://github.com/mikemaccana",
"title": "Quick wins with node and Google AMP",
"description": "<p>Google's Accelerated Mobile Pages (AMP) is a subset of HTML designed to load as quickly as possible. AMP pages keep your users happy, get you higher in search engine results pages, and related features like structured data can get you right to the top. Here's how a little node engineering can mean more money in your pocket. # Talk Description What AMP is: - What you gain (pagerank, content previews inside Google search, low latency) - What still works and what breaks (analytics, conversion tracking etc support is still ongoing) Implementing AMP in a node app: - Creating an AMP version of your existing layout - Converting output from your existing template engine to AMPHTML via server-side DOM manipulation - Handing analytics in an AMPHTML world I've written and Open Soured some express-compatible middleware to make this job easier, see <a href=\"https://www.npmjs.com/package/amps-in-the-trunk ##\">https://www.npmjs.com/package/amps-in-the-trunk ##</a> Bio Mike MacCana is the founder of CertSimple, a startup that provides EV HTTPS certs - the ones where they check who you are - 40-500x faster than it's competitors. He's previously built web apps for Google, Adobe and Microsoft.</p>\n",
"milestone": "October 26th 2016",
"img": "https://avatars.githubusercontent.com/u/172594?v=3",
"handle": "mikemaccana",
"name": "Mike MacCana"
},
{
"apiSpeakerUrl": "https://api.github.com/users/foxreymann",
"speakerUrl": "https://github.com/foxreymann",
"title": "Ace JavaScript Interviews: Scoping and Hoisting",
"description": "<p>Back to basics of JavaScript. Informative, interesting and entertaining talk. Great knowledge refreshment for those who know JavaScript. Essential education for those who never learned JavaScript properly. Node.js Developer. Web Development Trainer. Looking for new opportunities. @foxreymann</p>\n",
"milestone": "September 28th 2016",
"img": "https://avatars.githubusercontent.com/u/807661?v=3",
"handle": "foxreymann",
"name": "Fox Reymann",
"youtubeUrl" : "https://youtu.be/hr61xyYSP6k"
},
{
"apiSpeakerUrl": "https://api.github.com/users/gnugat",
"speakerUrl": "https://github.com/gnugat",
"title": "Event Driven Architecture",
"description": "<p>When <a href=\"https://nodejs.org/en/\">Node.Js</a> says "<code>event-driven, non-blocking I/O</code>", have you ever felt it was some sort of black magic? Well in this talk we'll <a href=\"https://blog.8thlight.com/uncle-bob/2015/08/06/let-the-magic-die.html\">make the magic go away</a> by implementing our own simple HTTP server, Event Loop, Scheduler, Deferer/Promise and <a href=\"http://screencrush.com/442/files/2016/02/deadpool-2-boyfriend-pic.jpg?w=720&cdnnode=1\">Thread Pool</a>. Oh, Hi by the way! I'm Loïc (it's pronounced Low-ic), a "Lead Engineer" (read Lead Dev) at <a href=\"http://constant.co/\">Constant Commerce</a>. You'll find that I <a href=\"https://twitter.com/epiloic\">tweet</a> and <a href=\"http://gnugat.github.io/\">blog</a> a lot about tech. I aslo <a href=\"https://github.com/gnugat\">contribute a bit</a> to FOSS projects.</p>\n",
"milestone": "September 28th 2016",
"img": "https://avatars.githubusercontent.com/u/793185?v=3",
"handle": "gnugat",
"name": "Loïc Faugeron",
"youtubeUrl": "https://youtu.be/BwqouUxn-bg"
},
{
"apiSpeakerUrl": "https://api.github.com/users/tanzim",
"speakerUrl": "https://github.com/tanzim",
"title": "I've got swagger. Have you?",
"description": "<p>OpenAPI Specification, formerly known as Swagger is a well established standard for defining REST API interfaces. In this talk I'd like to quickly go over Swagger, how you can integrate it with node.js and a few best practices that goes a long way to deliver robust enterprise class API service Additional links: - <a href=\"https://github.com/OAI/OpenAPI-Specification -\">https://github.com/OAI/OpenAPI-Specification -</a> <a href=\"https://github.com/swagger-api/swagger-node\">https://github.com/swagger-api/swagger-node</a></p>\n",
"milestone": "September 28th 2016",
"img": "https://avatars.githubusercontent.com/u/1591642?v=3",
"handle": "tanzim",
"name": "Tanzim",
"youtubeUrl": "https://youtu.be/Dlo3e-0wB1E"
},
{
"apiSpeakerUrl": "https://api.github.com/users/dmagliola",
"speakerUrl": "https://github.com/dmagliola",
"title": "Harnessing the full power of Redis",
"description": "<p>The vast majority of projects use Redis like it's Memcached, but Redis can give so much more. In this talk I'll give practical examples of use cases where Redis, with its very particular set of skills, outshines everything else I've tried. Bio: Daniel Magliola has been writing code since he was 7 years old, professionally since 16, and through those years has dabbled in multiple technologies. These days you'll find him trying to extract every last bit of performance out of web applications. <a href=\"http://danielmagliola.com/\">Portfolio / Bio / CV / about me</a> Note on length: I <em>can</em> fly through this talk in 25 minutes, I can probably also shorten it a bit more and do it in 20 (with no time for Q&A), but it's really a whirlwind. If I could have 30 or more that'd make it a lot more understandable by the audience :-) Note on dates: I can do August, but not September unfortunately.</p>\n",
"milestone": "August 24th 2016",
"img": "https://avatars.githubusercontent.com/u/1516867?v=3",
"handle": "dmagliola",
"name": "Daniel Magliola"
},
{
"apiSpeakerUrl": "https://api.github.com/users/bernardbaker",
"speakerUrl": "https://github.com/bernardbaker",
"title": "NodeJS a professional case study",
"description": "<p>Hiring people from these events work! And small NodeJS apps that get things done. When I came to a previous event I was asked if I was hiring... I was, and found a great candidate and now a new team member for our development team. She will describe her working day and the different things she has been doing with us at Sky Works since she started. After that I will take you through the build and development of a small NodeJS app which gets a single task done well. We use it to update obfuscated JavaScript files. I'll explain the project/technical/functional brief and then take you through the development in steps of progress, there will be live coding of parts of the application and an explanation of how the libraries used work. At the end I will present the live application which is hosted on Heroku. Twitter: @bernibear2000 Github: bernardbaker</p>\n",
"milestone": "August 24th 2016",
"img": "https://avatars.githubusercontent.com/u/13556172?v=3",
"handle": "bernardbaker",
"name": "Bernard Baker"
},
{
"apiSpeakerUrl": "https://api.github.com/users/guypod",
"speakerUrl": "https://github.com/guypod",
"title": "Stranger Danger: addressing the security risk in npm dependencies",
"description": "<p>Open source modules, and especially npm, are undoubtedly awesome. However, they also represent an undeniable and massive risk. You’re introducing someone else’s code into your system, often with little or no scrutiny. Each component may have vulnerabilities (~14% of them do!), may be compromised, or even be outright malicious. Multiply that risk by hundreds of dependencies, and you have a recipe for disaster. In this talk we’ll show how you can mitigate this risk without losing productivity. We’ll share more data more about the risk; show how to find & fix known vulnerabilities in these dependencies; discuss how to prioritize the ones worthy of manual inspection & suggest what to monitor in production. </p>\n",
"milestone": "February 24th 2016",
"img": "https://avatars.githubusercontent.com/u/1106394?v=3",
"handle": "guypod",
"name": "Guy Podjarny"
},
{
"apiSpeakerUrl": "https://api.github.com/users/shakyShane",
"speakerUrl": "https://github.com/shakyShane",
"title": "Taming Asynchronous Programming with RxJS",
"description": "<p>Asynchronous programs can be confusing, hard to follow, difficult to debug and, quite frankly, just down right <em>annoying</em> to write. Mouse & touch events in the browser, XHR requests, node's various event emitters... - what if there was a way to model all of these eventual values in the exact same way? RxJS allows us to do exactly this with the Observable. Boasting a rich set of composable operators, you can begin to unravel your spaghetti code and author declarative transformation pipelines that are simply not possible otherwise.</p>\n",
"milestone": "February 24th 2016",
"img": "https://avatars.githubusercontent.com/u/1643522?v=3",
"handle": "shakyShane",
"name": "Shane Osbourne"
},
{
"apiSpeakerUrl": "https://api.github.com/users/zsid",
"speakerUrl": "https://github.com/zsid",
"title": "How to build a real-time application with Node",
"description": "<p>I would like to do a beginner level talk on Node. As someone who is just starting to learn Node, I want to share my experience and make a walkthrough presentation. I haven't decided whether I will be building a game or not.</p>\n",
"milestone": "February 24th 2016",
"img": "https://avatars.githubusercontent.com/u/11786608?v=3",
"handle": "zsid",
"name": "Zhivko Siderov"
},
{
"apiSpeakerUrl": "https://api.github.com/users/hxoliverrumbelow",
"speakerUrl": "https://github.com/hxoliverrumbelow",
"title": "NodeJS Supercomputing?!",
"description": "<p>Join me in a wild adventure to take a computationally heavy single-use NodeJS application and automagically scale it across many cores and many servers in the hunt for lazy performance. Disclaimer: This is all for fun, games and science.</p>\n",
"milestone": "January 27th 2016",
"img": "https://avatars.githubusercontent.com/u/3088374?v=3",
"handle": "hxoliverrumbelow",
"name": "Oliver Rumbelow",
"youtubeUrl": "https://youtu.be/1mYl6v0Kzt0"
},
{
"apiSpeakerUrl": "https://api.github.com/users/HugoDF",
"speakerUrl": "https://github.com/HugoDF",
"title": "Going cross-platform with React: ~1 codebase, 3 platforms",
"description": "<p>What's the fastest way to ship a Web, iOS and Android app? React Native goes beyond making native apps with web technology. You use javascript (granted that's a web technology) to make a fully fledged React app, using native components. It's more than leveraging the power of the (state) => (UI) mapping of React. It's about code reuse. Being this DRY hurts. All the high-level logic is portable and you have <strong>one</strong> single codebase for all three target platforms. All of this is free, as long as you embrace React.</p>\n",
"milestone": "January 27th 2016",
"img": "https://avatars.githubusercontent.com/u/6459679?v=3",
"handle": "HugoDF",
"name": "Hugo",
"youtubeUrl": "https://youtu.be/b3wYEn2r_Ac"
},
{
"apiSpeakerUrl": "https://api.github.com/users/philnash",
"speakerUrl": "https://github.com/philnash",
"title": "2FA, WTF?",
"description": "<p>Everyone is hacking everything. Everything is vulnerable. Your site, your users, even you. Are you worried about this? You should be! Don't worry, I'm not trying to scare you (that much). We have plenty of safeguards against attempts on our applications' user data. We all (hopefully) recognise Two Factor Auth as one of those safeguards, but what actually goes on under the hood of 2FA? We'll take a look into generating one time passwords in JavaScript, implementing 2FA in Node.js applications and the only real life compelling use case for QR codes. Together, we'll make the web a more secure place.</p>\n",
"milestone": "January 27th 2016",
"img": "https://avatars.githubusercontent.com/u/31462?v=3",
"handle": "philnash",
"name": "Phil Nash",
"youtubeUrl": "https://youtu.be/Wuc4Nh3lmSE"
},
{
"apiSpeakerUrl": "https://api.github.com/users/BenHall",
"speakerUrl": "https://github.com/BenHall",
"title": "Scaling Node.js using Docker",
"description": "<p>With great load comes great scaling responsibility. If we need to scale then hopefully it means we're doing something right. The problem is how to scale without increasing complexity and re-writing the application. In this talk, Ben will discuss how he scales Katacoda.com, an online learning platform for developers. Ben will show how to deploy Node.js applications with Docker. Once deployed, Ben will highlight how to scale the processes and take advantage of container based deployments.</p>\n",
"milestone": "November 25th 2015",
"img": "https://avatars.githubusercontent.com/u/82614?v=3",
"handle": "BenHall",
"name": "Ben Hall",
"youtubeUrl": "https://youtu.be/nBBJh75SqS4"
},
{
"apiSpeakerUrl": "https://api.github.com/users/fabiosantoscode",
"speakerUrl": "https://github.com/fabiosantoscode",
"title": "A javascript to c++ transpiler!",
"description": "<p>A talk about an in-development javascript to c++ transpiler which currently kind of works and implements closures, numbers, objects, functions and strings. Watch it compile and run hello world, and beat node in an EPIC FIB() BENCHMARK! Be compelled by the power of tern.js to figure out what you think you're actually writing!</p>\n",
"milestone": "November 25th 2015",
"img": "https://avatars.githubusercontent.com/u/1611595?v=3",
"handle": "fabiosantoscode",
"name": "Fábio Santos",
"youtubeUrl": "https://youtu.be/6RKxkINidvk"
},
{
"apiSpeakerUrl": "https://api.github.com/users/forbesmyester",
"speakerUrl": "https://github.com/forbesmyester",
"title": "MVP Diagrams that can do things",
"description": "<p>A short talk on DB DiaYAML, which is a journey-to-work and weekend project for drawing simple database diagrams. It's not particularly a serious project but it scratches an itch I had and has a nice MVP feel to it. There's a blog post about it at <a href=\"http://keyboardwritescode.blogspot.co.uk/2015/07/weekend-project-db-diayaml.html\">http://keyboardwritescode.blogspot.co.uk/2015/07/weekend-project-db-diayaml.html</a> </p>\n",
"milestone": "November 25th 2015",
"img": "https://avatars.githubusercontent.com/u/3470771?v=3",
"handle": "forbesmyester",
"name": "Matt Forrester",
"youtubeUrl": "https://youtu.be/qPCF4JUyllc"
},
{
"apiSpeakerUrl": "https://api.github.com/users/bananaoomarang",
"speakerUrl": "https://github.com/bananaoomarang",
"title": "Flux to Redux, Thinking with Data",
"description": "<p>Flux is one of the newer cool kids on the block, but it has it's fair share of problems. With all of the different implementations fighting for recognition, to first time users and abusers it can seem overly complicated. Redux is one Flux framework which has gained a lot of traction recently, thanks to its novel take on the architecture (vastly simpler than Facebooks sample implementation, for instance) and neat debugging features. This talk can show the differences between Redux's approach and more 'traditional' Flux architectures, running over its benefits for developers. It will also briefly explain the difference between Flux applications and other MVC implementations, for anyone curious and unfamiliar.</p>\n",
"milestone": "October 28th 2015",
"img": "https://avatars.githubusercontent.com/u/815831?v=3",
"handle": "bananaoomarang",
"name": "Milo Mordaunt",
"youtubeUrl":"https://youtu.be/n99Jhop6K8Y"
},
{
"apiSpeakerUrl": "https://api.github.com/users/alistairstead",
"speakerUrl": "https://github.com/alistairstead",
"title": "Full-stack BDD and its side effects",
"description": "<p>This is not yet another how do you do BDD in JavaScript talk. This is a talk about how you can apply widespread software design practices such as Design Patterns, BDD, TDD, DDD and SOLID to full-stack development. Less how to use these practices, more how to select and use them effectively. Just using these tools on their own can lead to unnecessary complexity that can be hard to understand or avoid. So let’s set aside discussions of the language syntax or capabilities and focus on what is important - delivering value to the customer. This presentation will show how BDD practices can be applied to the different contexts of developing features through a multi-layer stack whilst smoothing the communication, providing detailed direction and showing the value for business owners and developers alike. The result is a feature that meets the business owner’s expectations with happy side effects such as the code being clean, well designed, understandable, fully tested and documented.</p>\n",
"milestone": "October 28th 2015",
"img": "https://avatars.githubusercontent.com/u/62936?v=3",
"handle": "alistairstead",
"name": "Alistair Stead",
"youtubeUrl":"https://youtu.be/YP_YIH4GoGE"
},
{
"apiSpeakerUrl": "https://api.github.com/users/tomgco",
"speakerUrl": "https://github.com/tomgco",
"title": "White water streams",
"description": "<p>We use streams on a daily basis when handling data with our Node.js applications, but how do they work, and more importantly, how do we keep them efficient and performant? This talk focus mainly on analysing applications that utilises streaming data, identifying bottlenecks and making improvements. Be wow’ed by Flame{graphs,charts}, awed by benchmarks and take away some tips in writing decent stream implementations.</p>\n",
"milestone": "October 28th 2015",
"img": "https://avatars.githubusercontent.com/u/524382?v=3",
"handle": "tomgco",
"name": "Tom Gallacher",
"youtubeUrl":"https://youtu.be/iBEjz38ppe4"
},
{
"apiSpeakerUrl": "https://api.github.com/users/bodil",
"speakerUrl": "https://github.com/bodil",
"title": "The Miracle of Generators",
"description": "<p>The ECMAScript 2015 specification introduced <em>iterators</em>, which generalise iteration over common data structures, as well as providing an interface for allowing you to iterate over any custom data structures using common language constructs. ES2015 also introduced <em>generator functions</em>, which make writing arbitrary iterators a lot easier and less boilerplatey. But generators aren't just for making simple iterators over data structures. Because they're bidirectional—they don't only produce output, they can also take input—they're actually <em>coroutines</em>, which means there's no end to the sort of fun you can apply them to. We're going to explore how we can use them to make asynchronous programming in JavaScript a lot more elegant—to chart a path out of callback hell. And then we're going to take a look at what we've really discovered: one of the most fearsome mysteries of computer science, suddenly laid bare before us.</p>\n",
"milestone": "September 23rd 2015",
"img": "https://avatars.githubusercontent.com/u/17880?v=3",
"handle": "bodil",
"name": "Bodil Stokke"
},
{
"apiSpeakerUrl": "https://api.github.com/users/hassy",
"speakerUrl": "https://github.com/hassy",
"title": "Load-testing for fun and profit",
"description": "<p>This talk will (briefly) outline why load-testing should be a part of your testing activities and then dive into an overview of tooling and strategies & processes to get the most out of it when working on a production system. We'll also explore how load-testing can improve our understanding of both our own code and components that our code depends on.</p>\n",
"milestone": "September 23rd 2015",
"img": "https://avatars.githubusercontent.com/u/1490?v=3",
"handle": "hassy",
"name": "hassy veldstra"
},
{
"apiSpeakerUrl": "https://api.github.com/users/burtonjc",
"speakerUrl": "https://github.com/burtonjc",
"title": "How Waffle.io separated its API from its core web app",
"description": "<p>At Waffle.io, we recently built a public API to gain access to Waffle's data (in private beta now). We knew we wanted the API to be deployed, scaled, and monitored separately from our core app. We also wanted the app to use the same API we were providing to our users. Carving the API out as its own service consumed by our app provided some interesting challenges and produced some surprising benefits. This talk will describe the design we came up with, the challenges we faced, and the largely unexpected benefits we received.</p>\n",
"milestone": "September 23rd 2015",
"img": "https://avatars.githubusercontent.com/u/443084?v=3",
"handle": "burtonjc",
"name": "Jacob Burton"
},
{
"apiSpeakerUrl": "https://api.github.com/users/tjanczuk",
"speakerUrl": "https://github.com/tjanczuk",
"title": "Rethinking backend with webtasks",
"description": "<p>You are writing a mobile or HTML5 web application that needs just a little bit of a backend. Maybe you want to access MongoDB, send an SMS, or an e-mail. Do you really need to host your own Node.js service to run this small snippet of backend logic? In this talk I will take a hard look at the role of the backend in modern applications. I will introduce the concept of a <a href=\"https://webtask.io\">webtask</a> - a lightweight representation of backend logic that can safely be embedded in a client application. I will show how you can use modern container technologies based on CoreOS and Docker to build a generic, multi-tenant runtime for securely executing webtasks directly from a mobile or HTML5 application. You don’t need a backend to run backend code. This talk is based on lessons learned when building the Node.js sandboxing technology for internal use in our core operations at Auth0. Find out more: <a href=\"http://tomasz.janczuk.org/2015/04/rethinking-backend-with-webtasks.html\">Webtask concepts</a> <a href=\"https://github.com/auth0/wt-cli\">Webtask CLI</a> <a href=\"https://webtask.io\">Webtask playground</a> <a href=\"https://medium.com/aws-activate-startup-blog/sandboxing-code-in-the-era-of-containers-294edb3a674\">Webtask technology</a> </p>\n",
"milestone": "August 26th 2015",
"img": "https://avatars.githubusercontent.com/u/822369?v=3",
"handle": "tjanczuk",
"name": "Tomasz Janczuk",
"youtubeUrl":"https://youtu.be/bhQ3Ov4niPs"
},
{
"apiSpeakerUrl": "https://api.github.com/users/danjenkins",
"speakerUrl": "https://github.com/danjenkins",
"title": "WebRTC Reborn",
"description": "<p>WebRTC has had a real tough 3 or 4 years, and so have those working with it. Only a few short years ago, the development world were excited about WebRTC and proclaiming how awesome it was. You might have played with the technology a couple of years ago, only to find the extra infrastructure requirements were painful to implement and poorly documented. This probably left a bitter taste in your mouth, especially when things went wrong. Those in the industry have been working hard to sweeten the deal again - efforts have been made to bring WebRTC into the mainstream and as a result the technology is experiencing a rebirth. Thanks to those who have remained dedicated to improving the situation for those around them, WebRTC is finally starting to fulfil the original expectations that were had of it. Both the technology and the support networks have been built up to make experimenting with it again a pleasure, not a pain. WebRTC has grown up; in this talk you will learn how far along the tech has come, its current capabilities, the amazing things that people are starting to do with it, and how simple getting started with the new toolsets available. </p>\n",
"milestone": "August 26th 2015",
"img": "https://avatars.githubusercontent.com/u/243117?v=3",
"handle": "danjenkins",
"name": "Dan Jenkins",
"youtubeUrl": "https://youtu.be/tB9z4ZOoSwg"
},
{
"apiSpeakerUrl": "https://api.github.com/users/pimterry",
"speakerUrl": "https://github.com/pimterry",
"title": "TypeScript will finally bring peace to your troubled soul",
"description": "<p>You've heard of TypeScript, but you're not sure if it's a good idea, and you've never really seen it in action. TypeScript is powerful though, rapidly gaining momentum, and has a lot more to offer than just JS + classes. Let's take a proper look. In this talk, we'll dig a bit deeper and play around with some of the more interesting features TypeScript gives you. We'll walk through the extras that TypeScript provides and how they'll solve your every woe, learn a bit about where the types come in and why you care, and see how exactly you might put it into action on your next Node project.</p>\n",
"milestone": "August 26th 2015",
"img": "https://avatars.githubusercontent.com/u/1526883?v=3",
"handle": "pimterry",
"name": "Tim Perry",
"youtubeUrl":"https://youtu.be/UI9cgrMxGi0"
}
]