Primero, voy a presentar a mí mismo, soy Harold, soy un ingeniero de software, soy un
desarrollador de Fullstack y un desarrollador negativo de iOS.
Como estoy invitando aquí, aparentemente soy un profe, no sé qué significa esta invitación.
No, soy el co-founder de CodeWorks y profesor en el libro de desarrolladores.
Es una escuela programada y tenemos un problema muy inmersivo y muy difícil que es tres
meses, seis días de semana, 11 horas de día.
Así que si quieres feedback, después de eso, es sobre la desarrollación de fullstack de
iOS.
Utiliza frameworks like XPS, Koa, vamos a tomar un pick into frameworks like AngularJS
o React and Redux, ok?
So you will become a professional developer in three months with HidingFest at the end.
We have two students here of CodeWorks today, so if they look tired, ok, don't worry,
it's basically don't fall down, ok, so about, ok, I'm going to talk about this thing, failing
faster.
First of all, I want to tell a story, ok?
Some years ago, I think four years ago, along with some partners, we created a consultancy
firm that worked on iOS native development and later Android native development and web
development.
It's called LaFosca, hello, it's my partner from LaFosca, we started running, by the way.
Ok, we created that new business, ok, and when, I just ended the university there, I
had prior, like, I don't know, seven years of experience in IT when I ended the universities
to this, and we created that, and at that time I was pretty amazed about some of the startups
of San Francisco and all the movement that was coming, and obviously, I wanted to make
a very cool business.
And I was amazed by a concept by Google that some of you may have heard about, that is
the Google 20%.
Do you know about that, ok, it's like that cool stuff that, yeah, it's in the next slide.
So it was a very good idea, I mean, they are giving 20% of the time to their employees
to work, and they think that it's good for the company, ok, and it was a way to, I mean,
take advantage of the creativity of your employees, ok, of that development team.
And Gmail, NatSense, ok, it was good of, but look at the products that were out from
that program, ok.
So this is so nice, but eventually, ok, they cut it at the program, ok.
Marisa Meyer, who is the CEO of Yahoo, and it was one of the first 20 employees of Google,
said that it was the 20% of the 120%, ok.
Some workers started to be worried about the productivity and results on the analytics.
Google has like Google analytics inside their teams to analyze the productivity of workers,
ok.
So they were spending the 20%, they are not producing that much for the main business
of their teams.
And as you say, it doesn't exist anymore, ok.
So it was a very cool idea, but it's not perfect, ok.
But, ok, I wanted to apply it into my company as well, so we said, ok, let's apply it,
what could go wrong, right.
So we applied it, we made basically this, it's giving the 20% of freedom, completely
freedom to our employees to do whatever they want.
But it was nice, but the time was spent improving personal skills, refactoring the code that
we made on the other weekdays, and trying new technologies, ok.
I mean, this is nice actually, it's not by news, because the quality of our developers
was improving, ok.
But this is not what we wanted, because we weren't seeing that they made all of this
in the main business hours.
We wanted them to be creative, ok.
Also we found ourselves giving ideas to our employees, because they didn't know what to
do.
It's like a very big game, and it's like, I don't know what to do, I don't have ideas,
and it's like, I don't know what to do.
And they came to us to ask for something to do, and it's like, we don't have to answer
this question.
I mean, it's freedom, ok, it's meant to be freedom.
And non-developers were not using it, Eloi, designer, so he was not using it, ok.
Ok.
So we iterate that into presentations.
Instead of completely freedom, the guys were meant to do some presentations at the end of
the day, or maybe not at the end of the day, but every two weeks.
If you're working with something, we want to know what you're working on, and if you
have like a goal, like making a presentation, then you are more focused on that, ok.
The results were similar to that, 20%, ok.
We only solved the refactor thing, because it was made in business, and it's like, I'm
not talking about, I made that refactor, ok.
Ok, but, not all are bad news, ok.
There were some cool stuff that was the output of that thing, ok.
Like we were creating an app for a blogger, and in the main business hour, we were software
queues on that app, but the guy that was responsible of that app had an idea of creating the face
cropper, ok.
That is that all the images of that blog, in the Android screen, were not centered, ok.
They were centered, in the center of the image, but this is not the important thing.
The important thing is the face, so he developed, in two Fridays, the Android face cropper.
When you give it an image, it marks the center of the face, and it was so cool.
It's an open source project, and it has 426 stars in GitHub, and this is so nice.
This is one of the things that I am most proud of, about the output of these things.
So also in the presentation, some people was not motivated about it, and sometimes we kept
working on our mind business.
Also we kept receiving more and more work, we were growing, and then we had a lot of work,
and maybe as a person, because I had that 20% too, and I was preferring to do the business
and get the things done with the clients, and let's forget about that 20% for me.
So we tried it again, and we tried something more aggressive, hackathons, ok.
We went so cool, ok, let's start hackathons, every one or two weeks an organization prepared
a topic for a hackathon, like this week we are going to work on Internet of Things, Food
or Facebook.
So every one or two Fridays, we created two teams, two separated teams for a day, ok,
and they are meant to compete for creating the most cool thing at the day, ok, with that
topic.
So at the end of the day, it was composed by non-participants, non-participants were
non-technical guys, hello, the winners were given funny prizes, ok, and people with that
got really, really motivated.
It was fun, it was a fun thing in the company, ok, Fridays were really special.
But we found out that it was too much work for the organizer, we are talking about a
small team, ok, about 10 people, and this guy has something to do also, and that guy
had to prepare the event during the weekdays, ok, the other weekdays, not the 30%.
And then we found out also that as we were giving a fixed topic, we were killing creativity,
ok, well, it's like, work with Facebook, I mean, ok, maybe this is an open topic,
but work with food, it's like, ok, but I'm giving, I mean, I have to be creative, but
in this thing, it was killing, also the pressure was stopping it, I mean, it was a hackathon,
you started at 9, maybe you ended at 7, it's like, you have to do that in that hours, you
have to end up at 6, because we have to deliver, ok.
So the pressure was killing that creativity.
So we gave up, ok, actually it was not a decision, I mean, it was a delayed decision,
it's like, ok, this week no, this week later, this week later.
So we ended up by not working on that 30%, ok.
So, ok, I think this is misplaced, ok.
So at some point, we found, I mean, at some point in the company, in the future, I mean,
at some time, some people, some teammates and I found us in a position that we were so
interested in games.
Actually we received a job to create a very basic game in Unity, so we made it, we are
so active, we made it, we launched it, we liked it, and then we said, ok, why don't
we work on games, and we give it a try.
So I started to think again about that 20%.
So there was a movement also that creating that La Fosca Labs to represent that 20%,
ok.
It's like a little, little committee of keeping or allowing or embracing creativity into our
company.
So we created the fail faster team inside La Fosca, ok.
This is what I talked about, ok.
So we had, we have some problems with that, ok.
We want to start making our own games, but we had no game designer, ok.
Game designer is not anyone that, a person that make the assets, ok.
This is a designer and we had it.
We had no game designer, no one that says, make this game that has this mechanics and
you have to, it's, you have to make, when you push about and you have to make this red
little person to jump and you can go inside to the tunnels and, ok.
We haven't that guy, and we had no ideas.
So I started to make a little research on game designing, ok.
And I ended up with these two guys, ok.
The first one is the, I mean, the left one is for your perspective, because I said right.
The left guy is a YouTuber, is a YouTube channel, it's called Extra Credits, that they
are making every week video about game designing, or about game design concepts, or, or analysis,
ok.
But he explains so well.
So one of the topics that he was talking about is about failing faster, ok.
Look at that video, try to search fail fa, in YouTube fail faster, and it's the first
video that came out, ok, and it's, it's bringing this guy.
It was focused on game designing, ok.
And this other guy is Isakasimov, ok, that apparently some friend of him, for those who
doesn't know him, it's that, ok, it's a novelist of science fiction, also a chemist,
and, I mean, he was talking about the effects of internet in the society on 1988, ok.
We are talking about this guy, ok.
So what I found about this guy is that a friend of him found a letter that he made
for, for him and his team, when he invited Isakasimov into a group of research of anti-missiles,
anti-missiles protection of the US government state, ok.
So his guy was invited into brainstorming sessions about how to be creative, about anti-missiles
program, ok, about military topics, and he accepts it, but he went to, for two times,
to that brainstorming sessions, and he left, he's like, ok, I, I declined this thing for
two reasons.
One is, one reason mainly is that about knowing about the secrets of the government, about
military topics, was killing his creativity, about thinking about the future, ok.
If he knew the things that were secret, and it has to be known several years after, it
will kill his creativity.
So he sent a letter about how to do these brainstorming sessions for his friend.
He's like, drive it like this, ok.
So we're going to learn about feeling faster from this guy, and how to make a brainstorming
correctly by this guy, ok.
So about feeling faster, this guy is explaining about the feeling faster concept in the video
about how to design games, ok, and the first thing is that no idea is fully formed, no idea
is good, ok, if, I mean, I wonder, that moment when some game designer is facing their team
and saying, let's do a game about throwing birds into pigs, and the other say like, oh,
it's a billion dollar idea, ok, so they made it, ok, and they earn that amount of money
or more.
I mean, I'm talking about angry birds, ok.
So the moment that he had this idea, it was a very stupid idea, that's it, ok.
But they go after the idea, and they iterate over there.
When you, you can make this exercise on all the games, I mean, blue hedgehog running like
crazy, collecting rings, it's not a good idea, ok.
So here is that, ok, fail even before you have a line of code, ok, I mean, you can work
with some cardboard or something like this, you want to make a game, a video game, but
you can play with cardboard, ok, this apply also to our ideas as developers, like for
that facecropper, ok.
If you have an idea of a library as a developer, just try it, don't care about how the API
is designed, let's ship it and let's these guys on GitHub create an issue and say about
I copy paste that and it's not working, ok, and some issues like that, but some guy at
some point will create a new issue on GitHub that says, why don't you make this API working
like this or working the other, ok.
So if you have an idea, don't care about if it's well typed or if you're not linking
things correctly or your code is not beautiful, just ship it and let the other try.
Ok, a basic, a very important concept here also is expose yourself, ok, one of the things
that worry us the most about shipping ideas is about what the others are saying or will
say about our idea.
My idea is not good enough so I'm not talking to you and I'm not sharing you my idea because
I'm afraid about you saying that it's a very bad idea, don't care about that.
I mean, yeah, listen to what they are saying, ok, but your idea, if you embrace the idea,
the concept that your idea is not perfect, you won't be hurt by that, ok.
Don't protect your ideas, if someone is giving you feedback, listen to them, ok, and change
your idea, and don't protect your ego, ok, because maybe if you're protecting your ideas
because you're protecting your ego, and it's like, I had this idea and the other say, ok,
this is not that funny as you think, but you say, ok, you make the relation about this
idea, this is me, so he's saying that I'm a fool, and he's like, you don't have an idea,
so you quit, or the conversation, and that's it, ok.
So don't protect your ego, the other one is the basic thing, ship, ship, ship, it's
the only thing that you have to do, ship, ok, let's close this minimal version and then
let the other try it, ok, and every failure is another chance to get it right, ok, you
will learn about this failure, so you will be learning on every failure, if you fail
about, if you're shipping, not a game, an app, and it fails, it doesn't fail, it's not
a Boolean, ok, it has its data, it's failing, but what part is failing, it's failing the
onboarding, it's failing the, from this part, from this other, ok, it's not a Boolean,
that's it, ok, and then the other guy, this guy is talking to us about the brainstorming,
about how to create new ideas, ok, so we are thinking about, I mean I think that when
he wrote this letter, he wrote this, he wrote this letter, the brainstorming concept was
not embedded yet, the concept, I mean he has the, I mean this guy referred to celebration
sessions, as a brainstorm session, ok, celebration sessions, it's like, ok, it's good, so he
was talking about, ok, how can you get along some people to create new ideas, ok, so this
is the, you can read the letter, it's so interesting, he's talking about, he's getting these ideas,
about two people getting the same brilliant idea at the same time, like Darwin and I don't
know the other scientist that was, that derived to the same idea of evolution, ok, it's so
interesting, read it, if you, if you can, if you want, but the main things, ok, the conclusions
of that letter is that the brainstorming sessions, first of all, are opt in, ok, it's completely
optional, ok, because if you are making or obligating somebody to be in a brainstorming
session, it's like, what I'm doing here, I don't, I don't want to create new ideas,
or it's completely optional, he has to be engaged by default, ok, by himself, he has
to be motivated, first, the other one is work in isolation, ok, we're talking about brainstorming
session, what are you talking to me, I mean, isolation, group, it's not the case, he's
talking about working before the brainstorming session, everybody in this brainstorming session
has to be work alone before and prepare some ideas, ok, and why is that, because celebration
sessions aren't for creation, but for connecting ideas, so if we start a brainstorming session
with all of us guys, and we start, ok, let's try, take crazy things, you're perfect brainstorming,
ok, but you are not on every, on every, on every company, ok, it's like, it's perfect
silence, and it's like, yeah, you can start saying about pizza toppings, but it's like,
it's not the case, ok, so first of all, we can start, a good icebreaker is start talking
about the ideas that we bring into this session, ok, this is the perfect point of starting
of a brainstorming session, also a relaxed ambient, ok, and so the brainstorming session
is meant to, ok, I listen to all you, and then I start connecting ideas, and you all
do the same, ok, and it's like, ok, but if we take this thing, and we take this other,
maybe it's, ok, blah, blah, blah, blah, and we start discussing.
So also it has to be in a relaxed ambient, ok, as much as possible, here, not in the
meeting room, also it's recommendable not to be more than 5 people, ok, because the
creativity is stopped when you feel pressure, not only productivity pressure, but social
pressure, ok, it's about saying cheesecake, ok, but if some of you, you know, you're not,
but some of you may seem like you are, look like a fool if you say cheesecake, but it's
not the case, because we are in a brainstorming session, ok, but it occurs, so if we are in
a closed group of 5 people, it's better to make 20 brainstorming sessions of 5 people
that making it all together, ok, also no sense of responsibility, not being paid, ok,
I think this is the very best point of that thing, ok, the sense of responsibility is also
killing creativity, because I've been paid to have great ideas, my pressure is great,
I mean, it's like, ok, I have to earn that money, so I have to create this idea, I have
to be creative, and in the meantime I'm thinking about it, I'm not creating the ideas, instead
we can have a workaround here and pay for the action items, ok, the action items of
this brainstorming session, if we are talking about doing something, if we arrive to some
nice idea, we think that could work, then it's related to some work, it's like, ok,
implement it, do it, develop it, ok, so this action item is where you have to pay them,
ok, we will relate it, this is difficult for now, I mean, for our context, but we will
relate it in the after, and they have to be guided by psychoanalysts, ok, how many psychoanalysts
are in here, I put in brackets, because it's in quotes, because someone has to have the
role of psychoanalyst, it has to be a psychoanalyst, but the role of the psychoanalyst is not to
participate in the brainstorming session, ok, so you all participate in the brainstorming
session and I am the psychoanalyst, so I am the driver of that brainstorming session,
what is my job, when you say something, I ask it to you, and why, and I have to try
to make that stupid questions that make you think, ok, it's like a psychoanalyst, you
go to the psychoanalyst and he's asking you questions, but he knows what questions to
do, ok, this is difficult for us because we don't, but we have to make it forward and
try to make the correct questions, ok, usually stupid questions, and that's it, ok, ok, so
I got these ideas from these two guys, I messed up and I created a workflow for launching
the creativity of my teammates and of this team, ok, so the team, we created the fail
faster team that was meant to create new games and new ideas, and this team was completely
optional, ok, if, for you, for all of you that are interested in entering this fail
faster team, you can enter, if not, don't do it, you can work in anything else, ok,
but I assure that all of them are motivated, ok, but everyone can enter in here and make
the job and it's like, they are about the responsibilities, so, so Monday we had a brainstorming session
after having lunch, ok, after having lunch, we were playing ping-pong for an hour, ok,
for those who are in the team, Monday is for brainstorming, not ping-pong, so these two
things were crying and saying, it's completely opting, so, for those who want to, who want
to eat in a quarter an hour and start the brainstorming session, if they are attending
to the brainstorming session, they are really motivated, ok, because they were, they were
growing, they were relaxing time, ok, so, all of us were meant to bring our ideas in
a document, we had like a, like a questioner and we have to bring in the ideas into there,
so we can, at the start of the brainstorming session, we could start saying about, explaining
our ideas, then we continue discussing those ideas and connecting and creating new things
and we select an idea and we list the action items to work until Friday, ok, so, for example,
we select an idea about a game that is meant to be with magnets and some other things, ok,
so we ask to the designer to create that model and we, I was responsible of structuring the
work to do and trying to split it for all the guys that we are working on, because if
you are starting on Friday, 9am, you want to be as productive as you can, ok, so, all
of ours, we have an action, everyone of ours has an action items to work until Friday to
be prepared, so, when it comes Friday at 9am, all the team work at 8am, from 9am the morning,
we could start working on it, because we had, we had all the dependencies, we had all the
assets don't, because we have worked it when we had some time in the weekdays, all the
assets, ok, all the assets, all the time of that, of that Friday was pure work, pure work
for that, the results were not expected until Monday, this was because if some of the team,
some people in the team was that motivated about this idea and they like it the way they
worked on Friday, but they didn't finish that, they could continue on the weekend, I mean,
and this is not devil, I mean, I am not talking about my employers and I want them to work,
I did it, ok, I was working in some ideas across the weekend, because on Monday I wanted
to have this working and having that game working because it was so nice, so Monday we collect
feedback between each other, we presented the thing that we implemented Friday or the weekend,
and then we repeat the first, the burning time extension, but now with the result of the
first week, with the result of the first iteration as an option to continue, ok, so we can pick
a new idea or continue relating the one that we had.
And basically this is one of the outputs that we made, actually I didn't remember, we have
it in the Apple Store, now it's a game about, it's a very basic racing game, but it's so
funny, because I don't know if it's showing so well, you are all deciding, the first
one is a little stop by friction, and the others have to overtake that, the first one,
and the first can jump at the moment that the first is going faster, and then it's pushed
to the, farther, I mean to the end line, ok, tired, it's so funny, it's free, it's completely
free, ok, ok, so, ok, a little bit of conclusions, ok.
For the first thing about the, recapping all the things about the 20% of Google, I read
this in an article, I like it so much, let's say don't celebrate creativity, allow it,
what does it mean, is that don't try to have this 20% because of being cool, allow creativity
in your inner being as a company, ok, it's like we are not doing this 30% to get results
or no, creativity is creativity, maybe there are no results, maybe, but eventually they
are, also embrace failure in your company, and on yourself as well, ok, failure has to
be easy for you, I mean failure is about expose yourself like we say before, it's about letting
the others see how you fail, don't worry about that, the only thing that you are showing
here is that you are trying, if the others don't want to try, it's their problem, ok,
the only one, an embrace failure also is to, if you are in a company, don't punish failure,
maybe we are not doing this on purpose, maybe you are punishing yourself for being creative
and failing, because if you are failing one time after another, maybe you are thinking
for yourself, I have to do something, I have to exit from this entrepreneur way, I have
to get a job, I have to, ok, this is punishing yourself, or punishing your team about you
are not being that productive this way, this week, ok, this is the problem of the four,
not 4, 5, no, Wednesday whenever you want to apply, 10%, ok, and this is the only way
to keep trying, ok, and you have to keep trying, and the other quote, the final word is the only
way to not fail, it's not to try, ok, so you can ensure not to fail, but you want,
y tú no quieres nada más, ¿vale?
Así que eso es todo, muchas gracias.
Espero que esto no lo hagan mucho tiempo, ¿vale?
¿Y se ha hecho algo o no?
Y ya sabéis, ¡hasta la próxima!