 So, yeah, before we start, we'd like to clarify that some people don't like the Rockstar term, maybe they feel uncomfortable about maybe not the term, but the way in which sometimes it's used or abused. We are going to talk about Rockstars here in a positive way, so for us a Rockstar is the kind of developer that we think it's very, very good and we all look up to and admire and hopefully we'd like to become someday, but at the same time, the term, sometimes the way in which it has been coined makes it look like some kind of high and achievable status up there in the Olympus of software development, and you know, that makes it a bit difficult to feel like, it makes me feel like we are always chasing some kind of impossible thing. Does anyone here know any names of Rockstars in the Drupal community? Yeah? Yeah, if you know any, you know, can you give any names of, yeah, for example, so anyone here in the room feels like he or she is a Rockstar? Well, that's funny because to me, I'm seeing already a few faces that I've known for a long time here in this room, and I know that for me at least they are Rockstars. I consider them very good developers and I consider them to have the things that I'd like to have someday in a way they are some kind of inspiration for me, but at the same time they don't feel like they are Rockstars. So to me, this suggests that there's a gap between what is really a Rockstar and what we consider that is a Rockstar based on what we see on the Internet. So yeah, the general feeling or the general consensus is that a Rockstar is someone who does all these things, right? Someone who knows everything or pretty much everything about the tool that they work with, and of course about some other tools like, you know, the latest new frameworks and anything that comes up contributes a lot to Drupal core or Drupal contributed modules and of course gives great talks at Drupal.com. But according to this scale of values or to this measure, I don't really, I don't feel like I'm a Rockstar, but I don't feel like I can become one. So the thing is, I don't feel like I can do all of this, but I still try to do it. I feel like I must be doing it in order to become a good developer. So the question is, why are we doing this? It doesn't really make a lot of sense. I suppose it, I don't know. For some people it will be because they just want to be famous or they just want recognition for the work that they do in their jobs or out of their jobs. For me personally it will be something that I do because I like to grow and I think it's good for me. So I want to take like a next step in my career. So yeah, a Rockstar developer is not me. It's never me. So something's wrong here. We cannot, we can never achieve that, not be, not me. So I'm going to, I'm going to share with you my personal story as my career. I started my career like 15 years ago as a well, you know, developer of course. And then I was a senior developer. I was even a teacher for a while. And then I was a lead developer, something like that. And I became a manager, project manager first and kind of a CTO in a small company. And I was doing it good, but I didn't feel very well doing that. It wasn't my passion. I wanted to get back to the code, which is what I like, fixing problems and designing great solutions and that kind of stuff. So I asked myself what I have to change my profession in order to grow and be better because that's what I want, right? And so I decided to be a Rockstar. I didn't call it a Rockstar by that time, but I wanted to be a recognizer of the developer in Spain and in the international community. And so because I, the reason is that I, being just a programmer all my life, well, I felt shame with that idea. I couldn't say it loud. I was very young, but I couldn't see myself like older and being just a programmer. Something was wrong in my head with that. So being a Rockstar, being a super good developer was something worthy. And then I set myself this goal. And then I had children and problems, games and well, many things. And I think this message is not only in my head. It's in many heads and it's out there in the society we live today. And well, I want to tell you a story that I met a programmer. I met a brilliant manager. She was a programmer before in a previous agency. In a previous job, we were talking one day and she said something like this. I don't understand people that are still our programmers at the age of 40. And she said that with rejection, disapproval, it's like they were mediocre, not worthy. And that made me think a lot about that because I wasn't close of 40. I am super close of 40 now. So I saw that I was defending myself because I was not going to be just a programmer. I'm going to be a great programmer. That's okay, right? But why should I defend myself? Is it not worthy enough to spend your life doing a profession you love and you do it well? Something's wrong in the culture and the message. That's what I feel. So we spend all this time trying to look for things that we can do in order to achieve our next level. But the thing is that the next level for each person is not the same for everybody, right? I'm a developer now, but maybe in a few years' time I realize that I'm not such a good developer and I'm surrounded by people that are smarter than me and maybe I can become just a team leader because I'm not as efficient as they are as programmers but maybe I'm great at coordinating people that bring a team together that is going to do wonderful things. Or maybe I want to become a project manager. So the thing is, why am I doing all the things that someone is telling me to do or the internet is telling me to do? It doesn't make sense because the story or the next level is different for every person. So there's no point in chasing these things like some kind of creed. So what we wanted to do today or part of it is to just take these myths and maybe analyze them in a way that they can start to be useful for us. We can put them to work for us instead of letting them become death traps that we'll just set ourselves back in our careers. So the first one, it's a simple one. A rockstar knows everything. And this might sound a bit too obvious but it's really some kind of misconception that it's still out there and the thing is that it's not really possible and in order to realize of this we just need to talk to someone that we can see that are a rockstar. And of course we tend to think that these people that know so much they know everything because when we are talking to them about their particular area of expertise of course they know a lot of things and that gets us into the false feeling or the false idea that they just know everything. They are equally good at pretty much everything. But the thing is that it's not really possible. So we just get rid of this and stop using the word experts as if it meant to know absolutely everything on a given field. It just means that you have a deep expertise or a lot of skill in that thing but you don't need to know absolutely everything. The second one is one of my favorites. I've been ranting about this for quite a bit. So another misconception is that we have to be up to date with the latest new and shiny technology. We have to learn react and angular and then another thing comes out now it's Vue.js and there are all these.js frameworks and all these not only.js or front and just even in the back end as well like Laravel selects and a lot of new tools and things that we are supposed to be doing. But the thing is that there's first is not really possible and the great thing is that it's not even necessary. It's perfectly okay to just learn these things when we need to use these things. Of course maybe if I'm a team leader or a CTO I need to be more or less on top of the different things that I have at my disposal but I don't need to know them to a very high level. And the important thing here at least what has worked for me better is just to think about them as tools not as something that will me better or worse. Just to think them as something that they are supposed to solve a problem. So instead of trying to learn new things just because the Internet is telling us maybe we should start to or we should try always to make sure that we are solving a problem when we learn a new tool and that's the important thing. That's what gives or that makes me valuable as a developer. Clients will pay for me just to solve their problems not to create problems for them. So and often the use of new technologies will carry a lot of problems like you have to change your CI processes, you have to train your internal team and maybe not everybody can follow the same pace. You will discover new things along the way. And it's fine but of course we need to evaluate whether that's a cost worth taking on a given time. And the thing is that they get deprecated so quickly. I remember a few years ago my employer gave me like two weeks to work on whatever I wanted and I spent these two weeks learning a lot. I already knew some Node.js so I thought well maybe I should start looking into Angular and these kind of stacks and I spent like two weeks learning a lot of things and I was so excited because I learned so many new things, so many cool things that will allow me to do or to solve problems in a way different than Drupal and then I was so excited about maybe making or doing a little workshop for my team and showing them what I had learned and then two weeks after I had spent that time the Angular team said okay we are going to rebuild it and we are going to change all the API and I was like yeah well those were two weeks, you know, like I just lost most of the time. Of course I learned some new things that were still useful but most of them were deprecated. And the reason why I hate this one so much is because I believe personally it's one of the main source of problems like imposter syndrome or anxiety. The thing is early adopters and evangelists of these new technologies are often so loud on the internet that we fool ourselves thinking that if we are not learning these things and if we are not good at them we will be obsolete in two years. But the reality is just the opposite. In two years if these technologies are still around it will mean that they are actually solving a problem for everybody, a common problem not a problem that is just for Netflix or for Walmart or whatever. And at that point you know they will be more stable, it will be easier to adopt them it will be easier to find documentation. So yeah this is a big one but I think there's some things that we should think about here. And all this leads us to this sensation that a rockstar has so much time spending his or her time in learning new things, have bad projects contributing a lot in not only code but whatever, organizing events, giving presentations and so many things. And we can feel like we don't have time enough to reach that rhythm. It's like impossible, right? Well I don't think we need to spend extra time beyond 40 hours. It's only optional, it should be something like we wanted to do because it is important for us or maybe we have other priorities or hobbies in our life or even other profession. So what if I want to be a musician in my free time? I want to have a coach of a soccer team with the children or so many things that I just work or just work on my relationship with my wife or be there with my children actually playing with them. I've seen myself many times saying no to my daughter, Daddy would you play with me? No, no I have to work and it wasn't actually work. It was me just doing another thing, maybe looking at Twitter some article or something. And I didn't feel what doing that and I've been reflecting on that because I don't want to be my daughter to have problems in the future because her dad wasn't there, right? There are so many things and so many problems in our relationship and in our health that we can have. If we don't spend our time in what is important for us that we should stop this and start saying no to many things and saying yes to the things that are important for us. That can be also contributing and doing something else in your free time but we should take care of it. The message for me is that it's not necessary and what if you want to be a developer just half of the day because maybe you're a father or a mother that want to spend your afternoon and evening with your children or maybe you have another profession or you're helping in your parents' shop or whatever or you're starting a new project, totally different or you have a blog or whatever, so many things you can do in your life. So there are other professions where one can be respectable and very good just doing his or her job in five hours a day or four so we can. Well, also I want to say that it's very healthy to do different things out of your laptop. It's going to help your creativity. Sometimes I'm stuck with something and I go for a walk or do something completely different and when I come back two hours later, it's like magic. Oh, I see the solution now. Well, there are many studies about this. If you use your mind a lot in your computer and you do something very different like music, something creative, it's going to help you to be better at your profession too. And one more thing I want to say. I've seen some jobs that require open source contributions in order to hire people. I don't think this is a good idea because of all this. You don't know what's important. You can value that. It's something valuable. But requiring that, no, everyone has the luxury of spending time of this. No one has the luxury of being in a company that understands open source and allows you to contribute in the working time. So we should take care about these things and value more things and not setting more barriers. So this one has beaten myself as well in the past. So I'd like to spend some time out of work reading stuff or working on site projects. But for me, it goes with period. Sometimes I spend a few months working on those site projects but maybe then I'm not feeling like it for another two months and that's fine whenever I feel like doing it. But in the past, I've been forcing myself sometimes to just do something out of the working hours, which is stupid. I will feel guilty if I didn't do it because I was like, someone is going to get ahead of you and you have to be working, you have to get better. And that's really stupid. If I'm doing my work and I'm doing it well, I don't have to. If I like doing it, then that's perfect but I don't have to force myself. Another myth is that Rockstar writes perfect code. And to me, this is a dangerous thought. Personally, I might look really stupid but I've been beaten by this one as well. In the past, I remember having passed, I mean I was quite junior but I remember having passed some code from someone where there was a part that didn't quite click, didn't quite make sense to me. I thought that it will fail but then I thought, yeah, maybe it's me not understanding this properly and I said, yeah, okay, let's merge the code. And it was yes because the person that had written that code is so brilliant and is such a great developer and makes so few mistakes that I thought it will be fine. And let's say that the following day, the real-time information on the project that we were working on was not so real-time. So, yeah, this is a dangerous thing because every time we think that someone writes perfect code just because who he is or who she is, we are missing a chance of challenging some piece of code and learning something because even if it's right, then we'll get answered and we might be learning something new. So that's good. A consequence of thinking this is that we are afraid sometimes of showing code that isn't complete. But this is, again, something quite stupid. I mean, it might not happen to everyone, but it happens to some people. It's fine to show code that isn't complete even if it's rubbish, even if it's all a huge function that is not completed, but maybe we can get some good feedback from someone like, you know, you are fetching the data in this wrong way and it will become a performance problem with the amount of traffic that we will have or have you thought about the structure in this in some other way? But if we think about Drupal and why it has come so far is because people started contributing things that were not perfect at all and we just got to the issue queues and started to contribute to the best of our capabilities. And about the feedback, we should be trying to be nice when we give feedback to colleagues as well. That's one of the things that can make us really good developers when we do things, just praising for the good things rather than jumping straight on the bad things or on the things that need fixing. The problem is that some of us identify in some way with the code that we write or with what we produce. And so when someone wants to give us some constructive code, constructive criticism, even if it's negative, we may feel attacked ourselves because we identify ourselves with the thing that we produce, so, yeah. Let's try to give good feedback to people and when people give us bad feedback, we don't have to see them as enemies or someone wanting to annoy ourselves. We just need to... Maybe they're just doing it the wrong way, but that's still fine. Let's be smart and let's cherry-peak the feedback. Let's remember the feedback that is useful to us and that allows us to remember things. So, in this topic of code perfection and code completion, I'd like to talk about something quite related, which is monkeys. So I read this story... I don't know if it's still a thing or not, but I read this story in a book called The Passionate Programmer by Chad Fowler, and he tells this story about monkeys in South India and how big of a problem they were to people because they were always stealing food from people's hands, right? From street markets from everywhere. Any chance they had, they would steal the food. And South India... The people from India came with this idea of digging holes on the ground and throw cooked rice on them. And the idea was that the monkeys would put their hands and grab the rice, but the holes were done in a way that they were bigger on the inside. So when the monkeys grabbed the rice, it would become a fist and it would then come out. And of course, you know, that's a silly thing. Normally you would say, okay, I can't get the rice, but the monkeys instead will fight against the ground just to get the rice out instead of just dropping it there and leaving. So the book goes with this story to explain the concept of value rigidity, which is what happens when we give so much value to something that we are no longer able to objectively question that thing anymore. And to me, this is one of the most harmful things that we can do to ourselves, not only as developers, but in our careers in general, whatever we are. It's a very human thing. It's not even just related just to code. So some examples of value rigidity is when we insist that only one technology... We are discussing with our team what we should do, and we insist that only one technology is going to solve something, or that some other technology is really awful, even though we don't really have that much experience with it, or just because in the past it didn't work out for us. Or when we push back a code, some piece of code that is fine, it has no bugs, it's working, maybe just because it doesn't follow the design pattern that we had in our mind, or that we thought that it should follow. So we will be able to be much better developers if we just identify when we are falling into these kind of traps, because the thing with this is that it's very easy to fall into them, but it's very easy to avoid them as well. We just need to identify that we are falling into them and just thinking about things analytically. And even when we do this, and we take all the measures to do our job in the best possible way, sometimes we'll fail, and that's perfectly fine. We just embrace that as a way to learn and that we keep trying. Yeah. Many people are afraid to make mistakes and show their code because of that. I heard a story about... We don't know if it's true, but they say that Thomas Edison, well, he made a lot of experiments with balds and a lot of thousands of prototypes that didn't work, and they asked him about that and there's a quote which is, I haven't failed. I've just found 10,000 ways that won't work. And this is very relevant to me because science constantly teaches that we need to embrace the path of failure as something positive, something that we can learn from. There is a lot of value in mistakes and this is the way to success. Another thing I want to talk about is I feel like in our society we are educated to reward results above all, but not so much the way to get there if it's a clean way, if it's a dirty way, it doesn't matter many times, and of course not errors. Sometimes we punish them or we reject them. So, again, we should reflect on that and try to educate ourselves in another way. Like we do with our children, like in this slide before with that pet, our children can make two steps and then fall, but we are not regretting that. We are saying, okay, we are celebrating that small win, right? Because he made two steps, that's awesome. And we don't care if he has fallen. But I don't know, sometimes when we are older we stop not doing that, and instead of celebrating the small steps we are focusing more on the mistakes and punishing ourselves many times and others for that. So, we should try to educate ourselves in a different way, I think. And we can learn from test driving development, too, where we start with a fail. You write a test, and there is no code, so there is a failure. And it's okay. And now we are going to make it work, right? And also the bagging teaches that there is a lot of value in errors because when you have to chase an error, the bagging, you learn a lot from the code, from the workflow, many things. So, there is a lot of value there. Don't forget that. Sorry. And there is another myth, I don't memorize everything. Yeah, I haven't memorized that. I have to speak now. So, as you can see. So, I have a very lazy memory. Actually, I think the only song I know the lyrics from, it's Happy Birthday. Well, I know, too, because I know the Spanish version, too, so that's great. But, really, it's not that I'm bad at memorizing things. It's just that I'm very lazy, and I think my brain refuses to learn because I can just look up in 15 seconds. But I felt shame and I felt insecure many times for not having certain things memorized, like what does every Drupal hook or the parameters or some functions, common functions, like PHP, SDR, blah, blah, or whatever. So, I have to look at it every time, and it's okay for me. But I do kind of think that Rockset doesn't need that. They know everything, every little detail of everything, and, of course, that's not true again. But I thought that many times, and when I was going to present my first technical talk in the Drupal camp, I was super scared because of the questions, because what if they find out that I'm an imposter here, and there's so many things that I don't know, and I have to look and do that. I can't do that if I am asking a question. So, I was super scared about this. So, the good thing is not it's not necessary. Life is not an exam. We came for an education again. We learned to memorize everything for the exams, but that is no longer needed these days with the Internet. Thank God. Something that has worked for me for a long time today is to just learn the fundamentals of something. It doesn't make any sense to just memorize absolutely everything, because I will forget about most things, at least the technical, the exact details of how to do something in a given framework. If I'm working with different frameworks, it's very easy to, you know, if I stop doing Drupal for a month and start working on a symphony project, when I come to Drupal, maybe I start to mix things up, and I will forget everything. So, something that works for me is to just learn the fundamentals instead. It's much more useful for me to learn and to know how to identify, for example, the situations in which I have to use a background process or a task queue than knowing how to implement this in Drupal. I know the Drupal API, and just remembering a few things, and just do it in a few seconds. Learning the fundamentals, it's what will make it easier for us to start learning new technologies if we want to do so, because then we identify in every different stack when we need to do things in one way or the other, and again, the details can be looked up in seconds. At least for me, it works better to not become very obsessed with, you know, having to remember everything. And also, what works better is to just come up with my own set of tricks and tools that make me more efficient, like life templates in PHP, Storm, or CodeSneepads, or even sometimes I've built my own code generators just because they will save me, like, an hour or two of work. So that's one of the things that, for example, has worked better for me, and when I talk about resources, I talk as well about people. Sometimes the best resource is to ask as one of our colleagues. And sometimes, many times, the best resource is people. It's asking other people, but that involves vulnerability because you have to admit whatever I know. And here comes something that I really consider a rockstar ability, just something like this quote. My biggest professional development was getting comfortable admitting what I don't know. I love that quote. It's not only admitting what I don't know, it's getting comfortable doing that. That's a rockstar thing for me. A real rockstar thing. That's something I can do. It's not easy, but now I feel like I'm in a point that I can say that. I was so scary. I started as a freelance, and I wanted to have my personal brand in the Drupal world, in the technical world, and I just couldn't ask things out there in IRC or Twitter or other public spaces because I was worried about what people are going to think when they find my stupid comments in the Internet three years from now. Well, we are learning step by step. To be comfortable being vulnerable requires a filter, because you can expect that other people can be rude or cannot understand that. I can say, you don't know that. But we should try not to make that for ourselves. It's like, this is something that is a person problem. It's the other person comment. It's the other person attitude. It's not us. We should try to set this filter. And normally you're not going to find that in the answer. Normally people are going to value that you're being vulnerable, that you're being authentic and real, and you trust yourself to admit what you don't know and what you need to achieve just by asking. So that's a good thing, and people normally see good things about that. Somehow this is not in our head. This is not a common thought. This is why things like imposter syndrome are so common in our culture today. I guess everyone knows about the imposter syndrome. Imposter syndrome is being unable to knowledge your strengths and value what you're good at and focus on the opposite. Focus on what you lack, what you don't have, what you don't know. And the two main symptoms is refusing to take challenges, job, projects, and also burn out to try to achieve those super high standards you keep in your head. Because as I told you, I felt that way in the Drupal community because I was known very early by many Spanish folks, but I felt like, okay, people know me, so people think I'm a good developer, but I don't know anything because I was just always focusing on what I don't know, what I don't know, what I don't know. And also it happens to me well, I didn't even thought that I could be there, so it was my dream, but okay, they hired me, I have tricked them somehow. And when I was in the first retreat I heard that they were talking about imposter syndrome and how that imposter syndrome thing was something that everyone feels when it's done at Lullabot. And that was a huge relief because I learned that they weren't expecting expecting from me any higher standards, any super rockstar myths that I had in my head. They just were expecting me to be me and to be motivated and give the value I can give just being me because they just hired me as I am. That was a huge relief. So we can change some messages in a way that we can create a future that where imposter syndrome is not so common. One of the tips or one of the advices that some psychologists give to people to overcome this, I mean this wasn't for me, it was for a friend of mine of course, is to just have a notebook on your desk next to your laptop and whenever someone says something good to you or gives you praise for something, just write it down. Write it down there and just leave it. Whenever the thing kicks in and you start to feel like you are not worthy for whatever reason, just open the notebook and just read the notes and just one minute and just get on with your life. So where does this come from? We hear a lot of messages out there of scarcity that we are not enough, that we have not time enough, money enough, we are not healthy enough, safe enough many things. But I find it especially dangerous and we don't talk much about this, that message that we are not extraordinary enough. Somehow in this world having an ordinary life and having a meaningless life has become synonymous, has become the same thing in our minds. So we try to do a lot of things in the quest for the extraordinary, like trying to find our purpose of setting new goals to make achievements, to get higher, to step out of our comfort zone. Many, many messages that can make sense in a context but all together are creating a pressure to look for the extraordinary because in the end we need to be happy or something like that. But what if we are missing what is really important to us? The ordinary moments I think the ordinary moments in our lives, like playing with our children, having relationships, doing things that has a lot of value for us and are aligned with our values is where we can find the most joy. There is an exercise which is thinking about, it's a scary exercise but in coaching when you think about what happens if you are going to pass away one year from now or two years from now or six months, that helps you to connect what is important for you. And people that have experience that are close to death, they come back doing something different like saying that they love someone or they don't come back to develop normally, so that could help. Maybe we should just try to live an authentic life rather than chasing the extraordinary and I love this authenticity definition from Brenner Brown, this authenticity is the daily practice of letting go of who we think we are supposed to be and embracing who we are. So to be authentic needs daily practice. I need to self, myself, accept myself as I am with a smile, I can't expect to feel worthy looking at the outside and I don't need to do anything to feel proud. Finally, here is my last reflection. I think if you love yourself just as you are without expectations, without conditions, and you can trust yourself offer something special and unique because every one of us are unique and special like our experience, like our creativity and I think we can give much more value and you will probably find the most joy and peace. So let's think twice about chasing all these things that we consider that we should be doing in order to become better in our lives and in our careers. We can offer or we can be valuable in so many other ways that it doesn't really make sense to follow blindly all these things. Of course it's fine to go after them if we want to be speakers and we want to give presentations and that's great. But it's fine to be vulnerable, it's fine to be to keep your feet on the ground, you don't have to be learning new things all the time. In reality the problems are with the tools, the problems are where your clients are and you can offer so much value to your clients and to your customers just by being able to be on Earth just solving the problems there not jumping from one technology to another all the time. The important thing here is really that you do whatever you want. If you want to go and do all the things that we generally agree that are common traits in drugstore developers, that's fine but just do it because you like doing them not because someone is imposing all these things on you. So I like Monty Python as well. The real important thing is that we do these things because we want not because someone is telling us that that's what you should be doing. So just set your career and your life in the direction that you want it to be. In my case that will be something that it will be even better for me because if I'm just happy doing the things the way I want I'll be even better doing the other things that people are supposed to have in order to be drugstore developers. I won't have any pressure. So yeah, that will be my message. And I wanted to put this I think it's a liberating message and take away you don't have to do anything in this life you don't have to do anything just embrace who you are. And I know let's embody your honest trends and creativity and of course break the myths of the rocks to the developer and believe in yourself. Thank you. So yeah great that you have questions already. Well in case some of you are shy I have written some questions for you to inspire to invite you to talk. Thank you. I love a lot. I I have been I think most of us has been through just that and you managed to put some words on it I feel really deeply thankful for you doing that. Is that better? I have done some study about the subject as well because I was exploring from the imposter syndrome a few years back and I think your slides are missing an important piece that helped me through that which is someone once told me that empathy is the easiest way to success. You rarely get hired or you rarely get accepted into empathy or anywhere in the world without some sort of empathy. You rarely get accepted on wisdom alone. So empathy precedes wisdom. I absolutely agree and I cannot talk about many many things that I would like to talk more great and more things that I have to learn we have this slide with resources the first one is a book that I love which is the gift of imperfection that I recommend you all it's from Bernie Brown and she studies happy people more in the joy meaning more in the happy happy but there are kind of three keys to joy and one of them is empathy so I'm glad you say that there's a lot more to say than to learn. Very good. Well I'm going to keep this. Hi. First thank you to include the women inside the talk I got it. It's not common. I would like to share with you a history that happened to me last year that was my first Drupalcom. I didn't know anyone I didn't know any rock stars and I was free to talk about everything and I was in dinner and someone asked like what do you what you would like to change about Drupalcom was not to me was in general and I started to say what I thought that we should change and then someone told me like do you know with whom you are talking about and really I didn't know but I mean it's not because it's me I think that we have to open the doors to who has something new to say about it's also that we as a community we put this person as a rock star and then nobody is able to talk with them and to say what we really think about and I want it also to share with you my point of view about my professional life I like to change technologies I didn't know that was something common for some person and take me time to accept myself what I wanted I don't want to be a specialist in something I want to share technologies because it's what I really enjoy and I want to be a develop but it takes me a lot of time to accept that thanks thank you for sharing your story I think as a community we have a lot of of things like tunnel vision so sometimes we feel like if an opinion or feedback comes from outside of the community it's somehow less valid but you are right we have to listen to everybody really we have to be open with anything every opinion has value and every opinion counts and I think it's fine as well if you want to be you will read a lot that you should be an expert in one thing instead of spreading yourself too much but I think it's perfectly okay if you'll find more joy learning different technologies and you can offer a lot of value with that as well I'm glad that you shared your story and I will encourage you to just keep doing or taking your career that way and I think that also has another kind of value if you know different technologies you can get the best thing of everything and then improve the other technology absolutely agree with that thank you I want to say both things none of those two things are related to Drupal and those two things are uplifting first who in this room has ever felt the imposter syndrome raise your hands Okay, news here Richard Feynman Nobel Prize in Physics suffered from imposter syndrome so it's no one is free from that and that's how he solved that he just received an insane offer from some university I think it was Princeton but I'm not sure he felt the imposter syndrome for quite some time and then suddenly stopped by the university what the hell and I'm feeling though they know me I'm scientific that means they have my papers they have read my papers they know my work they know me, they know my CB if they want to pay me for that it's probably okay to stop the second thing is about being 40 years old who in this room is over 40 years old okay, not alone thanks Scott the thing is that what's the future for people in technology over the certain age good news that there are companies that pay for these expertise pay well it's to be half accordingly pay a lot, respect your work it happens and you can check yourself for example people who know the video game Batman, Arkham Knight you don't have to know that just go look on YouTube for the credits video in the credits video there's a pattern that repeats again and again it's a long list of people and you see city design senior designers all senior designers then two designers and then two juniors same week coders senior developer, senior developer developer, junior developer they always repeat the same pattern some interns here and there the book of the work for people with experience and then they put young blood into the project slowly, not everything at a time then interns they do exactly the other way around and what happens when you do that is games like Arkham Knight this incredible piece of work but there are companies out there that understand that you can do something that Arkham Knight with interns those companies do exist thanks a lot that's what I wanted to say thank you first of all, thank you for the session it's been really inspiring and well, I want to admit publicly that I suffer from exposure syndrome the more I know the less I think I know and yeah it's something that most of us suffer I am not shy to admit it but I want to ask you about some advices what common things can we do to reduce or to try to reduce this imposter syndrome thank you there's a great talk the last one which is enlightening there are so many tips to overcome imposter syndrome one of them is very important one of the reasons is you don't know what you know and your values your strength getting track actually like in paper getting track of every good feedback of everything you're doing well it's going to help you a lot to see that and see okay I'm not so bad so that's one of my favorites from that talk this motivation of my presentation is I want you to think that we all can change slightly the culture we are in and create an environment where imposter syndrome is less common and there are a lot of things that we can do to show us more vulnerable to welcome better vulnerability for instance Dan Abramov co-author of Redux from React he started a hashtag in twitter asking very basic questions about things that he was willing to admit that he doesn't know and the hashtag is the junior there for life and it was a symbolic thing of course not a junior right but it was telling outside it's okay to ask basic questions and many people follow that and in general we live in a culture where we are many times we're showing our best smile, our best face our best vacation picture in facebook or twitter or whatever and we're not so we should embrace our shitty work you should show it we should be more vulnerable in our message out there and show everything because otherwise we're creating the opposite and I think that the society is made that impossible smile and happiness standard that we are not like that so yeah all things be creative I wanted to give my point of view about that topic what I try to do is to be clear with myself and to be clear with the people I mean I know what I know or I think that I know what I know I'm trying to say I don't know that part doesn't mean that I don't want to learn it I want to learn everything but at the moment I don't know something and it doesn't matter unless I would like to propose you to think about if you can make a session or if you can make a question because for some of us like me it's not something that is going to come to me like oh you are great I force myself to do it but I think that is something good for me and also good for the community because we learn from each other we're running out of time one more question actually there was one slide about kind of the time management and I just wanted to ask you what do you think those people who are like putting there another four or six even more hours after the mandatory eight I would say those are not kind of workaholic instead of just being superstar or rock star or whatever pop star because sometimes I feel there are colleagues of mine or even there were a few who never stopped like we had to leave the office six for instance then they brought home the work in the next day they provided something that was not the best but still we felt they put their lot of resources so workaholism versus being rock star well I think well there was yesterday a very good talk it was Marina I don't know it was about being a leader something like that or a manager and they made us we did an exercise a mindfulness exercise very basic aligning our values and our actions in our life and many people can see that actually our actions are not aligned with our values and that's mind changing so the important thing is if you're doing what is important for you if people are doing what is important for each person that's what's matter not doing things because I should because that's what you're supposed to be and do things because I must it's because that's something that comes from you it's really important for you that's the only thing I have to say there's one thing about this my take is that that might happen sometimes sometimes I've had to work some extra time as well there's a tight deadline and sometimes it happens and of course that attitude when there's a problem and your colleagues are there and they are working their asses off to get the thing done for me that's one of the things that makes someone a rockstar as well being there when you need it but that is not a requirement for someone to be a rockstar it doesn't happen once in very specific cases and then that's okay but if it happens often it will lead to burnout and it's really not healthy and if it happens often what that suggests to me that the problem is someone up there in another layer is not the problem with developers and the developers should not be having to spend all that extra time working on that so I think we ran a little bit out of time so thanks everyone for attending and if you don't mind taking a minute to rate us at some point in the day that would be great thank you