/
index.html
753 lines (605 loc) · 35.5 KB
/
index.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
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
<!--
FITC - DON'T GET COMFORTABLE
Powered by reveal.js
Everything else released under the DO WHAT THE FUCK YOU WANT TO public license.
For: http://fitc.ca/event/am17/
YOU WILL LEARN:
1) Why comfort is your enemy as a creative
2) How to properly burn your work to the ground, and why you should
3) Why failing still counts as finishing, and isn’t a bad thing
4) How to write improvised code displayed on huge projection screens while being watched by a thousand dancing people at 3am in a giant inflatable tent next to a 250ft radio telescope dish
5) Why you should never, ever, EVER live search for animated GIFs when you’re in front of an audience
-->
<html lang="en">
<head>
<meta charset="utf-8">
<title>FITC - DON'T GET COMFORTABLE</title>
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/danhett.css" id="theme">
<style type="text/css" media="screen">
.slides section.has-dark-background,
.slides section.has-dark-background h3 {
color: #fff;
}
.slides section.has-light-background,
.slides section.has-light-background h3 {
color: #000;
}
</style>
</head>
<body>
<div class="reveal">
<div class="slides">
<section data-background-image="">
<h1>HELLO</h1>
</section>
<section data-background-image="">
<h2>Dan Hett</h2>
<h4>TECHNOLOGIST/ARTIST</h4>
<aside class='notes'>
<p>- somewhere between creative programmer and digital artist</p>
<p>- regard myself as a creative who uses software</p>
<p>- not a software guy who stumbled into art</p>
</aside>
<!-- <aside class='notes'>I'm somewhere in between a creative programmer and digital artist. Put another way - I write code for a living, but I absolutely regard myself as a creative who happens to use software, rather than a software guy who stumbled into art and design.</aside> -->
</section>
<section>
<img src='assets/portfolio2.png'>
<aside class='notes'>
<p>- generally hate talks where someone stands on stage pointing at shiny stuff in their portfolio for an hour, so I won't do that</p>
<p>- almost not going to show you any finished work at all</p>
</aside>
<!-- <aside class='notes'>I generally hate talks where someone stands on stage for 45 minutes and jerks off about their portfolio, and so I'm not going to do that. This talk doesn't even have any finished work in it. I'm going to take you through some prototypes and diversions, there's a bit of code but don't worry - we'll be using it to make some noise - I hate technical talks too! </aside> -->
</section>
<section>
<img src='assets/ticklist0.jpg'>
<aside class='notes'>
<p>- I do like to make sure I stick to what I promised though</p>
<p>- these are the five things I said you would learn from this session, and learn them you shall</p>
<p>- and this talk is, I'm sure you're aware, called:</p>
</aside>
<!-- <aside class='notes'>I do like keeping on-message though, so these are the things I promised I would take us through today - we'll be ticking these off. Anyway, as a core message, I say:</aside> -->
</section>
<section data-background-image="">
<h2>DON'T GET COMFORTABLE</h2>
<aside class='notes'>
<p>- and the reason for this is that I have a single core message I want to share with you today</p>
</aside>
</section>
<section data-background-image="">
<h2>COMFORT IS YOUR ENEMY.</h2>
<aside class='notes'>
<p>- BEING PERFECTLY COMFORTABLE IS YOUR SINGLE BIGGEST ENEMY AS A CREATIVE</p>
<p>- whether your tool is code, photoshop, paint, the written word, or anything else, being nice and complacent and falling into easy habits is my absolute creative nemesis</p>
<p>- So much so, in fact, that putting myself in stressful and creatively challenging positions has almost become a defining characteristic of my work - or at least the work I'll show you today</p>
</aside>
<!-- <aside class='notes'>BEING COMFORTABLE IS YOUR BIGGEST ENEMY AS A CREATIVE.
Whether your tool is Javascript, Photoshop, a paintbrush or the written word - as ANY kind of creative, being nice and comfortable is your absolute fucking nemesis. The overwhelming desire to not get too complacent, and to constantly interogate, destroy and rebuild my tools and my craft, have become a sort of central defining characteristic of my practice.</aside> -->
</section>
<section data-background-image="">
<h2>HELLO, WORLD</h2>
<aside class='notes'>
<p>- my entry point to being a programer definitely shaped this</p>
<p>- didn't study computer science at all, I did DESIGN AND VISUAL ARTS</p>
<p>- fell into 'proper' programming very late on when my creative desires became more complex.</p>
</aside>
<!-- <aside class='notes'>My entry point to this stuff I think shaped a lot of why I feel this way. I actually didn't study computer science, at all, and in fact my degree is in Design and Visual Arts - I fell into programming very late on, when I needed to do more complicated things with Flash that bits and pieces of script weren't enough. I would never have chosen a Computer Science route, and I still wouldn't.</aside> -->
</section>
<section>
<img src='assets/violinist.jpg'>
<p>CLASSICALLY TRAINED</p>
<aside class='notes'>Not that there’s anything wrong with studying computer science of course. I think of normal programmers being sort of the classically trained musicians...</aside>
</section>
<section>
<img src='assets/guitarist.jpg'>
<p>CLASSIC, UNTRAINED</p>
<aside class='notes'>...to my three chord punk. Same core tools, wildly different approaches. And of course we need both, I don't want this kind of programmer working for my bank, and I don't want the other kind making my videogames, right?</aside>
</section>
<section>
<img src='assets/megaphone.jpg'>
<aside class='notes'>...except the music analogy falls down a little bit because classically trained musicians don't go to punk shows and tell the band they're not playing their instruments properly, which has ABSOLUTELY been my experience - but that's OK.</aside>
</section>
<section>
<img src='assets/baby.jpg'>
<aside class='notes'>
<p>- some of you might be vegetarian, some vegan - I exclusively subsist on the tears of crybaby neckbeards who tell me I'm doing things incorrectly</p>
<p>- for the most part, you don't need to be a world-beating rockstar coder to get your ideas out of your head and into reality (again, speaking creatively, if you're writing systems for jet fighters then study please)</p>
<p>- obviously I'm not saying NEVER LEARN ANYTHING (if you're going to throw the rulebook out of the window, you need to first own a copy), but there is definitely a lot of garbage that comes with programming that I now enjoy disregarding in favour of actually having fun and being productive</p>
</aside>
<!-- <aside class='notes'>Luckily, nowadays I actually exclusively subsist on the tears of crybaby neckbeards who tell me I'm doing all this incorrectly, or slightly inefficiently. What I did get from all this was a valuable lesson though - for the most part, you don’t NEED to be a classically trained programmer to get by. Obviously you need to learn, and there are good and bad ways to most things, but you don’t need to get dogmatic about most of this stuff AT ALL. </aside> -->
</section>
<section>
<img class='stretch' src='assets/trophy.jpg'>
<p>BULLSHIT WORLD CHAMP 2008</p>
<aside class='notes'>
<p>- problem with being late to the party is that I had to effectively lie to get my first gig</p>
<p>- everything went fine, my advice is always to say yes!</p>
<p>- all you really need is a can-do attitude, Google, and persistence. Persistence is almost everything! (NOT ON COMPANY TIME)</p>
</aside>
<!-- <aside class='notes'>My first gig in the industry was a local agency, and let's be real here: I effectively bullshitted my way into a deveopment job. The big lesson here is that within reason, you should always say YES when an opportunity for money and/or excitement pops up. (of course this doesn't apply if you're on a plane and someone shouts "oh my god is there a doctor on the plane"), but for something as easy as writing a bit of code, yeah definitely! Fuck being classically trained! Google and a 'can do' attitude will get you 80% of the way, and the rest is dogged persistence and a willingness to fail (ideally when not on company time - I've done both)</aside> -->
</section>
<section>
<img class='stretch' src='assets/storytime.jpg'>
<aside class='notes'>From there I went to work for BBC Children's in the UK. This was a huge scale job, creating apps for millions and millions of users. Very high intensity and high pressure. And also, the projects were HUGE in scale sometimes, which seems like a great thing on paper. There's a certain sort of romantic idea around pouring your heart and soul into a huge project for years - the cameraderie of the tough challenge, the late night pizzas, the intense process - all that stuff. But to be honest, I know some people thrive in that sort of scenario, but it wasn't for me.</aside>
</section>
<section>
<img class='stretch' src='assets/bafta1.jpg'>
<aside class='notes'>I even won a BAFTA, and picked up a few nominations. I only ever saw the BAFTA once, but it exists...</aside>
</section>
<section>
<img class='stretch' src='assets/bafta2.jpg'>
<aside class='notes'>...but I didn't let it go to my head. So, while that was a cool place to work, it was a very nailed-down environment in terms of tech - which is understandable, you need solid stuff if it's going out to millions of users, and I had to really really have my shit together. But really, I'm not a very processey kind of guy - if I never see another JIRA ticket in my life I'll be a happy man.</aside>
</section>
<section>
<img class='stretch' src='assets/rd1.jpg'>
<aside class='notes'>Finally I ended up getting a rare shot at a position for the BBC's prestigious Research and Development group, which I dived on. Now this is where things got interesting, because suddenly my colleagues were a mix of discliplines, skills and attitudes - far fewer classically trained programmers and a FAR MORE RENEGADES </aside>
</section>
<section>
<img class='stretch' src='assets/desk.jpg'>
<aside class='notes'>Suddenly I wasn't stuck at a desk, I was writing code in a TV studio, or at a festival! I was building things that weren't being stuck on the app store, or even facing users, but were instead just there to understand and test a problem out quickly and boldly. And this is the kind of thing I mean when I talk about not being comfortable. None of this was well-trodden tech, and none of the problems we were working on there were even remotely solved - and that's quite scary, but super fucking exciting. Part of striding forward is using the tools and languages you know well, in entirely unexpected ways.</aside>
</section>
<section>
<img class='stretch' src='assets/primer2.jpg'>
<p>BBC R&D - PRIMER / 'NEARLY LIVE'</p>
<aside class='notes'>Primer was a piece of research into creating a completely new workflow, that would allow the BBC to cover more events more cheaply - it used four massively high resolution and completely unmanned cameras to record a live event, and allowed a single operator to create and jump between virtual HD cameras defined from this huge wall of pixels. Really what this project did was create a whole new sort of craft role, between cameraman, director and editor, all in real time. </aside>
</section>
<section>
<img class='stretch' src='assets/primer3.jpg'>
<p>BBC R&D - PRIMER / 'NEARLY LIVE'</p>
<!-- <aside class='notes'>The 'nearly live' aspect came in when the operator was able to stop time - you set yourself a buffer window between the event happening and being broadcast, which allows you time to make fine-tuned edits and do things like blanking swearing out etc - some things have to be really live-live (like a football match) but for something like say, a music festival, even a few minutes of time to make decisions results in a hugely improved transmission quality. And, this is unmanned cameras and a single operator, so the costs are massively reduced, allowing the BBC (or anyone) to cover more events. This whole front end system was built using browser tech, which was a fairly intense technical undertaking but resulted in something that actually didn't even need to happen on site - I edited a live transmission from the Edinburgh festival while sitting hundreds of miles away in my office in Manchester.</aside> -->
</section>
<section>
<img class='stretch' src='assets/kitchen1.jpg'>
<p>BBC R&D - COOK-ALONG KITCHEN EXPERIENCE (CAKE!)</p>
</section>
<section>
<img class='stretch' src='assets/kitchen2.jpg'>
<p>BBC R&D - COOK-ALONG KITCHEN EXPERIENCE (CAKE!)</p>
</section>
<section>
<img class='stretch' src='assets/kitchen3.jpg'>
<p>BBC R&D - COOK-ALONG KITCHEN EXPERIENCE (CAKE!)</p>
<aside class='notes'>In many ways then, working for R&D was pretty much my perfect job, and so after a year I did what any sane, reasonable person would do... I quit.</aside>
</section>
<section>
<img src='assets/quit.jpg'>
<p>OMG</p>
<aside class='notes'>I quit, set up as a freelancer. There are a million small reasons why (money, freedom, and a burning desire to pursue my art), but actually for today's purposes...</aside>
</section>
<section>
<img class='stretch' src='assets/kit.jpg'>
<p>"Here. Build this."</p>
<aside class='notes'>...one of the main reasons for me making this move is, really, that I don't want to be at the end of the chain. Particularly as a developer there's this thing that happens where you get handed a fully-formed idea and are told 'here, build this'. And that, my friends, is comfortable. And if that's what you want to do, then that's totally cool, but for me this doesn't feel right. And to be fair, this was significantly less acute in BBC R&D, where we had a lot of agency to explore problems together and then solve them technically, we were still operating within research areas that someone else had defined - questions somebody else had asked. And so, I quit, and now I get to ask my own questions.</aside>
</section>
<section data-background-image="">
<h3>SIDE PROJECTS -> PROJECTS</h3>
<aside class='notes'>And of course, like I'm sure many of you in this room, I almost always have a bunch of side projects on the go. My wife calls mine a 'crippling addiction' to side projects, which I think is a bit unfair, but - what's happened now is that some of my 'side projects' have turned into just straight-up work projects now, which is a really good thing. And I couldn't have done that without taking the leap out of full time employment and into the void!</aside>
</section>
<section data-background-image="">
<h3>WHY SHORT PROJECTS?</h3>
<aside class='notes'>So my trajectory career-wise was that my projects started to get shorter and more intense as time went on, and I really liked this. Short projects (both side projects and for money) really suit me well - I have the attention span of a three year old, and I get bored really easily. And again, really that should make me an awful programmer, right? WRONG! There are two specific reasons why short achieveable projects are amazing:</aside>
</section>
<section data-background-image="">
<h3>1 - NEW PROJECT SMELL</h3>
</section>
<section data-background-image="">
<h3>2 - ACTUALLY FINISHING STUFF</h3>
</section>
<section>
<p>Oh, and... </p>
</section>
<section>
<img class='stretch' src='assets/isaac.jpg'>
</section>
<section>
<img class='stretch' src='assets/gamejam1.png'>
<aside class='notes'>Outside of work, I started getting a taste for really all-out rapid projects very early on, starting with things like creating one of the UK's biggest game jams. Now a game jam for those uninitiated is sort of a hackday for games, where you'll design and build and test a fun playable videogame in a few short days, or even hours! </aside>
</section>
<section>
<img class='stretch' src='assets/gamejam2.png'>
<aside class='notes'></aside>
</section>
<section>
<img class='stretch' src='assets/gamejam3.png'>
<aside class='notes'></aside>
</section>
<section>
<img class='stretch' src='assets/gamejam4.png'>
<aside class='notes'></aside>
</section>
<section>
<img class='stretch' src='assets/gamejam5.png'>
<aside class='notes'></aside>
</section>
<section>
<img src='assets/ticklist3.jpg'>
</section>
<section data-background-image="">
<h3>EVOLVING > CREATING</h3>
<aside class='notes'>One thing I did also want to get across is, while of course one of the things I most enjoy is taking technologies and using them for unintended purposes, I actually have better results when I don't start from scratch every time. In fact, I think one of my core acts as a creative nowadays is holding up a project or whatever, staring at it really hard, and asking myself: where can I take this now? Its very rare I truly draw a line under anything. For example: </aside>
</section>
<section>
<img class='stretch' src='assets/typography1.png'>
<aside class='notes'>A gallery in my home city was about to close, and move to a new huge space - they came to me and asked if we could spend some time re-interpreting some of their materials into new forms. This included tons of architectural plans, data, and some amazing typography, which is what we focused on.</aside>
</section>
<section>
<img class='stretch' src='assets/typography2.jpg'>
<aside class='notes'>We chose to not focus on the final pieces we designed, but actually tried to illustrate the process. Using a quick but brute-force algorithm, we created a process that would try, over hundreds of thousands of iterations, to reassemble a smal number of polygons into the finished form, as closely as possible. The code itself ended up being a THROWAWAY TOOL, and wasn't the product - the print was the product. This is important to me - as a programmer I'm often instinctively very protective over my code, my sources. But actually more often than not, it's fine to trash it once it's served it's purpose! </aside>
</section>
<section data-background-image="">
<h1>THE WORD 'ALGORITHM'</h1>
<aside class='notes'>Oh, and of course while we're talking about algorithms - I'm going to talk about algorithms a lot more during in this talk. I've heard it said that "algorithm" is a word that programmers use when they don't want to tell you what they did... </aside>
</section>
<section>
<img class='stretch' src='assets/piers.jpg'>
<aside class='notes'>...and I also quite enjoy this insight from respected digital culture commentator Piers Morgan.</aside>
</section>
<section>
<img class='stretch' src='assets/scribbler1.jpg'>
<aside class='notes'>Anyway. That tiny little project that took mere hours to do, really opened up conversation with the gallery - what it did was really illustrate clearly what you could do in very little time and money, just by being super clear about what you're trying to build, and not freaking out and wasting time worrying about the code too much! And so, they came to me and some colleagues in Studio Audience (who are in the house today!) to do something a bit bigger and a bit cooler!</aside>
</section>
<section>
<img class='stretch' src='assets/scribbler2.jpg'>
<aside class='notes'></aside>
</section>
<section>
<img class='stretch' src='assets/scribbler3.jpg'>
<aside class='notes'></aside>
</section>
<section>
<img class='stretch' src='assets/card1.png'>
<aside class='notes'></aside>
</section>
<section>
<img class='stretch' src='assets/card2.png'>
<aside class='notes'></aside>
</section>
<section>
<img class='stretch' src='assets/card3.png'>
<aside class='notes'></aside>
</section>
<section>
<img class='stretch' src='assets/card4.png'>
<aside class='notes'></aside>
</section>
<section>
<img class='stretch' src='assets/moleskine1.png'>
<aside class='notes'>Now the reason I wanted to show you the Scribbler wasn't just that it was a fun thing, but it also led onto something small but weird - I was approached to take part in the Manchester Moleskine project but was the only programmer taking part</aside>
</section>
<section>
<img class='stretch' src='assets/moleskine2.png'>
<aside class='notes'></aside>
</section>
<section>
<img class='stretch' src='assets/moleskine3.png'>
<aside class='notes'></aside>
</section>
<section>
<img class='stretch' src='assets/moleskine4.png'>
<aside class='notes'>Does it still count as open source if you write the code down by hand and stick it in a gallery? SHRUG</aside>
</section>
<section data-background-image="">
<h3>DO IT WRONG</h3>
<aside class='notes'>Aside from trying to sometimes operate at very high speed, one of the other ways in which I like to try and break out of my comfortable safe zone is to really try and contort, break, and genererally mis-use my tools and languages. Knowing something inside-out is sometimes exactly what you need, but often when I'm in a rut creatively, one of my strongest weapons is to reassess and remix and challenge what I've built before, or what I'm using. For example:</aside>
</section>
<section>
<p>twitter.com/NQguide</p>
<img class='stretch' src='assets/twitter1.png'>
<aside class='notes'>I build a lot of twitter bots, and other automated forms of mischief. There's something very satisfying about spinning something up and letting it go, and being hands-off while it causes mischief...</aside>
</section>
<section>
<p>twitter.com/_journorequest</p>
<img class='stretch' src='assets/twitter2.png'>
</section>
<section>
<p>twitter.com/nomanswhine</p>
<img class='stretch' src='assets/twitter3.png'>
</section>
<section>
<p>twitter.com/javascriptlibs</p>
<img class='stretch' src='assets/twitter4.png'>
</section>
<section>
<p>TRACERY</p>
<img class='stretch' src='assets/tracery.png'>
<aside class='notes'>As funny as these are, I'm showing you them because - the tech that powers these, is something that I've pulled out into some really ludicrous uses that it wasn't really designed for at all. It's call Tracery (by Kate Compton), and it's basically a grammar construction library that assembles patterns of words made from patterns of words, that can in turn be assembled from patterns of words, forever. You see how this works.</aside>
</section>
<section>
<p>TRACERY FLOW</p>
<img class='stretch' src='assets/botlogic1.png'>
</section>
<section>
<p>TRACERY GRAMMAR</p>
<img class='stretch' src='assets/botlogic2.png'>
</section>
<section>
<img class='stretch' src='assets/botlogic3.png'>
</section>
<section>
<img class='stretch' src='assets/lazycoder.png'>
</section>
<section>
<img class='stretch' src='assets/lazycoder2.png'>
</section>
<section>
<video controls>
<source data-src="assets/video/autorave2.mp4" type="video/mp4">
</video>
</section>
<section data-background-image="">
<h3>BREAK YOUR STUFF</h3>
<aside class='notes'>Taking tools and languages designed for one thing, and mis-shaping them into stupid new forms, is my jam. And I highly recommend this as a way of generating new ideas, approaches - ask yourself: how I can take this thing and contort the shit out of it until it does something else? And if it breaks, that's fine too - as long as you learned something, or it looked cool.</aside>
</section>
<section data-background-image="">
<h3>INTERROGATE YOUR PRACTICE</h3>
<aside class='notes'>And outside of your actual tools, this of course applies to your wider my practice I think - right down to how and where I work. Part of being comfortable for me is sitting with my feet on the desk in an office doing the same thing day in and day out - WE CAN FIX THAT TOO</aside>
</section>
<section data-background-image="">
<h3>LIVECODING</h3>
<aside class='notes'>Livecoding is something that I've been immersed in for a few years now, and actually is the perfect vehicle for me to demonstrate how I actually DO all this 'being uncomfortable, push your boundaries' stuff. And it's noisy and exciting too, which is always a plus.</aside>
</section>
<section data-background-image="">
<h3>LIVECODING<br />=/=<br />'LIVE CODING'</h3>
</section>
<section>
<video controls>
<source data-src="assets/video/cartoonfood.mp4" type="video/mp4">
</video>
</section>
<section>
<img class='stretch' src='assets/mizkai1.png'>
</section>
<section>
<img class='stretch' src='assets/mizkai2.png'>
</section>
<section>
<img class='stretch' src='assets/shirobon.png'>
</section>
<section data-background-image="">
<h3>REGULAR PROGRAMMING</h3>
</section>
<section>
<img class='stretch' src='assets/cyril1.png'>
</section>
<section>
<img class='stretch' src='assets/cyril2.png'>
</section>
<section>
<img class='stretch' src='assets/cyril3.png'>
</section>
<section>
<img class='stretch' src='assets/cyril4.png'>
</section>
<section data-background-image="">
<h3>TALK IS CHEAP:<br />WANNA SEE?</h3>
</section>
<section data-background-image="">
<h3>WTF IS HAPPENING HERE?</h3>
</section>
<section data-background-image="">
<h3>LIVE COMPILING</h3>
</section>
<section data-background-image="">
<h3>ERRORS?!</h3>
</section>
<section data-background-image="">
<h3>WHY WOULD YOU DO THIS</h3>
</section>
<section data-background-image="">
<h3>TOTAL PROCESS RESET</h3>
</section>
<section data-background-image="">
<h3>IMMEDIACY</h3>
</section>
<section data-background-image="">
<h3>IMPROVISATION</h3>
</section>
<section data-background-image="">
<h3>TRANSIENCE</h3>
</section>
<section>
<img src='assets/ticklist2.jpg'>
</section>
<section data-background-image="">
<h3>LIVECODING<br />KILLS<br />POSERS</h3>
</section>
<section>
<img class='stretch' src='assets/posers.jpg'>
</section>
<section>
<img class='stretch' src='assets/algologo.jpg'>
</section>
<section data-background-image="">
<h3>ALGO as in 'ALGORITHM'</h3>
</section>
<section data-background-image="">
<h3>RAVE as in 'RAVE'</h3>
</section>
<section>
<video controls>
<source data-src="assets/video/algorave.mp4" type="video/mp4">
</video>
</section>
<section data-background-image="">
<h4>SOUNDS WHOLLY OR PREDOMINANTLY CHARACTERISED BY THE EMISSION OF A SUCCESSION OF REPETITIVE CONDITIONALS</h4>
<aside class='notes'>Taken from the Criminal Justice and Order Act 1994 when the UK government had to come up with a legal definition of music, in order to shut down the huge rave scene. This is something I really like as a nod to the electronic music that's come before - Algorave is an evolution, not a new form!</aside>
</section>
<section>
<img class='stretch' src='assets/press-wired.png'>
</section>
<section>
<img class='stretch' src='assets/press-dazed.png'>
</section>
<section>
<img class='stretch' src='assets/press-vice.png'>
</section>
<section>
<img class='stretch' src='assets/press-mixmag.png'>
</section>
<section data-background-image="">
<h3>THE MANIFESTO</h3>
<aside class='notes'>
<p>- "Code should be seen as well as heard, underlying algorithms viewed as well as their visual outcome"</p>
<p>- "It is not necessary for a lay audience to understand the code to appreciate it, much as it is not necessary to know how to play guitar in order to appreciate watching a guitar performance."</p>
</aside>
</section>
<section>
<img class='stretch' src='assets/bluedot1.jpg'>
</section>
<section>
<img class='stretch' src='assets/bluedot2.jpg'>
</section>
<section>
<img src='assets/ticklist4.jpg'>
</section>
<section>
<img class='stretch' src='assets/tito.png'>
</section>
<section data-background-image="">
<h3>LIVECODE AND VJ</h3>
</section>
<section>
<img class='stretch' src='assets/vj1.png'>
</section>
<section data-background-image="">
<h3>CHALLENGE TRADITION</h3>
</section>
<section>
<p>A NOTE ON GIFS</p>
<img class='stretch' src='assets/fence.gif'>
</section>
<section>
<img src='assets/ticklist5.jpg'>
</section>
<section>
<img class='stretch' src='assets/vj2.png'>
</section>
<section>
<img class='stretch' src='assets/vj3.png'>
</section>
<section>
<img class='stretch' src='assets/vj4.png'>
</section>
<section>
<img class='stretch' src='assets/vj5.png'>
</section>
<section data-background-image="">
<h3>EVOLVE OR DIE:<br />WHERE NEXT?</h3>
</section>
<section>
<img class='stretch' src='assets/prints1.png'>
</section>
<section>
<img class='stretch' src='assets/prints2.png'>
</section>
<section>
<img class='stretch' src='assets/prints3.png'>
</section>
<section>
<img class='stretch' src='assets/prints4.png'>
</section>
<section>
<img class='stretch' src='assets/prints5.png'>
</section>
<section>
<img class='stretch' src='assets/prints6.png'>
</section>
<section>
<img class='stretch' src='assets/home1.png'>
</section>
<section>
<img class='stretch' src='assets/home2.png'>
</section>
<section>
<img class='stretch' src='assets/home3.png'>
</section>
<section data-background-image="">
<h3>THE LICENSE</h3>
</section>
<section>
<img class='stretch' src='assets/license.png'>
</section>
<section data-background-image="">
<h3>IN SHORT:</h3>
<aside class='notes'>I am not old, experience, or wise enough to give really useful advice on anything, but - what I can do is sum up what I think are the cores to my creative approach.</aside>
</section>
<section data-background-image="">
<h3>DON'T GET COMFORTABLE</h3>
<aside class='notes'>Being comfortable and complacent is your absolute number one enemy as a creative. And you gotta fight it! If you have even the faintest desire to grow as a practitioner you have to slay that compulsion to just put your feet up (literally or metaphorically).</aside>
</section>
<section>
<img src='assets/ticklist1.jpg'>
</section>
<section data-background-image="">
<h3>DESTROY, REBUILD, DESTROY AGAIN</h3>
<aside class='notes'>The old line about 'rules are made to be broken' isn't enough - both the rules, and the tools you have at your disposal (be that software, technique, or mindset), can and should be destroyed, dismantled, reconfigured and rebuilt constantly. THE ONLY RULES ARE THE ONES WE ENFORCE ON OURSELVES </aside>
</section>
<section data-background-image="">
<h3>STAY PUNK</h3>
<aside class='notes'>And I think this whole mindset should permeate every part of the process, it's not just about smashing up code and breaking your tools. We're all creatives here: you can and should be as bold and defiant and sure as you can be in your ideas, in the way you approach a problem, the way in which you work. You're a creative, you have unlimited opportunity to do as much amazing interesting beautiful work as you can - so be punk. At least in spirit. Don't waste it being Coldplay. You don't want to be Coldplay, do you?</aside>
</section>
<section data-background-image="">
<h3>A MILLION RIGHT WAYS</h3>
<aside class='notes'>Do not listen to your inner worrier, the book author, or ANY fucking neckbeard on the internet: there are plenty of ways to do something wrong of course, but the real secret is that there's a million ways to do something right. If it feels right, looks right, and does the job - you're doing it right. (again, if you get a job writing code for a bank, or NASA, then at that point you should stop accepting freewheeling career advice from a hungover guy on a stage in Amsterdam)</aside>
</section>
<section data-background-image="">
<h3>AND FINALLY...</h3>
<aside class='notes'>I'd like to end on a quote, not by a respected designer or rockstar developer, but by that great voice of our time... Doug Stanhope.</aside>
</section>
<section>
<img class='stretch' src='assets/stanhope.jpg'>
<aside class='notes'>
In 1960, the New York Giants American football team hired a kicker from Hungary. This is back when, if you watch old black and white NFL footage, they used to kick field goals really stupid and stiff, like a kid with rickets. And that was the norm, until they finally hired this soccer player from Hungary, and he came over and sees all these people - it had to be a lot of pressure, you sail all the way on a boat from Hungary to be a kicker, everyone else is kicking like an idiot! He says - "Well, I don't WANNA have to kick like an idiot just because that's how it's done". So finally, he says "Fuck em, I'm gonna kick like I kick". And he's the first guy to kick how they now kick field goals, soccer style. He didn't know he was a genius, he just said "I don't wanna look like an asshole, so I'm gonna muster up the courage to kick like I kick despite the peer pressure". He revolutionised every team in the NFL just by being brave, a little tiny bit. So whatever it is, if you think you have a brilliant idea, don't be afraid to be wrong... </aside>
</section>
<section data-background-image="">
<h3>KICK LIKE YOU KICK...</h3>
</section>
<section data-background-image="">
<h3>FUCK 'EM IF THEY <br />DON'T LIKE IT.</h3>
</section>
<section data-background-image="">
<h3>THANK YOU.</h3>
<h4>@DANHETT</h4>
</section>
</div>
</div>
<script>
// Randomly selects a background for slides.
getRandomImage = function() {
return "assets/bg/bg" + Math.ceil(Math.random() * 82) + ".jpg"
}
var elems = document.body.getElementsByTagName("*");
for(var i = 0; i < elems.length; i++) {
if(elems[i].getAttribute("data-background-image") === "")
elems[i].setAttribute("data-background-image", getRandomImage());
}
</script>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script src="plugin/notes/notes.js"></script>
<script>
Reveal.initialize({
center: true,
history: true,
progress: false,
controls: false,
showNotes: false,
transition: 'fade', // none/fade/slide/convex/concave/zoom
transitionSpeed: 'slow'
});
/*
Reveal.configure({
keyboard: {
13: 'next', // go to the next slide when the ENTER key is pressed
27: function() {}, // do something custom when ESC is pressed
32: function(){
if (video.paused == true) video.play();
else video.pause();
}
}
});
var video = document.getElementById('video');
*/
</script>
</body>
</html>