Mind of a developer

(bright music) - The only thing that we know for sure is that everything's going to change, so the way to overcome with that is just to embrace the change. I think that's how you need to work in this field, right? Because, if not, you are going to be frustrated all the time. I mean, you'll learn Angular and then after one month, oh, there is a new version. It's completely different. So you don't need to get frustrated. I think it's part of the path. So I think learning to embrace the change is how you solve the problem and how you face most of the challenges in this field. - Coming from an engineering background, I tend to approach things from sort of a emotionless perspective or a really logical perspective when it comes to analyzing things and reasoning and making decisions. It's easy for some people to get bogged down and make an instant emotional response to things. Sometimes I'll consciously ask myself if my emotions are affecting the way that I'm approaching a problem or how I should be dealing with it. And if my emotions are a big factor, then I put that problem to the side and I address it later when I'm in a different state of mind. Just being able to sit down and pragmatically analyze the different components of a problem quite often leads you to a more swift solution. - What are the really important things in a responsive design framework? What makes a good responsive design framework? How do I communicate that in a way that people will understand my code and want to use it in their own work? I'm very passionate about making sure that critical thinking is understood. That people are understanding why they choose technology A over technology B. And that they're able to articulate that. - So, for me, I had an engineering background. I went to school for engineering. And ended up, over time, in tech. And so, I take a lot of my engineering background into problem solving. When you go to school for engineering, they teach you problem solving. The reality is, you've got some templates, you've got some ways of thinking about problems that you can then apply a systematic, methodological approach to solving problems. And so I take that into testing, as well. There's a lot of problems that testers need to deal with. Taking that problem solving approach when you run stuck on something is a very powerful skill to have. - So the thing is that whenever you see a problem, the first thing that you have to do is get to know the problem. There are many developers who I've seen in my technology work experience who sometimes don't even know what the problem is. And they just want to fix the defect. That doesn't work. You have to know the semantics of the problem. You have to see the bigger picture. How is that problem affecting the entire bigger picture that you have in the organization? You need to see how it affects at all points in that flow and the strategy is, to solve a problem, you take one thing at a time. It could be a very complicated issue to solve and you may not be able to do everything at the same time. You have to take one step at a time. You need a strategy. You need planned steps. You need to plan it out, that this is how I'm gonna solve it. And just take one step at a time. And, you know, it is very easy to say not to, don't try to panic, but you know, that's the key. A cool mind, a calm mind, is often going to help you solve problems in a way better manner than just getting yourself panicked and then messing it all up. (bright music)