This repository has been archived by the owner on Dec 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
schedule.yaml
251 lines (251 loc) · 11.2 KB
/
schedule.yaml
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
---
- day: friday
events:
- time: "8:00 am"
name: Registration
speaker: SCRC
twitter: '@SteelCityRuby'
img: scrc.jpg
desc: >
Welcome to Steel City Ruby Conference, please register in the
lobby and get ready for a great day.
- time: "9:00 am"
name: Remembering SCRC14
speaker: Jean Lange
twitter: '@jean_lange'
img: jean_lang.jpg
desc: >
Let's all (really all) talk about what this Ruby conference is for,
why you're here, and what you're going to do to go home thrilled with
your experience. First, listen to my perspective - I say this
conference is for strengthening and broadening our sense of
ourselves as Rubyists so that we can learn from each other and
move forward as a community. Then wield your markers and
stickies to start to express and share your ideas about what
will make SCRC14 amazing for you and for us
- time: "9:30 am"
name: Break
speaker: SCRC
twitter: '@SteelCityRuby'
img: scrc.jpg
desc: >
- time: "10:00 am"
name: "JRuby: The Best Parts"
speaker: Charles Nutter
twitter: '@headius'
img: charles_nutter.jpg
desc: >
You've probably heard of JRuby, and maybe you've even tried it.
You may know it can run your Ruby code fast, take advantage of all cores in your system,
and handle large applications and datasets with ease. But wait, there's more!
JRuby can also be used to make games, desktop applications, Minecraft plugins,
Android apps... just about anything you can imagine. This talk will cover some
of these awesome capabilities and show how you can get started with JRuby today.
- time: "10:30 am"
name: Break
speaker: SCRC
twitter: '@SteelCityRuby'
img: scrc.jpg
desc: >
- time: "11:00 am"
name: Utils is a Junk Drawer
speaker: Franklin Weber
twitter: '@franklinwebber'
img: franklin_weber.jpg
desc: >
Nearly all our larger scale applications end up with a utils
folder, module, or class. We all know them as our project's
junk drawers. The wayward place for motley code. In this talk
we will explore these junk drawers, come to know their stories,
and lay to rest the question: Does having a junk drawer in my
application make everything better or worse?
- time: "11:30 am"
name: Lunch
speaker: SCRC
twitter: '@SteelCityRuby'
img: scrc.jpg
desc: >
Lunch will be until 1:30 pm.
- time: "1:30 pm"
name: Better Visualizations with Science
speaker: John Feminella
img: john_feminella.jpg
twitter: '@jxxf'
desc: >
We've got a lot of tools at our disposal to render data in all kinds of interesting ways: charts, tables, gauges, and so on. Yet most dashboards are designed for consumption by humans, and many users say they don't get a lot of value from these visualizations -- or even worse, they find them confusing to use. We're doing something wrong.
In this talk, we'll describe the scientifically-validated attributes of great visualizations, point out some common antipatterns that we think you should avoid, and illustrate how to optimize for showing the most relevant facets of a dataset. Don't let your dashboard become another statistic!
- time: "2:00 pm"
name: Break
speaker: SCRC
twitter: '@SteelCityRuby'
img: scrc.jpg
desc: >
- time: "2:30 pm"
name: Lightning Talks
speaker: SCRC
twitter: '@SteelCityRuby'
img: scrc.jpg
desc: >
Details Will Be Outlined Soon
- time: "3:00 pm"
name: Better Coding with Ruby Lambdas
speaker: Keith Bennett
twitter: '@SteelCityRuby'
img: keith_bennett.jpg
desc: >
We Rubyists reject unnecessary ceremony and complexity, always
striving to minimize complexity as much as possible without
sacrificing clarity. So why are we not using functional approaches
when object oriented approaches fail to go the last mile?
- time: "3:30 pm"
name: Break
speaker: SCRC
twitter: '@SteelCityRuby'
img: scrc.jpg
desc: >
- time: "4:00 pm"
name: Saving the World with Ruby
speaker: Sean Marcia
twitter: '@seanmarcia'
img: sean_marcia.jpg
desc: >
Two thirds of honeybee hives have died out in Virginia. Is it
possible for us to devise a way of monitoring beehives in
remote locations to find the cause? Enter a Raspberry Pi +
Rails. Using a combination of this robust hardware and
software solution, we were able to successfully track,
monitor and provide reporting on the well-being of hives from
across the county. Find out how we used Ruby, Rails, solar
panels and other libraries to provide insight into this problem.
- time: "4:30 pm"
name: Inside RubyMotion for Android
speaker: Laurent Sansonetti
twitter: '@lrz'
img: laurent_sansonetti.jpg
desc: >
RubyMotion is a command-line Ruby based toolchain that initially allowed the development of iOS and OS X apps. Recently, Android support was introduced, and RubyMotion can therefore be used to write Android apps too. RubyMotion for Android features a brand new implementation of Ruby. In this session we will dive inside RubyMotion for Android and see how things work internally. This will be a technical presentation featuring demos.
- time: "6:00 - 11:00 pm"
name: ModCloth Party
speaker: Thanks to ModCloth
twitter: '@ModCloth'
img: modcloth.jpg
desc: >
Details Will Be Outlined Soon
- day: saturday
events:
- time: "10:00 am"
name: Ruby Motion and Accessibility
speaker: Austin Seraphin
img: austin_seraphin.jpg
twitter: '@AustinSeraphin'
desc: >
How does a blind person even use an iPhone? Learn through personal stories
why accessibility matters and some simple things you can do. Additionally,
learn about some RubyMotion tools to improve accessibility both for sighted
and blind iOS developers.
- time: "10:30 am"
name: Break
speaker: SCRC
img: scrc.jpg
twitter: '@SteelCityRuby'
desc: >
- time: "11:00 am"
name: From Whence Rubygems?
speaker: Timothy Uruski
img: timothy_uruski.jpg
twitter: '@timuruski'
desc: >
Where do Rubygems come from? We will trace the journey a Gem takes on its
way into your codebase, mapping paths through tools like RVM, rbenv and
Bundler. Along the way we will learn how these tools wrangle third party
Ruby code into place and what methods they share.
- time: "11:30 am"
name: Using Ruby for Journalism
speaker: Derek Willis
img: derek_willis.jpg
twitter: '@derekwillis'
desc: >
Although Ruby is well-known for its use in popular consumer applications,
it also has been used for several years in major newsrooms such as The New
York Times and ProPublica to build "news applications" that display data,
serve APIs and help inform readers. This isn't a typical web development
environment: in newsrooms, deadlines can mean hours, not weeks, and often
involve unfamiliar datasets and the challenges of both real-time publishing
and archived material. In this talk I'll introduce developers to the unique
world of newsroom developers and some of the applications and tools they've
built using Ruby.
- time: "12:00 pm"
name: Lunch
speaker: SCRC
img: scrc.jpg
twitter: '@SteelCityRuby'
desc: >
Lunch will be until 2:00 pm
- time: "2:00 pm"
name: Jam Session
speaker: SCRC
img: scrc.jpg
twitter: '@SteelCityRuby'
desc: >
In honor of our late friend Jim Weirich, we will be dedicating a spot
to a jam session. Jim was known for bringing his ukelele to conferences
and hosting impromptu jam sessions. We're going to have a spot in our
schedule for others to continue this trend.
- time: "2:30 pm"
name: Entrepreneurship for Engineers
speaker: Bryan Helmkamp
img: bryan_helmkamp.jpg
twitter: '@brynary'
desc: >
At some point or another, many engineers entertain the thought of
venturing out and starting their own business. It's a scary idea, but
the promises of control, flexibility and financial independence are
compelling. This talk will explore the path from software engineer to
entrepreneur, with its challenges, rewards and tradeoffs, influenced
by my experience founding Code Climate.
- time: "3:00 pm"
name: Break
speaker: SCRC
img: scrc.jpg
twitter: '@SteelCityRuby'
desc: >
- time: "3:30 pm"
name: The Metaphysics of Strings
speaker: Greg Gates
twitter: '@gregates'
img: greg_gates.jpg
desc: >
Presenting a paradox involving two Ruby strings which are
equal and constructed in ways that look very similar, but which
have different properties -- one of them is "html_safe" and the
other is not. The goal of the talk is to explore three things
about this paradox.
- time: "4:00 pm"
name: Dealing with the Demands of the Open Source Community
speaker: Seth Vargo
img: seth_vargo.jpg
twitter: '@sethvargo'
desc: >
They don't pay us money. They don't understand the goals of the project. They don't even say "thank you". But studies and personal experiences have proven that users of open source software are more demanding than those same users who pay for software. Why?
Understanding the "why" will help us discover the "how". How can we solve this problem? Because it's not a technical one - it's a cultural one.
- time: "4:30 pm"
name: Break
speaker: SCRC
img: scrc.jpg
twitter: '@SteelCityRuby'
desc: >
- time: "5:00 pm"
name: Generative Testing for Better Code
speaker: Jessica Kerr
img: jessica_kerr.jpg
twitter: '@jessitron'
desc: >
What’s better than Test-Driven Development? Even more test driven development! Unit tests are useful, but it's impractical to cover every situation. The more we try, the more tests we write, the more lines of code we maintain.
What if we could cover every valid scenario with exactly one test? The goal of Generative Testing is to carefully define every possible input, then let the framework run hundreds of scenarios through the same test. It means thinking about more than a few examples, and deciding what the code should do in every possible situation. This kind of test is much harder to write -- and that’s the best reason to do it. Thinking before coding is the real purpose of TDD, and this kind of testing drives us to think harder. Generative testing won’t just sharpen your test and your code: it can sharpen your mind.
- time: "5:30 pm"
name: "Remembering SCRC14, reprise"
speaker: SCRC
img: scrc.jpg
twitter: '@SteelCityRuby'
desc: >
Closing Remarks from the SCRC 2014 Team. Thank You!