Build an extraordinary career by sharing your knowledge
This is a modal window.
Das Video konnte nicht geladen werden, da entweder ein Server- oder Netzwerkfehler auftrat oder das Format nicht unterstützt wird.
Formale Metadaten
| Titel |
| |
| Serientitel | ||
| Anzahl der Teile | 170 | |
| Autor | ||
| Lizenz | CC-Namensnennung - keine kommerzielle Nutzung - Weitergabe unter gleichen Bedingungen 3.0 Unported: Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben | |
| Identifikatoren | 10.5446/50811 (DOI) | |
| Herausgeber | ||
| Erscheinungsjahr | ||
| Sprache |
Inhaltliche Metadaten
| Fachgebiet | ||
| Genre | ||
| Abstract |
|
NDC Oslo 2014103 / 170
2
3
5
6
8
11
12
16
21
22
23
27
31
35
37
42
43
45
47
48
49
50
52
54
56
57
58
61
65
66
67
71
74
77
80
81
83
84
85
87
88
89
90
91
94
95
96
97
98
100
102
107
108
112
114
115
116
118
120
121
122
123
126
127
128
130
133
135
137
138
139
140
141
142
143
144
145
147
148
149
150
153
155
156
157
158
159
160
161
162
163
166
169
170
00:00
DatenstrukturRechter WinkelClientGüte der AnpassungCodeSoftwareentwicklerMereologiePufferüberlaufSprachsyntheseComputerspielCoxeter-GruppeMatchingMeterVollständiger VerbandGeradeMultiplikationsoperatorCheat <Computerspiel>CodierungDateiformatBildverstehenOrdnung <Mathematik>Kollaboration <Informatik>BitRobotikPerspektivePeer-to-Peer-NetzBitrateWort <Informatik>MaschinenspracheMAPBenutzerbeteiligungOffice-PaketSchreib-Lese-KopfMathematikGarbentheorieHalbleiterspeicherCASE <Informatik>VideokonferenzGewicht <Ausgleichsrechnung>Digitale PhotographieTaskElement <Gruppentheorie>Kategorie <Mathematik>Jensen-MaßProzess <Informatik>MusterspracheLuenberger-BeobachterPunktVererbungshierarchieNP-hartes ProblemInterface <Schaltung>Quick-SortProgrammierungExogene VariableUmsetzung <Informatik>SystemaufrufDienst <Informatik>HardwareStichprobenumfangBrennen <Datenverarbeitung>Perfekte GruppeAggregatzustandSchlussregelZweiVerschlingungProjektive EbeneWasserdampftafelDifferenteSummengleichungAdressraumE-MailKontextbezogenes SystemFilter <Stochastik>Ein-AusgabeStützpunkt <Mathematik>Gruppe <Mathematik>Microsoft dot netBrowserHumanoider RoboterForcingSelbst organisierendes SystemBetrag <Mathematik>Total <Mathematik>Offene MengeFrequenzEreignishorizontAuswahlaxiomWeb SiteFontAppletZeitzoneEinsMehrrechnersystemTabelleKreisflächeRechenschieberBasis <Mathematik>TemplateDatenkompressionNeuroinformatikFeuchteleitungHilfesystemSoftwareBeamerZeichenvorratÜberlagerung <Mathematik>Demo <Programm>TexteditorProgrammiergerätSystemplattformFormale SpracheGrenzschichtablösungSmartphoneAuflösung <Mathematik>Physikalisches SystemAutorisierungVorlesung/Konferenz
Transkript: Englisch(automatisch erzeugt)
00:00
All right. So I hope that everybody is feeling a little bit more awake than I am. It was a good party last night. Today I'm going to talk about building an extraordinary career by sharing your knowledge. But first, where anybody at the cruise on Wednesday? Yeah.
00:26
What do you think of Norwegian summers? They suck. Yeah. So my name is Johannes Brodwall. I'm the chief scientist in Excelsoft. I've been working 15 years for the IT industry in Norway.
00:42
And then I realized, you know, Norwegian weather, it's kind of cold and wet. So now for the last two years, I've been working as the chief scientist for Excelsoft, which is based in Sri Lanka. So now I'm working for the Sri Lankan IT industry, which is, I think, a little bit of an extraordinary thing to have happen to your career.
01:04
I have been invited to speak at conferences all over Europe, in the United States, in India. And I've met interesting people. I've gone to interesting places as part of a job. And for me it all started with giving presentations, like I'm doing now.
01:32
So I'm hoping that you guys are here because you want to learn how to give presentations so that you can share your knowledge. And hopefully that might lead your
01:47
life in extraordinary ways and interesting ways that you hadn't thought of. So first, you guys at the overflow. So this will be a very interactive session. So you guys will probably not get so much out of it. So if you would do me a favor,
02:04
would you just stand up? Yeah, you. You. Stand up. All right. And then come on over to room six. It's behind the overflow, up the stairs, and you'll be having a lot more fun than if you were sitting right there. So that's I'm not sure if anybody's watching.
02:26
It will be interesting to see if anybody joins us. So the talk is about giving presentations. And I think I'll just start off with the method that I use to give presentations.
02:45
There are three things you need to give a good presentation. You need to want something. You need to know something. And you need to practice. That's all you need. So when it comes to what you want, it helps to get your to look at your audience and find out
03:12
what is it that my audience wants. So why am I here in front of this audience?
03:20
So I assume that you guys are here probably because you're slightly interested. Welcome. Because you're slightly interested in speaking in public. Who's slightly interested in speaking in public? Or speaking for your peers at your company. Or to get less nervous when you're
03:40
speaking. All right. So I'm then so that's one crucial element. But before I start with that, I want to ask one question first. And this is where you can start using your piece of paper. So think of your paper divided in three. And the first section is called
04:05
no. What does your audience know about what you're talking already? So in this case, I expect that most of you have given one or two talks. You don't feel comfortable as a speaker. You
04:20
have some idea of what's going on. And you certainly have seen some talks that you thought were pretty good. And then the second one is what do they want? So I think that you guys want to be more comfortable giving talks. And I think that you guys want to find some methods for giving talks. Does that match? All right. And now the third one. Can anybody guess what
04:51
the third part will be? Practice? No. That was the third. We're now at the first part. We're about exploring your passion. But you did remember the three parts. So the
05:05
three parts of giving a talk is finding out what you want, knowing it or structuring it, and then practice. In the first part, knowing what you want, there are three elements to it. The first is what do they know? The second is what do they want? And the third one is how do you come again? What they don't want. That's interesting. Yes. That is what I want.
05:29
And I want you guys to change something. As a speaker, you want somebody to change their behavior in some way. If you don't change your behavior, if you feel this was an inspiring talk
05:42
and then you don't do anything, well, then I haven't had any impact with my talk. So the third word to write down is how do they change? And how I want you to change. What I hope is that some of you, after seeing this talk, you will give a talk of your own in a situation when
06:03
you otherwise wouldn't. So I would like to see you give a talk at a conference not so long from now. All right. So now we have these three questions. And to explore these questions, it helps to collaborate. So this will be the hardest part of the talk for me. But I'm going
06:26
to have to ask you guys to stand up. All right. This always amazes me. Now I've already had you change in a little bit. All right. So everybody look around. Find someone that you don't know
06:42
already. And sit together with that person. So find someone that you don't know. And sit together. This is when you guys from the overflow really need to come up here. Because I don't think this
07:00
works so well on the overflow. But you can try. All right. So you haven't found somebody yet? You haven't found somebody? He wants you. He really wants you. Right? Yeah. He's a great guy. You should want to work with him. All right. So I will give you guys five minutes.
07:23
And the first person whose name is first in the alphabet shall interview the other person. And find out what can he talk about? What does the people he would talk to already know? What would the people he would talk to or she want? And how could he change their behavior? Do you
07:49
understand the task? Do you understand the task? Vaguely? Yep. And this is where you can use the notes. So find out what the other person can talk about. And I'll give you five minutes to
08:05
do so. All right. So you have a problem. Yeah. All right. Let's get started. Come on.
08:25
All right. Let's get up on stage. Yeah. Yeah. Come on. Ah. So hey, guys. So
08:43
these so doc, I want you to ask was it Denise? Jesse. So I want you to ask Jesse what could she talk about? What would her audience already know about what her topic? What would they want?
09:01
And if anybody's wondering, this would be his audience perspective. The other person's
11:17
audience perspective. What do they know already about the subject? So that was about five
13:42
minutes. And now I will swap. So I hope that you got some ideas of what the other person can talk about. It sounds like you couldn't believe that was possibly five minutes.
14:00
And so the other person will now ask will now find a topic. What do the audience already know about that topic? What do they want? Why would they go to the talk? And how could you see them change after the talk? So switch roles and another five minutes. Any questions
14:21
before we start? Was that a question or no? Just scratching your head. Good. Everybody's got somebody? Right. Let's get started. That was another five minutes. And so the purpose
17:21
of this now is to kind of explore a topic that we could talk about. So, Espen, did you speak with anybody who had an interesting topic? Hello? I spoke to this guy who, what he does
17:52
is he talks to people, to developers in Sri Lanka and interface between clients and he helps them communicate with each other and understand each other. I think that's
18:02
a good thing. So what does his audience already know about the subject? They probably know what it's like to be a customer and a customer experience but he wants to increase the understanding of each other. And what do the audience know? Sorry, what do they
18:21
want? The people who come to his talk, what do they want? No cheating. I always cheat. That's the best way to get things done. Sorry, I forgot. I think that they want to probably not feel like they're left with a responsibility after the conversation.
18:47
What you want to do is basically make people who are not so good to talk to people to help them talk to people. And how would they change after the talk? You probably know more about that than me. All right. So after the talk, they would
19:04
at the next interface with the customer, they probably would speak more. That's a simple change in behavior. Thank you very much, Aspen. I hope that everybody has got some idea of what the person next to you could talk about.
19:27
So let's start over here. So what's your name? Martin. And who were you interviewing? Ola. Ola. So what did Ola have to share?
19:43
He's fishing. He's a Swedish guy. I'm Norwegian. So we spoke in Norwegian and Swedish. I don't know if we're fishing. Is it fly fishing? Fly fishing. Yeah. Right. Cool. So you're speaking about fly fishing. What does this
20:01
audience know about it already? Probably nothing. So they know what it is, but they have never tried it. Yeah. What do they want? I hope they want to, it's probably impossible to learn it in the session, but maybe they should be interested in
20:22
it. And hopefully this guy could get them interested in it. So they would have a feeling of, they want to know whether this is something for them, I guess. Yep. And how would their behavior change after his talk?
20:41
Go and shop and buy fishing equipment. That's a change that you can measure. That's good. So if you give that talk and somebody ends up at the shop buying fishing equipment, something has happened. Very good. Thank you. All right. So what's your name? Håkan. Håkan. Yep. And who did you speak to? I spoke to Dimitri. Dimitri. And what could Dimitri speak about? He was interested in talking about performance.
21:05
In performance. Very good. So what does the audience already know about performance? Well, basically they wouldn't have good knowledge of writing programs, but maybe they're not so aware about how it affects performance. So they're developers, but they don't know so much about this specific subject. Good. So what
21:22
do they want? Well, they would probably know how to write more efficient code that uses the hardware better. Good. And now comes the difficult part for this kind of talk. How would they change after the talk? Well, hopefully they would change so that they are more aware about memory consumption. Right. So being aware is not a change.
21:42
How would they, what would they do differently? Well, they would probably write different code. They would write different code. And in what way would their code be different? More efficient. More efficient. So they probably would use some of the code examples, patterns, tools that Dimitri had to share.
22:04
So there we have a pretty specific change. Thank you. All right. Who's next? All right. What about you? What about you, doc? All right. So Jesse's talk was about
22:22
introducing play for problem solving. Right. And so what the audience might already know, they're probably already business owners and they probably encountered problems within their business. There's a good chance that they're also maybe parents. So they have some perspective on play from an observed. Right. And obviously at one point they were kids,
22:42
so they have a perspective on, hopefully they were, their perspective on play from actual, like, you know, being involved in it, if they're not still doing it. Right. Until the robots come. Yes. Yes. All right. So what do they want? Well, so what they would, I think what they would want out of it is, is like to find new ways of solving problems, to increase collaboration. Right. Maybe to understand how play is actually valuable. Right. So they would
23:06
want to understand how play is valuable. That's a pretty good summary. Yeah. All right. How would they change after the talk? So after the talk, they'd actually come away with, one, a better understanding of how play is valuable, but that's not a change. They'd actually have tools that they can then apply, you know, back at the office for problem
23:24
solving. So they would have, you know, actually new activities that they can do. So they would do those activities. Right. Right. That's a very specific change. Thank you. All right. Who wants to go next? We need, I think we need two more. All right. You're, you're, you look really nervous. What about you? What's your name?
23:45
Celia. Celia. So who did you speak to? Okay. What can you talk about? Video conference. And he's a C++ developer. So we want to talk about how to integrate the web and video
24:01
conference. Nice. Yeah. So what would this audience know about it already? I don't know. I thought, no. So one, one important question I guess would be, are they, are they developers? Yeah. And they probably want to know how to integrate video conferences.
24:23
So they are developers. They haven't worked with video conferencing before, and they want to know how to do that. All right. And how would they change after the talk? This is actually a pretty easy one. Yeah. They would know how to, but knowing is not a change. They would start to develop. Yeah. They would write some code
24:44
that would use video conferencing. Yes. So did my mic just cut out? Okay. Good. Great. We need one more. All right. So this is good. People have stopped looking away.
25:00
It's kind of, that means that you're getting more comfortable with this. So you're already becoming more comfortable with speaking with a crowd. All right. So what's your name? Okay. And you spoke to whom? He is an architect and he wants to talk about speaking to developers about coding,
25:28
coding style and code quality to improve the coding. And what would his audience know about it already? They would know how to code, but he wants to improve the coding techniques that are used in cross language in several languages, both on a Microsoft platform and Java.
25:43
Good. So that's both the know and the want part. And how would they change? Probably invite better codes. I'll accept that one. Write better code. So we can, we can probably be more specific about how we would know that they wrote better code.
26:02
All right. So we have a few talks here. And my memory is influenced by the fact that yesterday was a late night. So all right. So what was the first one? That was your talk, right? Your name was? And the talk was about fly fishing. Good. And the second one, was that you?
26:27
Sergei? Yes. Will come again. Dimitri. That's pretty embarrassing. Isn't it? It's like, uh, yeah. Nevermind. Dimitri. So, uh, can I call it Dima? Yeah.
26:42
So Dima, what was your talk again? Performance. All right. And the third one was that you, Jesse? All right. So Jesse, your talk was about play to solve problems. Good.
27:05
And were you next? And what was your talk about again? Good. And I forgot you. So what was your
27:21
name again? Knut. And you talked about video conferencing. Yes. Video conferencing on web. Good. Right. Did I forget anyone? Ah, good. So we have now talked about the passion part.
27:43
We've talked about finding out who you're going to speak to, what they want and how you want to change them. So the second thing we're going to talk about is the structure part, the knowledge that you have there. And if you're not very familiar with a talk, then the next time you give a talk, you have to use this format unless you don't want to.
28:04
So I use a format that I call three by three. We have three main subjects and each of those three subjects has three subtopics. So it looks like this. And I'm not going to, we don't have the time for everybody to
28:22
interview the other person about this, so we'll do it in a different way. So it might, so now we've got sort of a blank sheet of paper here and it might be a bit hard to get started with what should those three categories be. So I have some tricks. Welcome.
28:41
So the first one is, the first one, good thing I have more pens. The first trick is to have the headings be what, why and how. All right, so let's try that one out. So let's say, yeah, so fly fishing.
29:10
Could you say three things about what fly fishing is? So three things about what is fly fishing? Well, for me, it's a loophole and from the ordinary working days. Good. And
29:26
it gives me time to think and reflect. We're actually more on the why part. So more, what is it? Well, well, you fish, you hunt, I don't know. Yeah, you're fishing. So it's an outdoor activity, outdoor activity. That's the most important. Yeah. And do you have the fish
29:46
and what's different about fly fishing than other fishing? More expensive if you like to. It's a lifelong learning. You can never master it. So this is what you need to know about
30:05
fly fishing. It's an outdoors activity. It involves water and it's more expensive than other kinds of fishing. All right. And why would you want to do it? Now you're getting to the three reasons why. Well, okay. It's a getaway. I get new inputs on my thoughts and
30:25
it's a good exercise for my brain to leave something. And the second reason? The second reason would be discovering parts of the new parts of the world.
30:45
So you get to see places. Yeah. Yeah. Even if I thought I had been there before, if I just linger around there for a few hours, then I discover new things. And the third reason why?
31:06
Third reason why. So why should I take up fly fishing? I can be on my own. Yeah. So spend some time on your own. Great. And then the third question is how. So how do I get started? You have now sold me on fly fishing. What do I do? Well, you can borrow
31:26
equipment from me. You can follow me. I can take you to a beautiful place. Cool. And we can have some beer. Perfect. All right. So that's the talk on fly fishing. You now have the
31:41
structure for your talk on fly fishing. So that is the what, why, how structure. The second structure that I like to use is something I call the nightmare, the dream, and the road there. And I think that that could work pretty well for your talk, Dima. So you want the microphone? Oh, yes. Yes. Thank you. So what's the performance nightmare?
32:08
Three things about three things, you know, you're in the performance nightmare. Oh, well, I haven't seen any big project yet, which improves over years regarding performance. It usually gets worse, right? So your performance gets worse and worse. Yeah. Despite the fact
32:24
that computers get better and better. And my smartphone is my is now much more powerful than my first computer. Yeah. So that's, that's one thing that you're noticing. So, you know, you feel things that get worse, even though the software gets better. What's another thing that you notice you're in the nightmare? Oh, well, sometimes system requirement for some
32:47
programs. Here's insane. software we are working with, it requires 32 gigabytes of memory, at least, and stuff like that. Right. So your hardware bill keeps going up and up.
33:02
Yeah. And the third thing. Should we do something about like users and and and the third thing that from the old code basis I've seen, people quite often think more about style and how it reads now how the code looks and how it works. Oh, that's interesting. And without understanding how it works, sometimes it's really arguable what what is better in
33:25
which situations, right? So your, your performance getting worse and worse, your hardware cost is going up and up, and everybody is just focusing on what the code looks like, not what it does. All right, what would be a dream situation? Well, dream situation is like,
33:42
if software I've written five years ago, an old computer works now on the computer, which is five times faster, this software should work five times faster, right? Great. This is like you take this offer, you plop it on the new computer, and it's faster. Yay. Okay, the second thing. Oh, the second way, you know, you're in the dream scenario.
34:05
What's the second? Well, everyone thinks what he's doing. So people, and you're not so focused about this uncle Bob stuff that clean code. All right, I think that we're, but the balance
34:23
is good thing. I'm not saying I'm not saying it should be just one line of really performant code, which is just no one can read ever. And the third reason, you know, that you're in a, in the dream of performance, that I don't need to think about it anymore. Perfect. I love that.
34:40
So when you're in, so wouldn't it be great when you're, when you don't have to think about performance anymore? All right. So how do we get there? Well, three things. Oh, start examine what we have. And the second thing is we learn on mistakes. We know there are a few common patterns people follow all over again, and it leads to
35:04
worst performance ever. That's less just for the, for the sake of making the talk structure, we'll just find two of those patterns. So we say people, so you start caring about it and you start with this pattern and you start with that pattern.
35:20
Now you've got the structure for your talk. Yes. Great. Yes. And so yeah, we have time for a little bit of an anecdote. So this method that I'm using on you now was developed when I organized a lightning talk event. So I there were 10 Norwegian authors in the
35:46
book 97 things every developer needs to know, every programmer needs to know. And Kevin Henny, who was the editor of the book, he came to Norway for some event. And then I said, why don't we get everybody together? And everybody who contributed to the book will
36:02
give a lightning talk. This is great. And then we can meet up before and we can have some beers and we can have nice dinner and conversation together. And I, and I had email with everybody and they were setting off the time and I organized with a venue and a sponsor and we
36:20
got everything in place. And I'm like, Oh, finally, I got everything in place. We meet up two hours before at the restaurant. We have a beer, two beers, three beers, right? I'm not an alcoholic, but you might, you might be excused for thinking so in this context. And then 15 minutes before the event starts, the person next to me at the table says,
36:44
so what are you going to talk about? Oh, crap. So what you're, so I sometimes call this punch drunk or what do you call drunken style presentation? So you don't need a lot of preparation. You can throw together something
37:07
that looks pretty good. That being said, I don't recommend giving a presentation while you're drunk. All right. I think it might be, but, but I think my talk was about among the best ones actually. So in my humble opinion, of course. All right. So we had the
37:27
first style or the first way of using three by three style was the what the why and the how the second one was the dream the the nightmare, the dream and how to get there. And the
37:41
third style that I like to use is the past, the present and the future. So it doesn't necessarily work so well. But perhaps Knut, could we talk a little bit about video conferencing in the past, the present and the future? I think that would work. Maybe it's not
38:05
exactly your topic. So so we'll have to we'll have to wing it, but we'll try and demonstrate it. So here's the microphone. Thank you. It would be easier with the nightmare dream. All right. I hope this doesn't feel like the nightmare. Okay. So
38:25
so there is a so we start with the past. So what are three things about video conferencing and the web in the past? How was how this how did this used to be in the past? There were we didn't use web for conferencing. Yeah, at least not much. And nowadays,
38:46
three things about three things. So the web and video, the web and video conferencing weren't really the same. So let's talk a little bit more about video conferencing. So how was video conferencing before? It was hardware based, mostly. Good. And one more thing,
39:04
dedicated conference rooms. Great. So it was non web, it was hardware based, and it was dedicated conference rooms. How is it today? It's still somewhat the same, but now we have also Microsoft link. So you have link Yeah, which is then kind of
39:22
not conference room based. Right. Okay, good. Second thing about how it is today. So I mean, what what is the state of web and video conferencing right now?
39:42
It's changing now, but it's maybe not so much used. You have link on web. Yeah. And you got different technologies there, but it's not so much in use. Right. So you got link on web, you got different kind of technologies. Third thing about how it is today. Is it easy? Is it hard? I would say it's hard. So it's hard, but it's possible.
40:07
And the problem is solutions don't talk to each other quite often. So now we got some good things there. So today it is it is now coming solutions like link. It is possible,
40:23
but it's hard, but the solutions don't work together. All right. So what can we expect in the future from video conferencing on the web? What's in what's in? I would only be guessing. Yeah. Yes. Do that. Three guesses about the future.
40:41
Well, it would be easier if I could talk about the dream. Yeah. So what would be a dream of the future? That would be everyone uses standards. So link all talk together. Great. It's not the case. Yeah. So anything else? So how would it
41:00
be for the users? What would the users experience in the dream? If you are invited to a meeting, you'll get an email with the link. You click it, your web browser opens, and you're in the meeting with web audio and video. All right. I think that's good enough.
41:20
Thank you. All right. So that's the past, the present, and the future. So in the past, the web and the video were not working together. There were what else did we say? I don't remember. That's embarrassing. All right. So
41:40
let's move on. So I've talked about so the first what was the first step of giving a good talk? Who remembers the first step of giving a good talk? You have to know what you want. And you have to know the audience. You have to have a passion. I have three questions to find out what do you want? It is what do the people you talk
42:06
to already know? What do they want? And how do you want them to change? The second step is how do you structure what you know about it? And I like to structure it in this three by three format. I tell people you have to use it unless you don't want to.
42:22
It's a good place to start if you don't have a strong opinion. And I have three examples of that three by three format. It's the what, why, how. It's the dream, the nightmare, and how to get there. And it's the past, the present, and the future. Those are three ways to get you started. So if you're kind of stuck,
42:44
you don't know where to get started with your talk, you can just write down three points in one of those templates and then now you've got a passively good talk. The third part is practice. So what makes a good talk is the practice part.
43:01
And we do some things wrong when we practice. The first thing we do wrong is that we wait too long. If the first time you practice, if it doesn't feel like a total disaster, you've prepared for too long. So you can practice. It gets more powerful if you stand up and you speak out loud rather than practicing in your head. And it gets more powerful when you
43:23
practice many times. So we have to demonstrate this part as well. And now I'll give you as the audience a choice. So we've got five talks that we're aware of now. It is Ola talking about fly fishing. It is Dimitri talking about performance. It's Jesse talking about play to
43:44
solve problems. It's Kneut talking about video conferencing on the web. So I'll let you vote. Who would like to hear more about fly fishing? So that's one, two,
44:01
three, four. And this is no criticism to the topics. I don't think that there were many fly fishing enthusiasts here. So that's to be expected. So who would like to hear about performance tuning? One, two, three, four, five, six, seven, eight, nine, nine. All right.
44:23
Who would like to hear about using play to solve your problems? Oh, one, two, three, four, five, six, seven, eight, nine, 10, 11, 12, 13, 14, 15, 16, 17. Come again? I think so. But people can vote for more than one thing.
44:40
I wish I didn't tell you before. So I'm changing the rules. Yes. So you knew that I couldn't keep count anyway. So you've actually heard the same thing twice, didn't you? All right. And coding style. Who would like to hear more about coding style? One, two, three, four, five, six, seven, eight.
45:03
And who would like to hear more about video conferencing on the web? One, two, three, four, five, six. Six. So there is a specialized audience for your talk.
45:20
But I think six people is enough to kind of give the talk. Good. So it looks like it's up to you, Jesse. So now it's up to you. I know that you're more experienced with speaking, perhaps more experienced than I am. So maybe you should be standing here. Yeah, I know. So would you like to try and
45:43
perform your talk? Or do you want me to do it for you? All right. I think maybe if it was somebody else, I would kind of force you to do it. But I think for this purpose, it's better for me to do it. Yes. All right. So
46:02
which format do you guys want to have about using Play for Work? The why, how, the why, sorry, the what, why, how? The future, the past, present, future, or the dream, the nightmare, and the way there? I think it has a pretty self-evident one, right?
46:25
The first one? Yeah, I think so. All right. So the topic is, you said using Play at work? Using Play to solve problems. All right. So what is Play? Could you say three things?
46:45
Yeah. Yeah. So childlike and childish is not the same.
47:08
So why should I use Play to solve problems? So that reframe is about avoiding staleness?
47:26
Yep. I think that's, I've written that as two. So yeah. So yeah. Great.
47:53
All right. And how do you get, how do you do this? How do you do that?
48:10
Ah, right. So should we have that as one or two points? Two points. Cool. Yeah. And the third point? So how do we get started? Oh, great.
48:31
Hire a coach. All right. So this is the talk on using Play to solve problems.
48:42
All right. Using Play to solve problems. And we talked about, so welcome to this talk on solving Play for, using Play to solve problem. My name is Johannes Broadwall. And I think you are here because you want to experience that more childlike behavior at work as well.
49:05
So let's talk a little bit about using Play to solve problems. I will tell you first what is Play. Then I'll, in the context of problem solving, then I'll tell you a little bit about why you should use Play and then I'll let you know how to get started. All right. So you're ready?
49:24
Okay. So what is Play? First, Play is an activity that's fun and it's interactive. And it's something that we do together. So it's something that gets you laughing, you know, like you were when you were a child. And that's the second thing about Play is that it's childlike
49:42
and it brings back sort of the careless approach and the lack of filters that you can have as a child. And Play can often be in a sense like a game. So it can be a structured activity
50:01
with rules and with a little bit of competition in it. So why would you want to use Play to solve your problems? The first problem when you're solving problems, you get that, uh-huh, is that you're often stuck in sort of one perspective of the future. And by being playful,
50:24
you can take a wider look, you can reframe the problem, and you can avoid sort of thinking about the problem in the same stale way. The second thing is that you can break down the barriers. So instead of solving the problem alone, you get the help of your friends and your
50:41
co-workers, and you get it in a way that builds the team. So it's not just you solving the problem, it's the team solving the problem. And the third is that you get a new perspective on things. So you get, just like I said with the framing, and I don't really know how to phrase this in a
51:00
better way. So I hope you're convinced now that Play is a good thing to try. So how do you get started? The first thing is that you have to build that sort of open culture where people are open to new ideas. And you have to, that comes down to everyday interactions, and it comes
51:20
down to how you greet each other and how everybody acts on a day-to-day basis at work. And a very good way to get started with this is some improv techniques. So you can use improv, and one of my favorite techniques that I'd like you to try is called a one-word story.
51:41
And what you do is you set people in a circle, and you say, okay, now we're going to tell the story. And each person in the circle will only contribute one word at a time. And this, and then you go around the circle. And this is a very fun way to learn how to interact with a group. So that's one very cool technique. And there are many others.
52:02
And in order to get the sense of play into your culture and to facilitate these kind of workshops, it's really good to have a coach. And I happen to know a really good coach here, Jessie. And I think she's available for hire. So if you're interested, you can talk to her
52:20
after the talk. All right. So I told you a little bit about how, what Play is in the context of problem solving, why you should care and how to get started. And this will really change the way that you're working with your problems. So after this talk, I want you to go back, and I want you to try one or two improv techniques on your project. Thank you very much.
52:47
All right. So that was a little bit of a drunken style presentation. And when you try and do this a few more times, it becomes more rehearsed. So the reason I really would have liked some of you to give it is that it doesn't need to be this
53:07
polished the first time. This is what you get through practice. And all I needed to start practicing was my little sheet with my outline that I got from Jessie. So we've got about five minutes left of the time period. So I'd like to hear if there
53:28
are any questions before we round off. Yes. Ah, very good. So that's a very good question.
53:46
How do you get, yes, when you're giving a talk, repeat the questions. All right. So how do you get to give a talk? For the big conferences in Norway,
54:00
they have open call for papers. So you pay attention to the websites of the conferences that are close to you. And you submit a call for paper. There are three conferences that I know of that are interesting to submit call for papers for in Oslo. It's NDC, of course.
54:20
It's the Java zone conference, which has a lot of things that are in Java. And you know, even though the Java developers, we still love them, right? And there's the Smeedy conference, which is the Agile conference, which is lightning talk focus, which is good for this sort of stuff. So that's the way that you get noticed. The way you get accepted is by doing it again
54:43
and again and again. There's also lots of user groups in Oslo. And if you go to meetup.com, you'll find lots of user groups there. And most of the organizers there will be happy to get a suggestion for a topic that you can give a presentation on. And that's also something
55:04
that helps build your presentation. And then a third technique in that sense is, when you've given a few talks, you often get the chance to mingle with other speakers, which is one of the cool things about giving talks. And so, for example, now,
55:24
I got to hang out with Doc and Jesse on the boat on Wednesday. And now I could ask Doc, you know, you went to my talk. Did you like it? Absolutely. Could you recommend me for some of the conferences that you speak at? Cool. So that's how you get going. And feel free to
55:46
use me in that respect. Who's a great speaker and who's doing a lot of activities in Bergen. She recently I forwarded her email address to the Agile Adri conference, which meant that she
56:04
had a nice vacation in Croatia in April and was giving a talk at the same time. So I hope that gives you a few places both where to start and where you can go. That's a very good question. Other questions? Yes.
56:32
My worst speaking nightmare. I like that. Well, I've been speaking for if I tell you how long I've been speaking, you probably will feel that it takes too long to get
56:44
good or practice. I'm not going to say that. But my worst speaking nightmare but I learned slow. All right. My worst speaking nightmare was at JavaZone 2007 when as I arrive at the conference, I'm going to do a live demo. My computer turns out that the battery isn't working.
57:07
I've forgotten the charger. I get to borrow another computer, but it doesn't install the tools that I need on it. And this is the first talk of the day. I'm in the conference
57:22
room and I'm trying desperately to get this going. And then just to warm up the conference, they have a Norwegian cover band for Rammstein. And that's going on in the background. And normally I like this music style, but it didn't help calm me down, I would have to say.
57:44
And five minutes or actually it was 15 minutes before my talk is supposed to be there. I get this computer working and I'm like, yeah. And then the AV guy comes over and he says, I'm really sorry. We're having a problem with the projector. It will not be fixed before 20 minutes into your talk. What do you want to do?
58:07
And at that point in time, before I'm able to kind of think about this problem, there's five minutes before the talk. People are starting to show up. And what should I do?
58:21
What would you have done? Yeah. And the flip side of it, that was the first talk I gave without slides. And it's one of my best talks ever. And it inspired me to give talks without slides in the future. So one of the things that I hope that you've seen here is that
58:46
a talk is not your slides. Your presentation is not your slides. I've given this talk without having any slides. I could have added slides to it as well. And perhaps I will in the next talk. But before you know how to give the talk without slides,
59:01
you should focus on that. And then you can add the slides and make it even better. All right? That's all the time we had. So I hope you had fun. Because I want this to be interactive. And I want you now to take what you've got here and go forward, submit a talk
59:22
to a conference, give a talk at a user group or give a talk inside of your company. Before you stand up, you have some person next to you. And you have some ideas of what that person can talk about. So put that person's email address down on your note.
59:42
So Espen, what's your email address? ESL? So what I want you to do is that
01:00:00
few days from now or maybe a week from now after the conference, send an email to the guy that you spoke with today and ask how it's going with his talk. All right. I hope you enjoyed it. Enjoy the rest of your conference. Thank you very much.
01:00:30
To those of you who offered or were forced to give your talk, I've got a little gift. So for Chiatil and Dima and Jesse and Morten and Knut, we have our technical magazine on
01:00:54
Google Glass development, Android development, .NET development, link, other fun things.
01:01:00
So if you want a copy, it's all yours.