-
Notifications
You must be signed in to change notification settings - Fork 1
/
concept.html
284 lines (246 loc) · 14.4 KB
/
concept.html
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
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<meta name="description" content="An experimental event taking place in the Swiss Alps">
<meta name="author" content="Swiss Mobile Club">
<title>The Swift Alps — Concept</title>
<!-- CSS -->
<link href="vendor/bootstrap/css/bootstrap.min.css" rel="stylesheet">
<link href="css/all.min.css" rel="stylesheet">
<link href="css/style.css" rel="stylesheet">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/Swiper/4.5.0/css/swiper.min.css">
<!-- JS -->
<script src="https://js.tito.io/v1" async=""></script>
</head>
<body id="page-top">
<!-- Navigation -->
<nav class="navbar navbar-expand-lg navbar-dark fixed-top navbar-default" id="mainNav">
<div class="container">
<a class="navbar-brand js-scroll-trigger" href="index.html">
<span class="logo-text"> Swift </span>
<img alt="Swift Alps logo" id="logoRed" src="img/logo-red.svg" class="p-0 d-none" style="height: 35px;">
<img alt="Swift Alps logo" id="logoWhite" src="img/logo.svg" class="p-0" style="height: 35px;">
<span class="logo-text"> Alps </span>
</a>
<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarResponsive"
aria-controls="navbarResponsive" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse" id="navbarResponsive">
<ul class="navbar-nav ml-auto">
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="index.html">4<sup>th</sup> Edition</a>
</li>
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="#motivation">Motivation</a>
</li>
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="#the-alps">The Alps</a>
</li>
</ul>
</div>
</div>
</nav>
<header id="hero" class="text-white pt-5">
<div class="py-5">
<h1 class="text-center h1 font-weight-bolder align-self-center display-4 pt-5 pb-md-5 pb-2">
The concept behind the <br class="d-sm-none d-block">Swift Alps.
</h1>
</div>
<img alt="mountains" src="img/mountains.svg" id="mountains">
</header>
<section id="rescue" class="text-dark">
<div class="container py-2">
<em>This post was originally published on <a
href="https://medium.com/@swiftalps/the-concept-behind-the-swift-alps-5b07e04c7ed1#.490lu02oz">Medium</a>
in 2016 prior to the first edition.</em>
</div>
</section>
<section id="intro" class="text-dark">
<div class="container py-1">
<p>The Swift Alps is an experimental conference, as stated in the website. The question is: why?</p>
What is the reason to experiment in the conference space? My goal for this post is to clarify
everything.<br />
</div>
</section>
<section class="text-dark">
<div class="container py-5">
<h2 id="motivation">Motivation</h2>
<p>There are many reasons to try something new in the conference space, some of these reasons are problems
speakers
and attendees are facing
at every event which are:</p>
<h3>Back to the routine</h3>
<p>After the conference has ended, it is very common to get back to the office, fire the code editor, try
some new
stuff and… just forget about it after a week.
All the new coolness just learned during the last event has been completely lost. Sometimes it could
also happen
that with a co-worker we are able to try something new for longer, but it’s usually only a single idea
that gets
adopted, forgetting the others N things learned during the conference. Experimenting and failing is part
of our
daily job, sometimes we have zero time, sometimes we have a little bit more, but <b>experimenting is the
first step
for adoption</b> and during regular confs it’s hard to do it.</p>
<h3>Collaboration</h3>
<p>We usually collaborate only with our co-workers and rarely, with people we don’t know personally over an
Open
Source project, but still, most of the time is just us and the code. In a classic conference the code on
the
screen seems interesting in a first place, but right after the talk is over, it’s unlikely to remember
it for
further usage. <b>Again, the coolness of the conference has been pretty much forgotten.</b></p>
<h3>Socialization</h3>
<p>Socializing is an important part of a conference, for some people is the main reason to go to a
conference, but
the chances to socialize are limited to breaks and after-party.
I never saw anybody starting a random-chat while somebody else was on stage presenting something, <b>this
is
generally rude</b>. What I also never saw is a couple of attendees socializing in front of a screen talking
about a
piece of code, which sounds strange, considering we spend 6–8 hours of our daily job time in front of a
screen.
</p>
<h3>Learning</h3>
<p>Learning is a complicated process, we go trough many steps while learning something. The current
conference model
makes learning hard, listening to somebody on a stage
is a small step, because the result is usually resume like “I just got aware of something cool”, leaving
in
front a lot of steps, but… how do we learn something? <b>Usually failing, while experimenting.</b>
Failure is part of our daily routine, we: code, fail, learn, fix, do it again. From other attendees we
can learn
a lot, most of the times we work with other people which we already know, sharing failures and learning
together. How many times we work with an absolute stranger who can teach us something new and cool or,
on
opposite, which we can teach something new? <b>Rarely.</b></p>
</div>
</section>
<section id="the-alps" class="text-dark">
<div class="container py-5">
<h2>The Alps</h2>
<p>This event is about <b>community</b>. Period. The major goal is to experiment with the Swift programming language
with all
the other attendees, trying to learn, while failing, as much as possible.
Ash Furrow wrote two amazing pieces about <a href="https://ashfurrow.com/blog/normalizing-struggle/">Normalizing Struggle</a> and later about <a href="https://ashfurrow.com/blog/empathetic-civilization/">Empathetic Civilization</a>,
which are
two great readings for somebody interested in joining us for this event. Both these articles are summarizing
what
<b>The Swift Alps</b> wants to tackle and what is going to be as event.</p>
<h2>The Format</h2>
<p>The format has been developed by many people, collaborating in a single document, trying to get the best of
other
formats like hackathons and un-conferences. What is the results?
As you might have seen in the <a href="index.html">official website</a> there are already some mentors (not speakers!) listed. These
mentors
are going to be an important part of the event, but the most important one is going to be the attendee —
you!</p>
<h3>Intro</h3>
The introduction is going to be a 5–7 minutes presentation from the mentors about a topic to run experiments
(examples: cross-platform Swift, server side Swift, testing, security, extensions, asynchronous programming,
etc…),
every attendee can then understand what the group is about and later join it for experiments.

<img src="img/concept/intro.png" class="py-2 img-fluid" role="presentation" />
<h3 class="py-2">Experimenting</h3>
<p>Every mentor is going to have a group of people, experimenting on the topic they prepared, maybe with a
final goal
in mind (examples: sample web app, Android app in Swift, fix of tedious bug in a widely used OS library,
Swift
Evolution Proposal, etc…), but they might also be totally open (bring your own bug). All the attendees are
going to
work with other people they probably never worked with, exchanging knowledge while normalizing the struggle.
We’ll
shake things up regularly and have 3–4 sessions with eachother. <b>What you will bring back home goes far
beyond what
you bring back home from a regular conference.</b></p>

<img src="img/concept/experimenting.png" class="py-2 img-fluid" role="presentation" />
<h3 class="py-2">Broadcasting</h3>
<p><b>Hacking is important, broadcasting knowledge even more.</b> One mentor is going to be dedicated to help
attendees
interested in presenting what they have done during the day to all the other attendees in a fire-talk, a 5
minutes
technical presentation about a topic, which are going to take place at the end of day (day 1 and 2).</p>

<img src="img/concept/broadcasting.png" class="py-2 img-fluid" role="presentation" />
<h3 class="py-2">Socialize</h3>
The day after the conference, we will organize social events, considering the location some options are
going to
likely be: hiking, culture visits, wine tasting, SPA, etc.. all these social events are going to be used to
talk
about what just learned and how the future of Swift looks like.
<h2 class="py-2">TL;DR</h2>
The format is basically the following things combined: best of confs + best of un-confs + best of hackatons
= The
Swift Alps.
<h2 class="py-2">Status</h2>
<p>We already have dates, which means we also have an amazing venue! On the official website there’s a link to
reserve
tickets. We are also working hard to give an extra option for transportation, which is going to be cheaper
than
public transportation, from the closest major airport: Geneva. We believe that also the journey from the
airport to
the town where the event will take place has to be part of the experience of the Alps.</p>
<p>For accommodation we have the plan to open a dedicated forum to discuss potential solutions, also to
encourage
sharing a chalet/apartment with other attendees whenever is possible.</p>
<p>We will release all the final details as soon as possible, with the complete list of mentors, so stay tuned, <b>we are
working hard for this event!</b></p>
Note: a big thanks to <a href="https://twitter.com/ashfurrow">Ash Furrow</a> for reviewing this and also for making the awesome graphics!
</div>
</section>
<!-- Footer -->
<footer class="py-5 bg-sa">
<div class="container">
<p class="m-0 text-center text-white">Copyright © 2020 Swiss Mobile Club</p>
</div>
<!-- /.container -->
</footer>
<!-- JS -->
<!-- Bootstrap core JavaScript -->
<script src="vendor/jquery/jquery.min.js"></script>
<script src="vendor/bootstrap/js/bootstrap.bundle.min.js"></script>
<!-- Plugin JavaScript -->
<script src="vendor/jquery-easing/jquery.easing.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/Swiper/4.5.0/js/swiper.min.js"></script>
<script src="js/scrolling-nav.js"></script>
<script type="text/javascript">
var mySwiper = new Swiper('.swiper-container', {
// Optional parameters
direction: 'horizontal',
slidesPerView: 3,
loop: true
})
function checkNavbar() {
if ($(window).scrollTop() > $("#mountains").position().top - 30) {
$('.logo-text').addClass('text-sa');
$('#logoWhite').addClass('d-none');
$('#logoRed').removeClass('d-none');
$('.navbar').addClass('navbar-light bg-white shadow-sm')
$('.navbar').removeClass('navbar-dark bg-dark')
}
}
$(document).ready(function () {
$(document).scroll(function () {
if ($(window).scrollTop() > $("#mountains").position().top - 30) {
$('.logo-text').addClass('text-sa');
$('#logoWhite').addClass('d-none');
$('#logoRed').removeClass('d-none');
$('.navbar').addClass('navbar-light bg-white shadow-sm')
$('.navbar').removeClass('navbar-dark bg-dark')
} else {
$('.logo-text').removeClass('text-sa');
$('#logoWhite').removeClass('d-none');
$('#logoRed').addClass('d-none');
$('.navbar').removeClass('navbar-light bg-white shadow-sm')
$('.navbar').addClass('navbar-dark')
}
});
});
</script>
</body>
</html>