1 00:00:00,000 --> 00:00:04,000 Coding well with others or being a team player is at the heart of 2 00:00:04,000 --> 00:00:07,600 everything. We do as a unless you're coding 3 00:00:07,600 --> 00:00:11,400 yourself for a piece of software that only you're going to use 4 00:00:11,700 --> 00:00:14,200 your not a solo developer right now. 5 00:00:14,200 --> 00:00:17,100 We share. Cody, get how we share it with 6 00:00:17,100 --> 00:00:20,500 everyone even if nobody's following even if nobody's 7 00:00:20,500 --> 00:00:23,700 interested, right off the bat on something, we're doing Google's 8 00:00:23,700 --> 00:00:27,000 their index and everything. I mean our coats on it, find out 9 00:00:27,000 --> 00:00:29,500 eventually. Even if we don't want to we may 10 00:00:29,500 --> 00:00:32,400 get fever. Feedback week, my get people 11 00:00:32,400 --> 00:00:36,100 fucking a code and using it. So we need to understand what it 12 00:00:36,100 --> 00:00:38,100 means to be part of that Community. 13 00:00:38,100 --> 00:00:41,200 Even if you don't want to and code in a way that helps, 14 00:00:41,200 --> 00:00:44,500 everyone, it's not just about ironic or any works for me, and 15 00:00:44,500 --> 00:00:50,300 that's it. Hey everyone. 16 00:00:50,900 --> 00:00:55,800 My name is Henry Surya Barragan. And you're listening to the 17 00:00:55,800 --> 00:00:59,300 tekhelet Juno, the show will be bringing you the greatest 18 00:00:59,300 --> 00:01:03,100 technical leaders practitioners and thought leaders in the 19 00:01:03,100 --> 00:01:08,000 industry to discuss about their Journey ideas and practices that 20 00:01:08,000 --> 00:01:11,000 we all can learn and apply to build a highly performing 21 00:01:11,000 --> 00:01:14,800 technical team and to make an impact in your personal work. 22 00:01:15,500 --> 00:01:24,000 So let's dive into our Journal. Hello again, to all my 23 00:01:24,000 --> 00:01:26,100 listeners. Hope that you are doing great 24 00:01:26,100 --> 00:01:27,800 today. Welcome back to another new 25 00:01:27,800 --> 00:01:30,100 episode of the Tecla Journal podcast. 26 00:01:30,500 --> 00:01:32,600 As always. Thank you for tuning in and 27 00:01:32,600 --> 00:01:36,000 listening to this episode. If you're new to this podcast, 28 00:01:36,100 --> 00:01:38,700 don't forget to subscribe and follow technology, you know, on 29 00:01:38,700 --> 00:01:42,700 your podcast app and social media on LinkedIn, Twitter and 30 00:01:42,700 --> 00:01:45,200 Instagram. And if you love the podcast, 31 00:01:45,300 --> 00:01:48,400 support the show by subscribing as a patron at package, you 32 00:01:48,400 --> 00:01:52,600 know, dot f / Patron. And support me in my journey to 33 00:01:52,600 --> 00:01:54,600 produce great episode. Every week. 34 00:01:55,600 --> 00:02:00,000 My guest for today's episode is Fernando, dog, Leo, Fernando is 35 00:02:00,000 --> 00:02:03,500 the author of skills of a software developer and he has 36 00:02:03,500 --> 00:02:07,200 over 18 years of experience in the software industry from web 37 00:02:07,200 --> 00:02:09,699 development, to Big Data, and so on. 38 00:02:10,000 --> 00:02:13,000 And by the way, throughout the conversation, I mentioned the 39 00:02:13,000 --> 00:02:17,400 book title as code well with others, however, since then the 40 00:02:17,400 --> 00:02:20,600 book title has been updated to skills of a software developer. 41 00:02:20,700 --> 00:02:22,800 /. So hopefully you all do not get 42 00:02:22,800 --> 00:02:26,800 confused about the two different titles in this episode. 43 00:02:26,800 --> 00:02:30,000 Fernando shared some insights from his book on how we can all 44 00:02:30,000 --> 00:02:31,800 be a successful software developer. 45 00:02:32,500 --> 00:02:35,900 He highlighted that software development is mostly a team 46 00:02:35,900 --> 00:02:39,700 effort and he shared a few tips on how we can be a great team 47 00:02:39,700 --> 00:02:43,600 player and work well with others, including the importance 48 00:02:43,600 --> 00:02:48,100 of writing readable code to Auntie patterns in particular 49 00:02:48,100 --> 00:02:50,600 that Fernando advisors to avoid are over it. 50 00:02:50,800 --> 00:02:54,400 Nearing an early optimization. So make sure that you listen to 51 00:02:54,400 --> 00:02:58,300 his reasoning so that we do not fall into the Trap of both in 52 00:02:58,300 --> 00:03:01,800 our work. Next Fernando also shared some 53 00:03:01,800 --> 00:03:05,100 practical tips on technical interviews and what we should 54 00:03:05,100 --> 00:03:08,500 avoid writing in our resume, towards the end. 55 00:03:08,500 --> 00:03:11,700 Fernando gave his tips to aspiring authors, who want to 56 00:03:11,700 --> 00:03:14,900 write a technical book. He himself has written five, 57 00:03:14,900 --> 00:03:18,000 technical books, including the recent Manning book and I asked 58 00:03:18,000 --> 00:03:20,500 him what advice he has for some of us. 59 00:03:20,700 --> 00:03:22,600 Who would also like to write a book. 60 00:03:23,000 --> 00:03:26,200 He gave really great advisors, and cleared some common 61 00:03:26,200 --> 00:03:29,700 misconceptions and mental blocks that may stop a lot of aspiring 62 00:03:29,700 --> 00:03:32,500 authors from writing, and Publishing their books. 63 00:03:33,400 --> 00:03:37,000 I enjoyed my conversation with Fernando listening to his tips 64 00:03:37,000 --> 00:03:39,000 for becoming a successful software developer. 65 00:03:39,300 --> 00:03:42,200 And in particular, his insightful advice on how to 66 00:03:42,200 --> 00:03:44,800 become a book author. And if you also like this 67 00:03:44,800 --> 00:03:48,200 episode, leave a rating and review on your podcast app or 68 00:03:48,200 --> 00:03:50,500 share some comments on the social media on. 69 00:03:50,800 --> 00:03:54,100 Do you enjoy from this episode? Those reviews and comments are 70 00:03:54,100 --> 00:03:57,300 one of the best ways to spread this podcast to reach more 71 00:03:57,300 --> 00:03:59,600 listeners. And it is my hope to have more 72 00:03:59,600 --> 00:04:03,000 people benefiting from all the episodes in this podcast. 73 00:04:03,300 --> 00:04:07,000 So let's get our episode started right after our sponsor message. 74 00:04:07,300 --> 00:04:10,300 Are you looking for a new cool swag tekhelet Journal. 75 00:04:10,300 --> 00:04:13,500 Now, offers you some swags that you can purchase online. 76 00:04:13,900 --> 00:04:17,800 These wax are printed on demand based on your preference and 77 00:04:17,800 --> 00:04:20,300 will be delivered safely to you all over the world. 78 00:04:20,300 --> 00:04:23,600 Where Shipping is available. Check out all the cool swag is 79 00:04:23,608 --> 00:04:25,500 available by visiting technology. 80 00:04:25,500 --> 00:04:28,900 Know that death / shop and don't forget to break yourself. 81 00:04:29,000 --> 00:04:31,100 Once you receive any of those tracks. 82 00:04:33,900 --> 00:04:36,400 Hey everyone, welcome back to another new episode of the 83 00:04:36,400 --> 00:04:39,700 technology on our podcast today. I have with me, Our Guest named 84 00:04:39,700 --> 00:04:42,800 Fernando do glue. He's actually start writing his 85 00:04:42,800 --> 00:04:44,700 book called coat, well, with others. 86 00:04:44,700 --> 00:04:47,400 With a subtitle, be an effective team player. 87 00:04:47,600 --> 00:04:50,500 I think today, we are going to cover tips and tricks for all. 88 00:04:50,700 --> 00:04:54,400 The lapis out there in order to be aware of how you should 89 00:04:54,400 --> 00:04:57,900 behave, or, how should you treat yourself differently when you 90 00:04:57,900 --> 00:05:00,200 work with others? Because probably will also 91 00:05:00,200 --> 00:05:03,200 discuss about the difference between a solo developer, which 92 00:05:03,200 --> 00:05:06,200 probably some of you are doing and also team player developers 93 00:05:06,400 --> 00:05:08,900 when you work in a company on the team or even open source 94 00:05:08,900 --> 00:05:11,900 projects, how much different it could be as a programmer. 95 00:05:12,200 --> 00:05:15,800 So Fernando also wrote a number of books and nickel books things 96 00:05:15,800 --> 00:05:18,100 like really good node.js and all that. 97 00:05:18,200 --> 00:05:22,100 So we will probably also get some tips from Him on how we can 98 00:05:22,100 --> 00:05:25,200 start writing, technical books. So, Fernando looking forward to 99 00:05:25,200 --> 00:05:26,800 have this conversation with you today. 100 00:05:27,000 --> 00:05:29,200 Welcome to the technician. All right. 101 00:05:29,200 --> 00:05:30,500 Thank you. Hi, everyone. 102 00:05:30,600 --> 00:05:33,100 Very excited, be here. I can't wait to get started 103 00:05:33,100 --> 00:05:34,100 honestly. Thank you. 104 00:05:34,600 --> 00:05:37,200 So Fernando, baby for people who don't know you yet. 105 00:05:37,200 --> 00:05:38,500 Maybe you can introduce yourself. 106 00:05:38,500 --> 00:05:41,000 Maybe sharing about highlights or turning points in your 107 00:05:41,000 --> 00:05:42,600 career. All right. 108 00:05:42,600 --> 00:05:44,200 Well, the exam from a little earlier. 109 00:05:44,400 --> 00:05:47,100 I'm originally from your way. Although I'm right now, living 110 00:05:47,100 --> 00:05:50,000 in Spain, in Madrid. I have been part of the 111 00:05:50,000 --> 00:05:52,500 industry. Or around 18, 19 years. 112 00:05:52,600 --> 00:05:56,600 I started working as most developers to, as a web 113 00:05:56,600 --> 00:05:59,000 developer. I started with JavaScript and 114 00:05:59,000 --> 00:06:04,200 HTML CSS eventually move to back in a few years later, around 115 00:06:04,200 --> 00:06:07,600 five or six years later. I moved into a big day toward 116 00:06:07,900 --> 00:06:12,300 and started also Mari. And my experience with web 117 00:06:12,300 --> 00:06:15,200 development, couple with the architecting of Big Data 118 00:06:15,200 --> 00:06:18,800 platforms and how to scale at application past the single 119 00:06:18,800 --> 00:06:21,400 computer essentially fellow We Big Data. 120 00:06:21,500 --> 00:06:23,100 Hello. We picked it architectures and 121 00:06:23,100 --> 00:06:26,400 bring our marriage, you know, deletion you practice for the 122 00:06:26,400 --> 00:06:27,100 company? You work for. 123 00:06:27,800 --> 00:06:30,600 So it seems to me that your experience is varied. 124 00:06:30,800 --> 00:06:33,300 So you started from like a front-end developers doing web 125 00:06:33,300 --> 00:06:36,700 development, go to the back end and then now be cater. 126 00:06:36,800 --> 00:06:39,700 It seems for some people. Actually, they might not even 127 00:06:39,700 --> 00:06:42,200 fantasize doing all these three different things at the same 128 00:06:42,200 --> 00:06:44,400 time. So maybe can you give us some 129 00:06:44,400 --> 00:06:45,900 lessons learned throughout your journey? 130 00:06:46,200 --> 00:06:49,600 How can someone actually achieve something like you juggling and 131 00:06:49,600 --> 00:06:51,300 hoping between multiple? Domains. 132 00:06:52,000 --> 00:06:55,600 Well, definitely part of why I've been able to do it because 133 00:06:55,600 --> 00:06:58,900 I've been at it for a while. I mean, 18 years, not sure time. 134 00:06:59,100 --> 00:07:01,300 So it takes time to go from one place to the other. 135 00:07:01,300 --> 00:07:03,700 That's for sure. But I think the key here is at 136 00:07:03,700 --> 00:07:05,500 least understand that everything is related. 137 00:07:05,500 --> 00:07:08,200 I mean, when you're working on the front end of web application 138 00:07:08,200 --> 00:07:12,400 nowadays, it's not like you're just building a static website 139 00:07:12,400 --> 00:07:15,000 for a small company up to people. 140 00:07:15,000 --> 00:07:18,100 You should at least aim for building, something that will be 141 00:07:18,100 --> 00:07:20,900 popular. I would be looked at by. - 142 00:07:20,900 --> 00:07:24,900 people will have high traffic that translates to a back-end, 143 00:07:24,900 --> 00:07:28,300 that is also capable of dealing with that amount of traffic and 144 00:07:28,300 --> 00:07:29,700 that translates to a whole architecture. 145 00:07:29,700 --> 00:07:32,700 So it's all related and the moment you start realizing that 146 00:07:32,700 --> 00:07:35,000 everything is the same. What I'm trying to say is 147 00:07:35,000 --> 00:07:40,300 whether you're coding in react, or working PHP or riding a bike 148 00:07:40,300 --> 00:07:42,900 line on by Spark, It's just cold. 149 00:07:43,100 --> 00:07:44,800 No more. Your style realized that the 150 00:07:44,800 --> 00:07:49,100 logic may change the language may change, but there are four 151 00:07:49,100 --> 00:07:52,100 five main paradigm. That you're going to be actually 152 00:07:52,100 --> 00:07:54,600 having to learn and applying and that's all you had to care 153 00:07:54,600 --> 00:07:57,100 about. The rest is just coding. 154 00:07:57,200 --> 00:07:59,800 Anyone can pick up coding. I mean, it's a matter of time. 155 00:08:00,000 --> 00:08:03,400 So I think the main problem with people going through that 156 00:08:03,400 --> 00:08:07,400 journey and trying to go from one area to The Other Extreme is 157 00:08:07,400 --> 00:08:10,900 that people put themselves in boxes and say, well, I'm on 158 00:08:10,900 --> 00:08:13,400 reactivated. I'm great at react. 159 00:08:13,400 --> 00:08:15,800 Don't talk to me about by spark because I don't know anything 160 00:08:15,800 --> 00:08:19,800 about by Stack, but honestly, you gotta pick up some mechanics 161 00:08:19,800 --> 00:08:21,700 of helps. Mark works, but that's 162 00:08:21,700 --> 00:08:23,700 learnable. The rest is just code. 163 00:08:23,800 --> 00:08:25,200 The Mummy that clicks in your head. 164 00:08:25,400 --> 00:08:29,200 Then there's no place for you that you can be honestly you 165 00:08:29,200 --> 00:08:32,400 want to go from coding react to coding robots. 166 00:08:32,500 --> 00:08:34,700 That's also possible. It's just cold. 167 00:08:34,900 --> 00:08:36,799 That's the main thing here. Sometimes. 168 00:08:36,799 --> 00:08:39,100 People don't get that. At least people get it started, 169 00:08:39,100 --> 00:08:41,299 and that's something. I also try to cover him a book. 170 00:08:41,500 --> 00:08:44,600 It's just cold. So, you also mention a one key 171 00:08:44,600 --> 00:08:47,200 thing that I took away from your explanation, just now, which is 172 00:08:47,200 --> 00:08:49,500 about Paradigm and putting yourself in boxes. 173 00:08:49,700 --> 00:08:52,300 So, I think the Since here is that we should not putting 174 00:08:52,300 --> 00:08:54,500 ourselves in a certain Paradigm saying that, okay. 175 00:08:54,500 --> 00:08:57,200 We are just a web developer. For example, I think 176 00:08:57,200 --> 00:09:00,300 understanding the fundamentals and Basics, which is that coding 177 00:09:00,300 --> 00:09:02,900 or you said, maybe some kind of algorithms on how a computer 178 00:09:02,900 --> 00:09:04,300 works. Things like that is also 179 00:09:04,300 --> 00:09:07,100 instruction, right? So, which brings us to the book 180 00:09:07,100 --> 00:09:09,300 itself? Why do you write about this 181 00:09:09,300 --> 00:09:12,000 topic codes? Well, with others, do you find 182 00:09:12,000 --> 00:09:15,500 problems in the industry or in your career that people do not 183 00:09:15,500 --> 00:09:17,500 code? Well with others, the book 184 00:09:17,500 --> 00:09:20,900 story, as a miracle on medium, actually it had I'd like to 185 00:09:20,908 --> 00:09:24,400 think he was like eight or nine Lessons Learned through my 18 186 00:09:24,400 --> 00:09:26,000 years of experience. There. 187 00:09:26,000 --> 00:09:29,300 I cover everything obviously. It was a single article covering 188 00:09:29,300 --> 00:09:32,000 the other thing so they were just highlights of a lot of 189 00:09:32,000 --> 00:09:35,000 things are now in the book, but it covered things. 190 00:09:35,000 --> 00:09:38,700 Like from usual, bad coding practices to problems with 191 00:09:38,700 --> 00:09:41,400 dealing with teams and remote teams, things like that. 192 00:09:41,600 --> 00:09:45,400 The article got a lot of big nice reception essentially, a 193 00:09:45,400 --> 00:09:48,500 lot of experienced coders saying, I agree 100% with you. 194 00:09:48,800 --> 00:09:52,900 You hit every nail When mining approached me and told me you 195 00:09:52,900 --> 00:09:53,900 were ready. Radical. 196 00:09:53,900 --> 00:09:57,800 And we like to expand on it which turned out into, as you 197 00:09:57,808 --> 00:10:01,200 see the blueprint of app developers career based on 198 00:10:01,200 --> 00:10:03,500 lessons. I've learned through those 18 199 00:10:03,500 --> 00:10:07,000 years. This is kind of our road trip to 200 00:10:07,000 --> 00:10:11,200 my Lisa mistakes. If you will, I made a lot of 201 00:10:11,200 --> 00:10:15,500 them through 18 years. So I'm just trying to show one 202 00:10:15,500 --> 00:10:19,000 that everyone makes them if you're making mistakes is part 203 00:10:19,000 --> 00:10:22,800 of the journey and to Larry set better way of doing some things 204 00:10:22,800 --> 00:10:25,800 and a better way to look at some situations coding. 205 00:10:25,800 --> 00:10:29,700 Well with others or being a team player is kind of a be heart of 206 00:10:29,700 --> 00:10:33,500 everything we do as a when you say you said solo vertebras 207 00:10:33,500 --> 00:10:36,200 right? Unless you're coding yourself 208 00:10:36,200 --> 00:10:39,700 for a piece of software that only you're going to use your 209 00:10:39,700 --> 00:10:44,000 not a solo developer right now. We share call you get how we 210 00:10:44,000 --> 00:10:47,600 share it with everyone even if nobody's following even if 211 00:10:47,600 --> 00:10:50,900 nobody's interested, right of the bat on, something will Doing 212 00:10:51,100 --> 00:10:52,700 Google's their induction everything. 213 00:10:52,700 --> 00:10:55,800 I mean our code is going to get find out eventually even if we 214 00:10:55,800 --> 00:11:00,200 don't want to, we may get feedback week might get people 215 00:11:00,300 --> 00:11:04,000 for king or code and using it. So we need to understand what it 216 00:11:04,000 --> 00:11:05,900 means to be part of that Community. 217 00:11:05,900 --> 00:11:09,000 Even if you don't want to and code in a way that helps, 218 00:11:09,000 --> 00:11:12,200 everyone it's not just about I run my code and it works for me 219 00:11:12,200 --> 00:11:14,700 and that's it. Interesting perspectives in the 220 00:11:14,708 --> 00:11:17,300 sense that even though you think you are so low developers, write 221 00:11:17,300 --> 00:11:20,100 like you're just building EOC project, but the moment that you 222 00:11:20,100 --> 00:11:23,300 share, RIT either on GitHub or maybe just publish a blog post 223 00:11:23,300 --> 00:11:26,400 that you think others will not read things can get picked up 224 00:11:26,400 --> 00:11:30,000 automatically by changing and maybe some random opportunities 225 00:11:30,000 --> 00:11:31,800 that people just randomly, see your code. 226 00:11:31,800 --> 00:11:34,800 And see, that actually how well your code is written, but maybe 227 00:11:34,800 --> 00:11:37,100 in the first place is. Alright, I wrote the first 228 00:11:37,100 --> 00:11:40,300 chapter of the book and you kind of like started interestingly by 229 00:11:40,300 --> 00:11:42,900 saying that all of us can be a successful developers. 230 00:11:43,100 --> 00:11:46,300 There are certain things that we don't actually need to be so 231 00:11:46,300 --> 00:11:48,900 concerned about. So things like bachelor degree 232 00:11:48,900 --> 00:11:50,400 or understanding about software development. 233 00:11:50,600 --> 00:11:53,700 My life cycle, so can you maybe share the Dismal your thought 234 00:11:53,700 --> 00:11:55,800 process around this? Absolutely. 235 00:11:56,000 --> 00:11:59,300 So I try to start attacking some of the classic misconceptions 236 00:11:59,300 --> 00:12:01,400 that people have around developers and what they need to 237 00:12:01,408 --> 00:12:03,700 become one. Like I said before anyone can do 238 00:12:03,700 --> 00:12:04,700 it. It's just a matter of 239 00:12:04,700 --> 00:12:07,600 understanding how God works from the user perspective and what 240 00:12:07,600 --> 00:12:10,900 commands, you need to work. You don't need to go to college 241 00:12:11,000 --> 00:12:14,500 to understand that you don't need like a paid certification 242 00:12:14,500 --> 00:12:17,500 to understand that you don't need to understand how the whole 243 00:12:17,500 --> 00:12:20,400 software development life cycle goes, what you have to learn. 244 00:12:20,500 --> 00:12:24,100 To code, just write words that make sense so that they can be 245 00:12:24,100 --> 00:12:26,500 executed. You can pick it up by reader 246 00:12:26,500 --> 00:12:28,500 tutorial or by watching a YouTube video. 247 00:12:28,500 --> 00:12:30,800 That's all you need. What I'm trying to say in 248 00:12:30,800 --> 00:12:34,900 chapter 1 is that instead of focusing on those skills that 249 00:12:34,900 --> 00:12:37,400 you have to learn to become a successful developer. 250 00:12:37,600 --> 00:12:40,700 You should realize that if you want to be a successful 251 00:12:40,700 --> 00:12:43,500 developer, you have to understand that you're going to 252 00:12:43,500 --> 00:12:45,300 be learning through the entire process. 253 00:12:45,400 --> 00:12:47,500 You have to understand that you're going to be having 254 00:12:47,500 --> 00:12:50,400 problems to solve and we determinant of 2. 255 00:12:50,600 --> 00:12:52,900 We'll go home one day with a problem. 256 00:12:52,900 --> 00:12:55,400 You couldn't solve, and come back tomorrow and start again or 257 00:12:55,400 --> 00:12:58,200 try again. It's not a set of hard skills 258 00:12:58,200 --> 00:13:00,600 that you have to learn in order to become a successful 259 00:13:00,600 --> 00:13:03,200 developer. The hard skills come with time, 260 00:13:03,300 --> 00:13:05,600 Claudine comes with time. You can really do a 261 00:13:05,600 --> 00:13:07,300 certification and say, whoa. Now. 262 00:13:07,300 --> 00:13:10,700 I'm a believer that part of learning the colder in the 263 00:13:10,700 --> 00:13:14,400 paradigms learning, how syntax works that takes time. 264 00:13:14,700 --> 00:13:16,800 The key traits that you have to have. 265 00:13:16,800 --> 00:13:20,800 Our orders are soft skills that if you don't think, About them, 266 00:13:20,800 --> 00:13:24,100 they're not available. If you don't take the process of 267 00:13:24,100 --> 00:13:27,300 going through the development of an application as a learning 268 00:13:27,300 --> 00:13:31,300 process, personally, you have to worry about the right thing to 269 00:13:31,300 --> 00:13:35,900 eventually make it as a sexually available and none of them are 270 00:13:35,900 --> 00:13:37,400 technical. That's my point there. 271 00:13:37,400 --> 00:13:40,100 If you want to pick up development right now, it's 272 00:13:40,100 --> 00:13:41,600 fine. Just go, watch a YouTube video. 273 00:13:41,600 --> 00:13:43,800 Write your hello work. You're a developer. 274 00:13:43,800 --> 00:13:45,400 You did it. That's it. 275 00:13:45,400 --> 00:13:48,100 The rest of the hard skills is expanding like that. 276 00:13:48,100 --> 00:13:52,000 You showed yourself that you're able to To learn something new. 277 00:13:52,300 --> 00:13:54,600 Are you going to be doing that throughout your entire career? 278 00:13:54,800 --> 00:13:58,200 You learned that your able to make a switch from whatever you 279 00:13:58,200 --> 00:14:01,200 were doing into this. And they have to be flexible 280 00:14:01,200 --> 00:14:04,100 through your entire career, unless you want to just focus on 281 00:14:04,100 --> 00:14:07,600 one branch of development. And then when that Branch dies, 282 00:14:07,600 --> 00:14:10,100 you're out of a career. So, that's the things that try 283 00:14:10,100 --> 00:14:12,900 to explain in chapter 1. Don't get me wrong. 284 00:14:12,900 --> 00:14:15,100 I'm not saying that formal education. 285 00:14:15,100 --> 00:14:17,400 I don't need it. I taught myself how to code when 286 00:14:17,400 --> 00:14:20,300 I was 14. I did the whole high school net. 287 00:14:20,500 --> 00:14:24,000 College thing and I dropped out of college because I had a job 288 00:14:24,000 --> 00:14:27,200 already and I try to pursue that but eventually realized I 289 00:14:27,200 --> 00:14:30,600 actually needed that formal education related in my ears and 290 00:14:30,600 --> 00:14:33,300 I went back to college and finish a technical degree. 291 00:14:33,500 --> 00:14:35,500 Why did that? Because definitely think there's 292 00:14:35,500 --> 00:14:37,900 a value to formal education. And there is a value to a 293 00:14:37,908 --> 00:14:40,800 certification that you can have an understanding that some of 294 00:14:40,800 --> 00:14:44,700 the Venom life cycle completely, but you don't need them to get 295 00:14:44,700 --> 00:14:47,200 started, and that's kind of what chapter 1 covers. 296 00:14:47,800 --> 00:14:51,700 So then in your case after you have Anshu, all this experience 297 00:14:51,700 --> 00:14:53,400 learning by mistakes. Like what humans? 298 00:14:53,400 --> 00:14:54,500 Share? What do you think are? 299 00:14:54,500 --> 00:14:57,700 Some of the biggest tips for somebody will pursue think about 300 00:14:57,700 --> 00:15:01,700 whenever they want to be able to work well in a team set up. 301 00:15:02,300 --> 00:15:04,900 So the first thing they need to understand that they're not 302 00:15:04,900 --> 00:15:07,600 alone, whatever they're doing and they'll see, she said, 303 00:15:07,600 --> 00:15:10,200 they're taking around their cold water colors. 304 00:15:10,500 --> 00:15:13,200 That's also the main point around the topic. 305 00:15:13,500 --> 00:15:17,600 If you're a perfectionist, I you wanna get your code, perfect, 306 00:15:17,600 --> 00:15:19,200 which is something that doesn't exist. 307 00:15:19,200 --> 00:15:22,000 Really, you're afraid. In timeline of your project if 308 00:15:22,000 --> 00:15:24,000 there is a dependency for no task. 309 00:15:24,000 --> 00:15:26,000 For instance. I do their Duty priests waiting 310 00:15:26,000 --> 00:15:28,200 for because you haven't finished yet. 311 00:15:28,400 --> 00:15:31,600 You're a faith in their work. If you're not careful enough and 312 00:15:31,600 --> 00:15:35,600 you're not writing unit tests for instance, or paying the 313 00:15:35,600 --> 00:15:37,600 right attention to, you need to send doing it. 314 00:15:37,600 --> 00:15:41,100 The proper way you might end up, delivering something that is not 315 00:15:41,100 --> 00:15:43,800 stable enough and others will work on top of that. 316 00:15:44,000 --> 00:15:47,200 So everything's connected in the sense that if you don't do your 317 00:15:47,200 --> 00:15:50,700 part, well, then everything else will fall apart even If you 318 00:15:50,700 --> 00:15:53,100 think yeah, you're a small part of it because you're just 319 00:15:53,100 --> 00:15:55,000 getting started. Junior developer. 320 00:15:55,000 --> 00:15:56,600 Who doesn't know better. Whatever. 321 00:15:56,600 --> 00:15:58,500 You may think that your situation is. 322 00:15:58,500 --> 00:16:01,000 Your work is directly affecting other stats. 323 00:16:01,100 --> 00:16:04,900 Also, the main point there are multiple topics that cover here 324 00:16:04,900 --> 00:16:07,100 regarding trying to over engineer a solution. 325 00:16:07,100 --> 00:16:09,500 Right? I mean who of us haven't really 326 00:16:09,500 --> 00:16:12,200 fall for that trap before and fell in love with a solution 327 00:16:12,200 --> 00:16:15,500 that is super complete and covers every angle of it. 328 00:16:15,500 --> 00:16:18,300 And when you actually need it practically you could have 329 00:16:18,300 --> 00:16:22,000 solved that problem in two days. You Actually took two weeks, but 330 00:16:22,000 --> 00:16:24,700 you cover everything that wasn't needed, you affected. 331 00:16:24,700 --> 00:16:27,700 The timeline of the project you delivered late and everyone 332 00:16:27,700 --> 00:16:29,300 depending on that was late as well. 333 00:16:29,600 --> 00:16:32,700 That's the kind of thing. I try to explain here and show 334 00:16:32,700 --> 00:16:36,500 how it affects others decision. So on the last topic where you 335 00:16:36,500 --> 00:16:39,400 mentioned over-engineering, I think most of the developers 336 00:16:39,400 --> 00:16:41,800 love to do this and one way or the other right, either 337 00:16:41,800 --> 00:16:44,700 consciously or unconsciously. We always like to chase 338 00:16:44,700 --> 00:16:47,600 something that we think is a Perfection, you mentioned that 339 00:16:47,600 --> 00:16:50,300 there are ways around overcoming this problem. 340 00:16:50,800 --> 00:16:54,100 So what are the ways or tips for people not to fall into the Trap 341 00:16:54,100 --> 00:16:57,000 of over-engineering? You have to be objective. 342 00:16:57,000 --> 00:16:58,800 I mean, they may problem you have. 343 00:16:58,800 --> 00:17:02,200 And the more reason why it we fall for that trap is because we 344 00:17:02,200 --> 00:17:05,300 fall in love with our own Solutions, we forget about the 345 00:17:05,300 --> 00:17:07,599 rest and we think about just the solution. 346 00:17:07,599 --> 00:17:11,300 I'll have to build and then within wall, this is good, but I 347 00:17:11,300 --> 00:17:13,300 can do better and I could do better. 348 00:17:13,500 --> 00:17:15,599 This is great. I have the perfect solution. 349 00:17:15,800 --> 00:17:18,599 I'll just implement it. I'll take as much time as you 350 00:17:18,599 --> 00:17:20,300 need. You never thought about well. 351 00:17:20,400 --> 00:17:22,599 Well, whatever. The others want to do, yours 352 00:17:22,599 --> 00:17:25,099 actually need that submitting. You have to look at the 353 00:17:25,099 --> 00:17:27,000 solution. You're trying to implement from 354 00:17:27,000 --> 00:17:29,300 the big picture. I like to say that sometimes 355 00:17:29,300 --> 00:17:32,800 developers don't raise the head above the laptop and look out. 356 00:17:32,800 --> 00:17:34,800 Were just so focused on what we're doing. 357 00:17:34,800 --> 00:17:37,200 The co-writing that we forget to look around us. 358 00:17:37,500 --> 00:17:40,500 We might have bunch of developers or teammates waiting 359 00:17:40,500 --> 00:17:43,300 for us to finish. So, I think that the main tip 360 00:17:43,300 --> 00:17:47,200 here is, if you're writing, if you do something you create 361 00:17:47,200 --> 00:17:50,300 something, you let it stay for a day and then come back. 362 00:17:50,500 --> 00:17:52,300 It, you might come by the other day. 363 00:17:52,300 --> 00:17:54,900 I hate it. If you draw if you paint thats 364 00:17:54,900 --> 00:17:58,500 also a common issue, you think you did something amazing and 365 00:17:58,500 --> 00:18:01,300 you come back the other day and just try way because it sucks 366 00:18:01,400 --> 00:18:04,300 the same is with other ideas. You will need to look at it 367 00:18:04,300 --> 00:18:07,800 objectively and even if you have to walk away and get back to it 368 00:18:07,800 --> 00:18:11,500 for a day, you might see that you're not actually thinking 369 00:18:11,500 --> 00:18:14,100 about the big picture. You just think about your 370 00:18:14,100 --> 00:18:17,200 particular solution, your particular problem and you're 371 00:18:17,200 --> 00:18:20,200 not caring about anyone else. I think that's the biggest tip. 372 00:18:20,400 --> 00:18:22,600 I have for overcoming over Vision. 373 00:18:22,600 --> 00:18:25,300 Earring is more like avoiding a Visionary at all. 374 00:18:25,600 --> 00:18:28,000 Try to look at it from another perspective. 375 00:18:28,000 --> 00:18:30,800 Not just yours. So when you mention about 376 00:18:30,800 --> 00:18:34,100 objectivity, right, maybe, can you refer to some examples? 377 00:18:34,100 --> 00:18:35,700 Is it like referring to requirements? 378 00:18:35,700 --> 00:18:37,400 Is it referring to the deadlines? 379 00:18:37,400 --> 00:18:40,500 Or is it referring to some other factors that you think can 380 00:18:40,500 --> 00:18:43,100 provide more objective Baseline for developers? 381 00:18:43,500 --> 00:18:45,300 Absolutely. I mean, it's all done and 382 00:18:45,300 --> 00:18:47,300 everything else except your problem. 383 00:18:47,400 --> 00:18:50,300 The timeline is going to be affected if you can deliver it. 384 00:18:50,400 --> 00:18:54,100 And you usually have a small window time preset for you to 385 00:18:54,100 --> 00:18:56,700 finish that solution. If you think that you have a 386 00:18:56,700 --> 00:18:59,400 better alternative, but it'll take longer. 387 00:18:59,400 --> 00:19:01,800 Then that's definitely going to affect everyone. 388 00:19:02,000 --> 00:19:05,400 Especially if you don't even consider how that's going to 389 00:19:05,400 --> 00:19:07,900 affect everyone else and even speak about it. 390 00:19:07,900 --> 00:19:10,900 You're going to have a big effect on the rest of the 391 00:19:10,900 --> 00:19:14,000 Prussian, the research team, the requirements Gathering as well. 392 00:19:14,200 --> 00:19:17,500 If you're shopping from solution to solution, bigger and bigger. 393 00:19:17,600 --> 00:19:21,400 If that turns out to be over engineer you Might even be 394 00:19:21,400 --> 00:19:25,600 making assumptions about future requirements to protect example, 395 00:19:25,600 --> 00:19:29,000 you have to feel that cataloging page or the login service for 396 00:19:29,000 --> 00:19:31,200 your app. You have a lot of alternatives 397 00:19:31,200 --> 00:19:34,500 are a little variations from simple user password valuation, 398 00:19:34,500 --> 00:19:38,700 against a database, all the way through single sign-on, multiple 399 00:19:38,700 --> 00:19:41,800 entities, and everything. So, where do you put that, stop? 400 00:19:41,800 --> 00:19:43,900 Where you say? Well, this is complex enough. 401 00:19:44,100 --> 00:19:46,900 This is big enough for the application and it's going to 402 00:19:46,900 --> 00:19:49,300 work as it is right now. If you have a set of 403 00:19:49,300 --> 00:19:52,000 requirements that State that are don't State. 404 00:19:52,000 --> 00:19:54,800 The fact that for instance, you need single sign-on, then why 405 00:19:54,800 --> 00:19:57,900 are you implementing that are you assume that's going to be 406 00:19:57,900 --> 00:19:59,500 needed? Because in the future you want 407 00:19:59,500 --> 00:20:01,600 to be building other applications that will benefit 408 00:20:01,600 --> 00:20:03,100 from that. That's fine. 409 00:20:03,200 --> 00:20:05,800 But if you're making that assumption you need to validate 410 00:20:05,800 --> 00:20:08,600 that assumption because that might be the case that you say. 411 00:20:08,600 --> 00:20:10,700 Well, are we gonna need this? Because in the future, we're 412 00:20:10,700 --> 00:20:14,000 going to build that your manager, your Technique, where 413 00:20:14,100 --> 00:20:15,700 my come by say. Well actually, you know, what? 414 00:20:15,700 --> 00:20:17,500 That's a great idea. Let's do that. 415 00:20:17,500 --> 00:20:20,200 And let's adjust the timeline because we needed. 416 00:20:20,300 --> 00:20:22,200 Showtime, that's another operation here. 417 00:20:22,400 --> 00:20:25,200 But if you don't do that, you don't validate that you just 418 00:20:25,200 --> 00:20:27,300 assume. So you're over engineer a 419 00:20:27,308 --> 00:20:28,600 solution. I should have been a lot 420 00:20:28,600 --> 00:20:31,400 simpler. That's a point and this is also 421 00:20:31,400 --> 00:20:34,200 kind of like related with another tip of your switches to 422 00:20:34,200 --> 00:20:37,600 focus on working code first. So when you start looking on 423 00:20:37,600 --> 00:20:40,400 solving a problem, you should probably aim to make it work 424 00:20:40,400 --> 00:20:42,500 first. Maybe you can elaborate more on 425 00:20:42,500 --> 00:20:44,300 this point. Absolutely. 426 00:20:44,400 --> 00:20:47,600 That also speaks to not only over each day and Barrel saw 427 00:20:47,600 --> 00:20:49,800 Ellie optimization. That's an old trap that we like 428 00:20:49,800 --> 00:20:51,500 to fall. Getting everything. 429 00:20:51,500 --> 00:20:55,200 Perfect and working the best possible way that he can work 430 00:20:55,200 --> 00:20:58,300 from the get-go. That's the worst way to build 431 00:20:58,300 --> 00:21:02,600 code because to optimize code to make it perfect. 432 00:21:02,600 --> 00:21:04,500 You need to have measured it first. 433 00:21:04,500 --> 00:21:07,800 You need to know how it performs if there's any bottleneck where 434 00:21:07,800 --> 00:21:11,000 it is and then optimize. So if you're going the other way 435 00:21:11,000 --> 00:21:14,500 around, if you put in the car in front the horses, then you're 436 00:21:14,500 --> 00:21:17,900 assuming that you're going to have problems, you're assuming 437 00:21:17,900 --> 00:21:20,200 where the problems going to be and you're assuming house. 438 00:21:20,300 --> 00:21:23,300 Oh, the solution will work. You're guessing essentially and 439 00:21:23,300 --> 00:21:27,000 you're not fixing anything. So, the way I like to approach 440 00:21:27,000 --> 00:21:30,600 coding and problem solving in general is get a bunch of code 441 00:21:30,600 --> 00:21:33,900 that together solve the problem. I don't care if it looks good. 442 00:21:33,900 --> 00:21:36,300 If it works great. Does it solve the problem? 443 00:21:36,400 --> 00:21:39,000 The main question you have to ask if it does so the product 444 00:21:39,000 --> 00:21:41,900 then start making it prettier. Clean it up into multiple 445 00:21:41,900 --> 00:21:45,800 modules or whatever. And then once that's ready, add 446 00:21:45,800 --> 00:21:49,200 the code is readable by others on the code is useful and 447 00:21:49,200 --> 00:21:51,400 reusable event, then. Start measuring it. 448 00:21:51,600 --> 00:21:53,100 That's it. Perform correctly. 449 00:21:53,400 --> 00:21:56,500 Does he have any bottlenecks? And then start optimizing it 450 00:21:56,700 --> 00:21:59,300 when you're optimizing it, understand that there is going 451 00:21:59,300 --> 00:22:02,200 to be a point where you have to say that's enough because the 452 00:22:02,200 --> 00:22:04,300 perfect gold doesn't really exist. 453 00:22:04,300 --> 00:22:07,100 There's always going to be something that throws you whole 454 00:22:07,100 --> 00:22:08,700 set of assumptions. The moment. 455 00:22:08,700 --> 00:22:12,200 You don't see that when you stop seeing that you're stuck in an 456 00:22:12,200 --> 00:22:15,000 infinite Loop, always optimism. That doesn't really need to be 457 00:22:15,000 --> 00:22:18,000 optimized. So when you say optimizing 458 00:22:18,000 --> 00:22:20,900 getting a measurement and all that does it mean that you 459 00:22:20,900 --> 00:22:24,500 always need to put the code itself to the front of users or 460 00:22:24,500 --> 00:22:27,400 getting deployed somewhere for people to validate or actually, 461 00:22:27,400 --> 00:22:29,000 you go through like some kind of performance. 462 00:22:29,000 --> 00:22:32,000 There's any kind of experience you have here on how to people 463 00:22:32,000 --> 00:22:35,400 measure their code first before they optimize, that's very 464 00:22:35,400 --> 00:22:37,200 valued. I mean, I can't really give an 465 00:22:37,200 --> 00:22:40,100 example of one way that will work for everyone because you 466 00:22:40,100 --> 00:22:42,600 have environments were running an algorithm. 467 00:22:42,600 --> 00:22:45,700 That can run your laptop. It's big enough of a lab test or 468 00:22:45,700 --> 00:22:48,700 good enough of a test to understand if it's performing or 469 00:22:48,700 --> 00:22:53,400 not, but if you're Keen on microcontrollers, or if you're 470 00:22:53,500 --> 00:22:57,100 building something that is super time-sensitive that you probably 471 00:22:57,100 --> 00:23:00,300 needed to run on the environment that it's going to be deployed 472 00:23:00,300 --> 00:23:03,600 to be 100% sure that he knows how to deal with all the 473 00:23:03,600 --> 00:23:06,200 intricacies of the environment. If you're building something 474 00:23:06,200 --> 00:23:09,300 that needs to be distributed. Then you need to understand how 475 00:23:09,300 --> 00:23:12,200 it runs for a set of notes or any should Master, but 476 00:23:12,200 --> 00:23:15,200 figuration and then build on top of that and try to make it 477 00:23:15,200 --> 00:23:17,000 bigger or smaller and go from there. 478 00:23:17,100 --> 00:23:20,600 So the point is that you need to understand that one you Have to 479 00:23:20,600 --> 00:23:23,200 make sure it you have to understand if performance is an 480 00:23:23,200 --> 00:23:26,200 important topic for you. Then you need to understand that 481 00:23:26,200 --> 00:23:28,100 you're going to measure that performance. 482 00:23:28,300 --> 00:23:32,300 You need to understand what kpis or what key indicators are there 483 00:23:32,300 --> 00:23:36,100 for you to look at because measuring is not just about 484 00:23:36,100 --> 00:23:39,300 having a start counter at the beginning of your code and an 485 00:23:39,300 --> 00:23:41,600 encounter. At the end of that whatever 486 00:23:41,600 --> 00:23:45,100 function you're trying to test and see how many seconds I took 487 00:23:45,100 --> 00:23:46,300 were having these in microseconds. 488 00:23:46,600 --> 00:23:49,600 You need to understand. If performance, for you means 489 00:23:49,600 --> 00:23:51,800 speed. Or if performance, for you means 490 00:23:51,800 --> 00:23:56,300 function calls or memory used or how many threads you were able 491 00:23:56,300 --> 00:23:58,800 to start. It's so quiet. 492 00:23:58,800 --> 00:24:01,300 It's Unique to your context again. 493 00:24:01,300 --> 00:24:04,900 No, share example here, but that is what you need to understand. 494 00:24:04,900 --> 00:24:07,600 You need to resonate when you're going to be basically, to what 495 00:24:07,600 --> 00:24:10,900 apis, you have to measure. And then three try to find a way 496 00:24:10,900 --> 00:24:14,200 to measure those kpis without affecting their performance, so 497 00:24:14,200 --> 00:24:17,500 much that the mere effort of measuring affects the 498 00:24:17,500 --> 00:24:19,200 performance. That's another big thing. 499 00:24:19,300 --> 00:24:23,100 But if you Managed to do that. Then you're able to actually 500 00:24:23,100 --> 00:24:25,800 understand how your application works, how your code works. 501 00:24:26,000 --> 00:24:29,000 You can build from there, understand if your kpis are 502 00:24:29,000 --> 00:24:32,100 within a reasonable thresholds than great. 503 00:24:32,100 --> 00:24:35,000 You made it, otherwise start tweaking based on that. 504 00:24:35,000 --> 00:24:38,300 But if you have that, you have half the bottom one because 505 00:24:38,300 --> 00:24:41,300 you're ready. You're basing everything you do 506 00:24:41,300 --> 00:24:44,600 from now on or reality. You're not assuming anything and 507 00:24:44,600 --> 00:24:47,800 that's major and you have mentioned a couple of times 508 00:24:47,800 --> 00:24:50,100 about readable code code that is maintained. 509 00:24:50,700 --> 00:24:53,700 I think this is also one big part of being a good team player 510 00:24:53,700 --> 00:24:56,200 for any developers out. There is that your produce code 511 00:24:56,200 --> 00:24:58,200 must be understandable by others. 512 00:24:58,400 --> 00:25:01,500 Maybe you can give us some stories or experience throughout 513 00:25:01,500 --> 00:25:03,900 your journey. Why is it so important for 514 00:25:03,900 --> 00:25:07,100 people to make their coat understandable by others? 515 00:25:07,800 --> 00:25:11,200 I always, like to say that code needs to run a computer, but be 516 00:25:11,200 --> 00:25:14,400 read by humans and sometimes we forget about the second part 517 00:25:14,600 --> 00:25:16,700 that goes back to my initial statement. 518 00:25:16,700 --> 00:25:19,900 You're never working alone. Even if you think you are that 519 00:25:19,900 --> 00:25:21,500 close. Code needs to be understandable 520 00:25:21,500 --> 00:25:25,300 by you in the future or tomorrow or within the next 10 minutes. 521 00:25:25,500 --> 00:25:28,800 When you write code, if you don't write it correctly, you 522 00:25:28,800 --> 00:25:31,800 might not add enough context to whatever you're doing. 523 00:25:32,100 --> 00:25:35,200 We're not perfect machines. We forget we have terrible 524 00:25:35,200 --> 00:25:37,200 memories. So when we get back to our 525 00:25:37,200 --> 00:25:39,500 algorithm that we wrote, and it's complex enough. 526 00:25:39,700 --> 00:25:42,600 We might not even understand our own code, and that happens to 527 00:25:42,600 --> 00:25:44,500 everyone that has happened to me. 528 00:25:44,500 --> 00:25:48,900 I mean, X, if we can't even rely on our memory to understand what 529 00:25:48,900 --> 00:25:52,900 we did, how can we We expect others who have not gone through 530 00:25:52,900 --> 00:25:55,600 the ideation process for bag with them to, actually 531 00:25:55,600 --> 00:25:58,000 understand it by just reading the code. 532 00:25:58,200 --> 00:26:01,200 So, readable code means a lot of things readable code. 533 00:26:01,200 --> 00:26:05,100 Can mean avoiding one liners because they might look cool or 534 00:26:05,100 --> 00:26:08,700 my solve a problem. It's just a single line, but my 535 00:26:08,700 --> 00:26:12,600 need to be mentally past when you're measuring, how readable 536 00:26:12,600 --> 00:26:16,000 code is, you have to take into consideration, the amount of 537 00:26:16,000 --> 00:26:19,100 effort that a person has to go through to understand the gold. 538 00:26:19,300 --> 00:26:22,400 And that means most Most of the times were mentally parsing the 539 00:26:22,400 --> 00:26:25,600 code and mentally executing it to understand how their good 540 00:26:25,600 --> 00:26:28,900 works, or how this single line is parsing or transforming the 541 00:26:28,900 --> 00:26:30,800 information. We need to actually make it 542 00:26:30,800 --> 00:26:34,400 usable on the next line. So if we have to go through that 543 00:26:34,400 --> 00:26:36,700 amount of effort just to understand it, then the code is 544 00:26:36,700 --> 00:26:39,100 not readable. It might work perfectly on the 545 00:26:39,108 --> 00:26:43,100 machine, but you need to also try to optimize the amount of 546 00:26:43,100 --> 00:26:45,500 time you have to spend looking at a block of code. 547 00:26:45,500 --> 00:26:48,600 If you want to modify in the future, it's not that hard 548 00:26:48,600 --> 00:26:51,800 honestly, I mean, well read Comment, might solve all that 549 00:26:51,800 --> 00:26:53,900 problem. So things like comments in the 550 00:26:53,900 --> 00:26:58,000 code understanding that the code has to have a structure so that 551 00:26:58,000 --> 00:27:01,000 it's easier to read, if you're not using something like, python 552 00:27:01,200 --> 00:27:04,800 indentation is crucial here. If we don't pay attention to 553 00:27:04,800 --> 00:27:07,700 that, then reading code becomes a lot harder. 554 00:27:08,100 --> 00:27:11,000 If you're already part of a team, there are probably coding 555 00:27:11,000 --> 00:27:13,000 standards that the whole team is following. 556 00:27:13,100 --> 00:27:15,700 If you don't follow those coding standards, you're not writing 557 00:27:15,700 --> 00:27:19,200 readable code because the reason for the coding standards is they 558 00:27:19,200 --> 00:27:21,200 have nothing to do. Ooh, with the computer, the 559 00:27:21,208 --> 00:27:23,800 computer will always translate, whatever you write to a piece of 560 00:27:23,800 --> 00:27:27,200 code that it understands. The coding standards are for you 561 00:27:27,200 --> 00:27:30,300 and other developers. If you write following the same 562 00:27:30,300 --> 00:27:33,800 naming conventions, the same syntax, the same structure in 563 00:27:33,800 --> 00:27:35,700 the code. It will become easier to jump 564 00:27:35,700 --> 00:27:38,600 from one file that you wrote to another file written by someone 565 00:27:38,600 --> 00:27:40,400 else. It'll be like, looking at two 566 00:27:40,400 --> 00:27:44,300 pages from the same author, you know how that author writes. 567 00:27:44,500 --> 00:27:48,000 I, you know, where to find the key bits of information already 568 00:27:48,000 --> 00:27:49,800 because it's follow the same standards. 569 00:27:50,300 --> 00:27:54,200 That's the way you have to also think about humans when writing 570 00:27:54,200 --> 00:27:56,000 code and make it readable for them. 571 00:27:56,600 --> 00:27:59,500 I'll add the way you explained the beginning, like saying that 572 00:27:59,500 --> 00:28:01,300 your code will be run by the computer. 573 00:28:01,300 --> 00:28:03,500 It doesn't matter how well written or not. 574 00:28:03,500 --> 00:28:06,100 So well written at the end of the day will be translated to 575 00:28:06,100 --> 00:28:08,400 the same binary. But also the other aspect is 576 00:28:08,400 --> 00:28:11,700 that your code will be read by other people, including you 577 00:28:11,700 --> 00:28:14,600 yourself in the future and I like the way you avoid the 578 00:28:14,600 --> 00:28:18,000 phrase mentally, parse it, I do there's some jokes like maybe 579 00:28:18,000 --> 00:28:22,300 the amount of WTF when Reading you should I think maybe one 580 00:28:22,300 --> 00:28:25,300 gauge of like mentally are seeing it so hard, right? 581 00:28:25,500 --> 00:28:28,400 Thanks for the analogy here, another chapter in the book. 582 00:28:28,400 --> 00:28:31,200 I think you cover a lot about technical interviews. 583 00:28:31,400 --> 00:28:34,000 For example, the first is from the employer point of view. 584 00:28:34,000 --> 00:28:36,100 Right? What we should look at in terms 585 00:28:36,100 --> 00:28:39,000 of assessing candidates, whether they could play well with 586 00:28:39,000 --> 00:28:41,700 others. So, yeah, the interview process 587 00:28:41,700 --> 00:28:45,200 is very interesting and filled with interesting Insight that 588 00:28:45,200 --> 00:28:48,200 both bodies get. I like to think of the interview 589 00:28:48,200 --> 00:28:50,600 process of us getting to know each Other. 590 00:28:50,800 --> 00:28:53,900 We as developers, tend to think that, you know, I'm going to get 591 00:28:53,900 --> 00:28:57,000 interviewed. I'm going to let them know me. 592 00:28:57,300 --> 00:28:59,600 But through that process, you're also knowing them the 593 00:28:59,600 --> 00:29:02,900 interviewer, the company you're trying to work for and the type 594 00:29:02,900 --> 00:29:06,700 of communities they have. So, from the interviewer side, 595 00:29:06,700 --> 00:29:09,700 and I've done this many times, you get a sense of how that 596 00:29:09,700 --> 00:29:12,300 person will fit within your existing team. 597 00:29:12,300 --> 00:29:15,700 If you have one or within the existing company culture, if you 598 00:29:15,700 --> 00:29:19,700 will, so when going to an interview, if the person coming 599 00:29:19,700 --> 00:29:23,800 is Is late or even if it's an online interview, like nowadays, 600 00:29:23,900 --> 00:29:27,300 if they don't show up in time, that's a big telling aspect. 601 00:29:27,400 --> 00:29:30,100 If their CV is filled with passwords. 602 00:29:30,100 --> 00:29:33,800 That's also something that might not be exactly what the 603 00:29:33,800 --> 00:29:37,400 interviewer wants to see if I'm looking for a web developer. 604 00:29:37,500 --> 00:29:42,200 And I get a CV filled with react view, angular JavaScript. 605 00:29:42,200 --> 00:29:44,200 You're not telling me I could do what you do with them. 606 00:29:44,300 --> 00:29:47,900 I might think that you're just putting things because they 607 00:29:47,900 --> 00:29:50,100 sound about, right? But at the end. 608 00:29:50,300 --> 00:29:53,600 You might have read a few articles about react blade or 609 00:29:53,600 --> 00:29:57,300 done a few boc with you and have been working for a few months. 610 00:29:57,300 --> 00:29:59,300 The dangler. That's actually what I want to 611 00:29:59,300 --> 00:30:01,700 know. So you got to the interview by 612 00:30:01,700 --> 00:30:04,900 you incorrectly set the expectations on the interviewer 613 00:30:04,900 --> 00:30:07,400 and that person's going to be really disappointed with your 614 00:30:07,400 --> 00:30:10,000 profile. When, if you have set the 615 00:30:10,000 --> 00:30:13,100 expectations right from the get-go, that person would have 616 00:30:13,100 --> 00:30:15,700 tackle the whole interview differently, maybe whatever we 617 00:30:15,700 --> 00:30:17,400 need press with your action knowledge. 618 00:30:17,600 --> 00:30:20,500 So that's a big thing, especially if you Take it 619 00:30:20,500 --> 00:30:23,600 farther lying in your resume, which is also something that is 620 00:30:23,600 --> 00:30:27,000 sometimes only pretends to do. It's a big No-No in my opinion 621 00:30:27,000 --> 00:30:30,300 because you might get lucky and you might get an interview that 622 00:30:30,400 --> 00:30:33,500 sorry care about one particular aspect that you lied about and 623 00:30:33,500 --> 00:30:36,500 will not even ask what? But the moment they ask and the 624 00:30:36,500 --> 00:30:40,200 moment they hear you not replying confidently enough or 625 00:30:40,200 --> 00:30:42,700 correctly. The whole expectation that you 626 00:30:42,700 --> 00:30:46,400 set, really high is going down. The whole idea of your profile 627 00:30:46,400 --> 00:30:50,000 is scratched just because you took it a bit further. 628 00:30:50,200 --> 00:30:53,200 So that's also something that from up interviewer point of 629 00:30:53,208 --> 00:30:55,500 view. I personally look for I only 630 00:30:55,500 --> 00:30:57,500 need you to be honest during the interview. 631 00:30:57,700 --> 00:31:00,200 I don't need you to be the best developer ever. 632 00:31:00,400 --> 00:31:02,600 If you show me you can solve problems. 633 00:31:02,600 --> 00:31:05,600 If you show me that you can explain how you would solve 634 00:31:05,600 --> 00:31:08,700 those problems even without using the right technical term 635 00:31:08,800 --> 00:31:11,000 even without using the right password. 636 00:31:11,100 --> 00:31:12,400 At the time. I'll be happy. 637 00:31:12,500 --> 00:31:16,700 It'll be a lot better for me than having this huge curriculum 638 00:31:16,700 --> 00:31:19,700 from someone that is not able to talk about those things. 639 00:31:20,100 --> 00:31:23,300 So, that's the main thing. I would say from an interviewer 640 00:31:23,300 --> 00:31:26,900 purview that can be seen essentially, interesting and 641 00:31:26,900 --> 00:31:29,000 what about, from the interviewee aspects? 642 00:31:29,200 --> 00:31:31,700 So, you mentioned in the chapters few examples that 643 00:31:31,700 --> 00:31:35,300 actually is interviewees, should not say or should not show it 644 00:31:35,300 --> 00:31:37,600 whenever they go through this technical interview, right? 645 00:31:38,100 --> 00:31:40,600 Well, saying something like I'm at react developer. 646 00:31:40,800 --> 00:31:44,800 I mean, you are already putting yourself in the Box, you're not 647 00:31:44,800 --> 00:31:48,500 even letting the interviewer do it for you and if they don't 648 00:31:48,500 --> 00:31:53,400 need react then, Does that mean you can really pick up view or 649 00:31:53,500 --> 00:31:55,500 angular or any other JavaScript framework? 650 00:31:55,500 --> 00:31:58,600 I mean, this is Javascript will talk about the same language, 651 00:31:58,600 --> 00:32:01,000 different Frameworks. Why are you doing that? 652 00:32:01,000 --> 00:32:04,500 That's something that I think should not be part of your 653 00:32:04,500 --> 00:32:06,300 resume. If you want to say I'm a 654 00:32:06,300 --> 00:32:09,000 developer and I know react that's another thing. 655 00:32:09,300 --> 00:32:12,200 That's a whole different way of looking at it by saying I'm a 656 00:32:12,200 --> 00:32:14,800 react developer. I travel developer then what is 657 00:32:14,800 --> 00:32:16,300 that mean? You can really pick up another 658 00:32:16,300 --> 00:32:18,700 language. Can you pick another language 659 00:32:18,700 --> 00:32:21,500 within a reasonable number? Time, I mean, what's the big 660 00:32:21,500 --> 00:32:24,800 deal with it? Or why do you prefer one 661 00:32:24,800 --> 00:32:27,200 technology over the other? That's another big No-No. 662 00:32:27,200 --> 00:32:31,200 I mean saying things that well, I work on Linux because Linux 663 00:32:31,200 --> 00:32:33,600 the best development environment and windows sucks. 664 00:32:33,800 --> 00:32:36,500 Yes, every piece of technology is going to be better than 665 00:32:36,500 --> 00:32:40,000 others in different context, but that doesn't mean you can't make 666 00:32:40,000 --> 00:32:43,000 it work. I love working on Linux for any 667 00:32:43,000 --> 00:32:46,300 development task, but I've had to do in Windows actually right 668 00:32:46,300 --> 00:32:48,300 now. My computer is a Windows machine 669 00:32:48,300 --> 00:32:51,600 and I sometimes have to code or Look at code and you can make it 670 00:32:51,600 --> 00:32:54,300 work. So, why are you closing yourself 671 00:32:54,300 --> 00:32:57,800 to the opportunity of that work? Just because you're just too of 672 00:32:57,800 --> 00:33:01,200 a fan of a piece of technology that you can really open your 673 00:33:01,200 --> 00:33:03,900 mind to others. That's also a big problem to me 674 00:33:03,900 --> 00:33:06,800 when interviewee tells me that, I mean, you're showing me that 675 00:33:06,800 --> 00:33:10,400 you're not flexible enough. Our industry is always changing. 676 00:33:10,600 --> 00:33:14,000 You might be working in react right now because it's the best 677 00:33:14,000 --> 00:33:17,900 framework ever and tomorrow. A new one comes up, that is 100 678 00:33:17,900 --> 00:33:19,600 times better. Are you telling me you're not 679 00:33:19,600 --> 00:33:22,700 going to Make the switch just because you love react you're 680 00:33:22,700 --> 00:33:25,100 gonna stay behind of the state-of-the-art. 681 00:33:25,200 --> 00:33:28,300 You're telling a lot without saying too many words, you're 682 00:33:28,300 --> 00:33:31,400 showing a lot of bad things, if you go that route, so that's 683 00:33:31,400 --> 00:33:35,100 also something that I recommend not focusing on, you might have 684 00:33:35,100 --> 00:33:36,500 a list of preferred Technologies. 685 00:33:36,500 --> 00:33:38,500 That's fine. But you also have to make sure 686 00:33:38,500 --> 00:33:42,300 that it's clear that you're flexible that you're open enough 687 00:33:42,300 --> 00:33:44,800 to pick up all the things that you've never seen before. 688 00:33:44,900 --> 00:33:47,400 There are probably other things beliefs could be a bit longer. 689 00:33:47,400 --> 00:33:50,000 But yeah, that's the main thanks again for it. 690 00:33:50,100 --> 00:33:53,500 He has not to put ourselves in the box and always to try our 691 00:33:53,500 --> 00:33:56,300 best to solve the problems even even though you don't know the 692 00:33:56,300 --> 00:33:57,300 technical. Jargon. 693 00:33:57,300 --> 00:33:59,900 You don't know the algorithm. You don't know the passwords as 694 00:33:59,900 --> 00:34:03,500 long as the principles, how you use the top process to solve the 695 00:34:03,500 --> 00:34:05,400 problem. I think that's probably is the 696 00:34:05,400 --> 00:34:07,900 most important thing that the interviewer is looking for. 697 00:34:08,100 --> 00:34:10,500 So, for another live, look at your profile, right? 698 00:34:10,500 --> 00:34:12,600 You seem to have written a lot of books. 699 00:34:12,600 --> 00:34:14,600 Actually. I think if I contract Leaf 700 00:34:14,600 --> 00:34:18,300 already published about no Jazz and related to that, the other 701 00:34:18,300 --> 00:34:19,900 one is the code. Well with others. 702 00:34:20,100 --> 00:34:22,199 Which is another technical book so to speak. 703 00:34:22,300 --> 00:34:25,300 So how do you achieve all these? Because they are some people who 704 00:34:25,300 --> 00:34:28,000 Wonder at themselves or I want to write a book but never seem 705 00:34:28,000 --> 00:34:30,900 to be able to get it done. So maybe I can share your 706 00:34:30,900 --> 00:34:33,100 experience in this ball. I see. 707 00:34:33,100 --> 00:34:35,400 Yeah, absolutely and I was one of them as well. 708 00:34:35,600 --> 00:34:39,500 He maintained that has to happen is that you have to understand 709 00:34:39,500 --> 00:34:43,199 that any one that writes a book is not an expert of that acting 710 00:34:43,199 --> 00:34:45,400 on the ship when they're starting to write a book. 711 00:34:45,600 --> 00:34:50,500 So there's this misconception that a lot of authors are They 712 00:34:50,500 --> 00:34:53,600 know everything about their subject that doesn't necessarily 713 00:34:53,600 --> 00:34:56,400 have to be true. It may have been some situations 714 00:34:56,400 --> 00:35:00,000 as that's absolutely correct. But many times it's just not 715 00:35:00,000 --> 00:35:02,500 there, just good at researching, you know, and learning 716 00:35:02,700 --> 00:35:06,800 personally, the first book I wrote about rest API design for 717 00:35:06,800 --> 00:35:09,500 no chairs. I studied the book with that 718 00:35:09,500 --> 00:35:11,900 misconception. I was sure I knew where we can 719 00:35:11,900 --> 00:35:15,300 have a rest and that I was able to write a book because of that, 720 00:35:15,500 --> 00:35:19,300 through the process of expanding other chapters to have blad and 721 00:35:19,300 --> 00:35:21,700 through their s of research and allowing more. 722 00:35:21,900 --> 00:35:25,400 I understood that I didn't know a lot about rest. 723 00:35:25,600 --> 00:35:28,600 I came out the other way, Having learned the things that I didn't 724 00:35:28,600 --> 00:35:31,300 know. But I also told me that I don't 725 00:35:31,300 --> 00:35:33,400 have to be the expert to write a book. 726 00:35:33,500 --> 00:35:37,600 I just need to understand how to do proper research, and then how 727 00:35:37,600 --> 00:35:40,100 to explain that researchers actually in an interesting 728 00:35:40,100 --> 00:35:44,300 manner that's not easy at all. I'm not saying it's easy or 729 00:35:44,300 --> 00:35:47,700 simple, it's just their mom and you realize that you don't have 730 00:35:47,700 --> 00:35:49,900 to be the expert, you start thinking world. 731 00:35:50,200 --> 00:35:52,600 I can do research. I'm always learning about new 732 00:35:52,600 --> 00:35:54,800 things. Then I can try to explain 733 00:35:54,800 --> 00:35:57,300 things. Even if you are now writing blog 734 00:35:57,300 --> 00:36:00,800 posts or articles and you're afraid of taking that next step 735 00:36:00,800 --> 00:36:03,000 into a walk. Then you already know how to do 736 00:36:03,000 --> 00:36:04,900 everything. It's just a matter of creating a 737 00:36:04,900 --> 00:36:08,200 bigger plan for a bigger article if you will, so, that's the 738 00:36:08,200 --> 00:36:11,200 first thing I understand it. You're capable of doing it that 739 00:36:11,200 --> 00:36:13,700 you don't have to be that experience or anything. 740 00:36:14,000 --> 00:36:16,900 The second mental block that we tend to have is. 741 00:36:16,900 --> 00:36:20,200 Well. I may be able to write it but No 742 00:36:20,200 --> 00:36:22,900 one cares about it because I'm not one who's going to read it? 743 00:36:22,900 --> 00:36:25,600 Who's going to care about what I have to say about this topic. 744 00:36:25,700 --> 00:36:28,700 That's the second mental block that we have to go through. 745 00:36:29,100 --> 00:36:31,900 When you realize that, it doesn't matter who reads it, 746 00:36:31,900 --> 00:36:36,300 you're writing it for yourself, then it's just a matter of going 747 00:36:36,300 --> 00:36:39,000 through, the rest of the steps that are more mechanical if you 748 00:36:39,000 --> 00:36:41,500 will. So after you made up your mind 749 00:36:41,500 --> 00:36:43,200 and say, well, I'm going to read the book. 750 00:36:43,200 --> 00:36:45,700 I know how to write. I think I know how to write. 751 00:36:45,700 --> 00:36:48,100 Maybe you never did it before. I think I know how to write a 752 00:36:48,100 --> 00:36:49,900 book. I think I have the topic. 753 00:36:50,100 --> 00:36:53,000 I want to talk about then. It's just a matter of trying to 754 00:36:53,000 --> 00:36:57,900 find the publisher and try to come up with the idea of what 755 00:36:57,900 --> 00:36:59,200 the book going to be. Like. 756 00:36:59,400 --> 00:37:01,800 What am I going to say about this particular topic? 757 00:37:02,000 --> 00:37:06,400 You might do that beforehand and then go find the publisher or 758 00:37:06,400 --> 00:37:10,200 you might go to a publisher and say well I want to write a book 759 00:37:10,300 --> 00:37:13,900 about this because I've been using it for years or because I 760 00:37:13,900 --> 00:37:17,700 think it's an interesting idea. They might say, well then let's 761 00:37:17,700 --> 00:37:19,600 work together. Let's create the table, 762 00:37:19,600 --> 00:37:21,400 contents. Then let's create a plan for it. 763 00:37:21,400 --> 00:37:23,100 And then we'll start working on it. 764 00:37:23,200 --> 00:37:26,200 Many may think that they need the book written beforehand, 765 00:37:26,200 --> 00:37:29,400 which is not true. They may think that there is no 766 00:37:29,400 --> 00:37:32,200 way to reach out to a publisher which is also not true. 767 00:37:32,400 --> 00:37:35,700 Most of the Publishers I work with and I looked at they 768 00:37:35,700 --> 00:37:39,300 usually have on the website contact form email or something 769 00:37:39,500 --> 00:37:43,100 some way for you to contact them and tell them about your idea. 770 00:37:43,300 --> 00:37:46,200 They also think that this Publishers will not really care 771 00:37:46,200 --> 00:37:49,400 about them or about their book ideas because they're not big 772 00:37:49,400 --> 00:37:51,700 Twitter. See, It is our big names in the 773 00:37:51,700 --> 00:37:54,300 developing industry. And again, that is not the case. 774 00:37:54,600 --> 00:37:57,500 They care about the content. If you don't have a big 775 00:37:57,500 --> 00:38:00,600 following or if you're not worked on big brushes before, 776 00:38:00,600 --> 00:38:05,000 that's not a problem at all. Most of them are super open to 777 00:38:05,000 --> 00:38:08,600 helping others in authors and walking you through the whole 778 00:38:08,600 --> 00:38:11,500 process. So it's actually a lot less 779 00:38:11,500 --> 00:38:13,200 painful that a little bit to think. 780 00:38:13,700 --> 00:38:15,400 Wow. Thanks for all this inside. 781 00:38:15,400 --> 00:38:18,000 So there are a few key things that I picked up here. 782 00:38:18,100 --> 00:38:19,800 The first is that, of course, you don't need to be. 783 00:38:20,000 --> 00:38:22,400 A all experts in this topic that you're writing about. 784 00:38:22,400 --> 00:38:24,400 So that is maybe one misconception. 785 00:38:24,600 --> 00:38:26,500 Sometimes. Also, you can do a good research 786 00:38:26,500 --> 00:38:30,100 about the topics that you want to write about and also write in 787 00:38:30,100 --> 00:38:32,900 an explainable manner, the findings from your research. 788 00:38:33,100 --> 00:38:35,900 And also don't think about whether people will read the 789 00:38:35,900 --> 00:38:38,700 book or not the end of the day. If you write for yourself and 790 00:38:38,700 --> 00:38:41,200 you are the only reader I think that is also another thing that 791 00:38:41,200 --> 00:38:43,000 could be an achievement by itself. 792 00:38:43,200 --> 00:38:44,800 The last one is about publisher, right? 793 00:38:44,800 --> 00:38:47,200 So you don't need to come up with a pre-written book as a 794 00:38:47,200 --> 00:38:49,000 draft. You can also reach out to 795 00:38:49,000 --> 00:38:52,300 publisher if you Topic, all these things, probably is a 796 00:38:52,300 --> 00:38:54,900 possibility. So don't think that you have to 797 00:38:54,900 --> 00:38:58,100 come up with a draft of, maybe 80% of the book and then share 798 00:38:58,100 --> 00:38:59,500 with the publisher. Correct. 799 00:38:59,500 --> 00:39:02,900 Some Publishers may ask for, like, a single reading chapter 800 00:39:02,900 --> 00:39:04,800 because they want to know how you write. 801 00:39:04,800 --> 00:39:07,000 If you've never done it. If you don't have any published 802 00:39:07,000 --> 00:39:10,500 work, they might want to look at how you explain things or things 803 00:39:10,500 --> 00:39:11,800 like that. How do you express yourself? 804 00:39:12,000 --> 00:39:14,700 Because that's also key. But it's just a matter of 805 00:39:14,700 --> 00:39:17,900 writing, a single chapter versus writing, 80% of the book, which 806 00:39:17,900 --> 00:39:20,700 is a little higher. One thing that Is also key here 807 00:39:20,700 --> 00:39:24,300 is that if you've never written anything before, you might be 808 00:39:24,300 --> 00:39:26,700 afraid that you're not able to express yourself in the right 809 00:39:26,700 --> 00:39:29,500 manner, you might think that your writing is boring. 810 00:39:29,700 --> 00:39:32,500 You're not explaining things correctly or you're doing it too 811 00:39:32,500 --> 00:39:35,000 complex. The thing also to understand is 812 00:39:35,000 --> 00:39:38,600 that you're not alone in this writing process, you write it. 813 00:39:38,600 --> 00:39:41,800 You be the author of the book and you'll take care of writing 814 00:39:41,800 --> 00:39:45,000 all the content, but they're going to be at least one some 815 00:39:45,000 --> 00:39:46,300 point. You just have a lot more 816 00:39:46,500 --> 00:39:50,200 reviewers of your work. Technical reviewers and Other 817 00:39:50,200 --> 00:39:53,800 type of editors that will give you feedback way before that 818 00:39:53,800 --> 00:39:55,700 chapters gets delivered to a party. 819 00:39:55,700 --> 00:39:59,200 So if you're not able to explain yourself correctly, if you're 820 00:39:59,200 --> 00:40:02,100 thinking that you might have a technical issue with an 821 00:40:02,100 --> 00:40:05,300 explanation, or you're not covering a topic long enough or 822 00:40:05,300 --> 00:40:07,500 good enough. There are a lot of filters that 823 00:40:07,500 --> 00:40:11,500 chapter has to go through before getting released and through all 824 00:40:11,500 --> 00:40:13,900 those features. You'll get feedback in the way, 825 00:40:13,900 --> 00:40:15,800 explain things in the actual topics. 826 00:40:15,800 --> 00:40:18,900 Are you cover? So, you'll be able to polish 827 00:40:18,900 --> 00:40:21,000 that chapter? Through that process. 828 00:40:21,100 --> 00:40:24,100 So by the time he gets released, it's a lot better than the 829 00:40:24,100 --> 00:40:26,600 initial draft. You're not going through that 830 00:40:26,600 --> 00:40:29,800 alone and doing the research yourself and trying to find 831 00:40:29,800 --> 00:40:32,000 yourself better ways to write essentially. 832 00:40:32,000 --> 00:40:35,400 So that's also a huge help that not only do people realize is 833 00:40:35,400 --> 00:40:37,700 there for you? Yeah, that's also a very key 834 00:40:37,700 --> 00:40:38,800 thing. I was about to ask. 835 00:40:38,800 --> 00:40:42,000 What if I didn't know how to write properly, all my English 836 00:40:42,000 --> 00:40:44,600 sucks, for example, she so thanks for reminding this. 837 00:40:44,600 --> 00:40:45,800 That actually you're not alone, right? 838 00:40:45,800 --> 00:40:48,600 There will be people along the way that can help to review or 839 00:40:48,600 --> 00:40:51,300 edit some of the stuff that Wrote at the end of the day. 840 00:40:51,300 --> 00:40:54,000 It's a team work again. Even though you are a single 841 00:40:54,000 --> 00:40:54,900 solo. Authorized. 842 00:40:54,900 --> 00:40:56,800 There are a number of people helped me along the way. 843 00:40:57,000 --> 00:40:58,500 So thanks Fernando for this time. 844 00:40:58,500 --> 00:41:01,100 I really love our conversation and learning a lot from you. 845 00:41:01,300 --> 00:41:04,200 But unfortunately we have to end the composition due to time. 846 00:41:04,300 --> 00:41:07,000 But before I let you go, I normally ask one question for 847 00:41:07,000 --> 00:41:10,000 all my guess, which is to share your tree technical leadership 848 00:41:10,000 --> 00:41:12,300 wisdom. So that people can learn from 849 00:41:12,300 --> 00:41:14,200 this wisdom. All right? 850 00:41:14,200 --> 00:41:16,500 Okay. So three, the main thing will be 851 00:41:16,500 --> 00:41:20,100 and I usually recommend this for leaders and not only the There's 852 00:41:20,100 --> 00:41:23,000 actually everyone is to leave your problems at the door. 853 00:41:23,100 --> 00:41:26,800 This was a piece of advice. I got when I think it was my 854 00:41:26,800 --> 00:41:29,900 first show it clicked. You might be having a terrible 855 00:41:29,900 --> 00:41:32,300 day. You might be having problems 856 00:41:32,300 --> 00:41:35,100 with your family or whatever. I'm not saying they're not 857 00:41:35,100 --> 00:41:37,500 important. I'm not diminishing their effect 858 00:41:37,500 --> 00:41:40,000 on you. But my recommendation is, when 859 00:41:40,000 --> 00:41:43,100 you have to start working, just drop them at the door. 860 00:41:43,300 --> 00:41:45,900 Forget about them. Mentally block them for the 861 00:41:45,900 --> 00:41:48,400 time. You have to do your work, focus 862 00:41:48,400 --> 00:41:51,500 on that, get the work done. And don't let that affect you. 863 00:41:51,700 --> 00:41:54,900 It's not easy, but with practice, you can get better at 864 00:41:54,900 --> 00:41:57,700 it, especially to avoid. Letting that affect your 865 00:41:57,700 --> 00:42:02,000 performance, might sound a bit harsh, but life is filled with 866 00:42:02,000 --> 00:42:04,100 problems. And if we don't make that 867 00:42:04,100 --> 00:42:08,100 separation, especially now where a lot of us are working remotely 868 00:42:08,100 --> 00:42:10,700 from home. So it's a lot harder to make 869 00:42:10,700 --> 00:42:13,000 that split and say. Well, now I'm going to the 870 00:42:13,000 --> 00:42:15,300 office and the office is in your living room. 871 00:42:15,500 --> 00:42:18,900 You can really stop thinking about personal problems and 872 00:42:18,900 --> 00:42:22,000 start thinking about What problems if you are able to make 873 00:42:22,000 --> 00:42:25,700 that separation that sleep, then you can just get the work done. 874 00:42:25,800 --> 00:42:28,400 Be done and then go back to dealing with whatever is 875 00:42:28,500 --> 00:42:30,000 affecting you in your personal life. 876 00:42:30,200 --> 00:42:33,500 That's my number one tip. I give everyone that is working 877 00:42:33,500 --> 00:42:37,300 in our community, the other one and this is definitely meant for 878 00:42:37,300 --> 00:42:40,200 leaders. And one that I had to learn 879 00:42:40,200 --> 00:42:44,700 myself is to listen and let others speak up as a leader. 880 00:42:44,900 --> 00:42:49,200 You might think that you're the one making all the decisions and 881 00:42:49,400 --> 00:42:53,400 your Plan. Your idea is always right, but 882 00:42:53,400 --> 00:42:56,200 that doesn't necessarily have to be, I mean, that's not why 883 00:42:56,200 --> 00:42:58,700 you're the leader this this confusion. 884 00:42:58,800 --> 00:43:02,900 You think that you're there because you're responsible for 885 00:43:02,900 --> 00:43:05,800 every single decision depression and that's not the case. 886 00:43:06,000 --> 00:43:09,700 You have a whole team around you that is doing and it's working 887 00:43:09,700 --> 00:43:11,500 on this exact same pressure that you are. 888 00:43:11,700 --> 00:43:13,900 They will probably have a little bit ideas that you do. 889 00:43:14,100 --> 00:43:17,200 So the first thing is to make sure that you're listening for 890 00:43:17,200 --> 00:43:21,600 those ideas that you're creating a Safe space for them to speak 891 00:43:21,600 --> 00:43:25,800 up and then that they know they are safe there and that they can 892 00:43:25,800 --> 00:43:27,700 speak up and even disagree with you. 893 00:43:28,000 --> 00:43:29,700 That's the most value interaction. 894 00:43:29,700 --> 00:43:32,400 Inside a project is when someone disagrees with the leader 895 00:43:32,400 --> 00:43:34,800 because they probably have a better way of doing it. 896 00:43:34,900 --> 00:43:38,100 They may be right or not. But that disagreement will spark 897 00:43:38,100 --> 00:43:40,600 the conversation. Maybe none of them were right, 898 00:43:40,600 --> 00:43:43,700 but the end result of that conversation will be a consensus 899 00:43:43,800 --> 00:43:48,000 of a way to solve a problem that no one has thought about so far. 900 00:43:48,200 --> 00:43:50,400 So, definitely make sure. Listen. 901 00:43:50,400 --> 00:43:53,200 And definitely make sure that everyone knows that they can 902 00:43:53,200 --> 00:43:54,500 speak up because that's another problem. 903 00:43:54,500 --> 00:43:56,600 I mean, especially in distributed teams. 904 00:43:56,900 --> 00:44:00,800 We're not always dealing with people from the same cultural 905 00:44:00,800 --> 00:44:05,900 background and not every culture is okay with this agreeing with 906 00:44:05,900 --> 00:44:08,200 leaders or disagreeing with authority figures. 907 00:44:08,500 --> 00:44:12,000 So it's sometimes a bit harder than others to make sure that 908 00:44:12,000 --> 00:44:14,800 whatever is working with, you is actually agreeing with you 909 00:44:14,800 --> 00:44:18,200 because they honestly think that you're correct and you're 910 00:44:18,200 --> 00:44:20,900 proposing the right plan. Or they're just agreeing with 911 00:44:20,900 --> 00:44:23,800 you because they don't think they can speak up and tell you 912 00:44:23,800 --> 00:44:25,000 that. No you're wrong. 913 00:44:25,100 --> 00:44:29,100 So creating that safe space so that everyone can feel like they 914 00:44:29,100 --> 00:44:32,400 can open up and tell you what they think is key to leadership. 915 00:44:32,400 --> 00:44:34,900 Finally. It's kind of tied to a point. 916 00:44:34,900 --> 00:44:37,300 You have to understand that you're not there. 917 00:44:37,300 --> 00:44:40,000 You're not in that position because you're the one that has 918 00:44:40,000 --> 00:44:43,100 the most critical knowledge of the team, you know, the guru. 919 00:44:43,100 --> 00:44:45,800 You're not the expert on everything that you're doing. 920 00:44:46,000 --> 00:44:48,400 You're the leader because you have a set of skills that 921 00:44:48,400 --> 00:44:51,800 probably not all of the People on the team, have you probably 922 00:44:51,800 --> 00:44:54,500 have the best soft skills. You have better blending skills, 923 00:44:54,700 --> 00:44:57,200 but you're not necessarily the most technical of them. 924 00:44:57,200 --> 00:45:00,200 So it takes with the other one knowing that is why you also 925 00:45:00,200 --> 00:45:02,500 have to make sure that you listen to your team because 926 00:45:02,500 --> 00:45:05,200 maybe your plan, your tinkle is yours are not best informed. 927 00:45:05,200 --> 00:45:08,600 They're not the greatest. You might have the greatest Tech 928 00:45:08,600 --> 00:45:11,100 developer in your team, and you're just not listening to 929 00:45:11,100 --> 00:45:14,200 that person. So definitely it's about knowing 930 00:45:14,200 --> 00:45:16,400 your place. Knowing why you're there and 931 00:45:16,400 --> 00:45:18,200 understand that you're not above everyone. 932 00:45:18,300 --> 00:45:19,700 You're just fulfilling. Bye. 933 00:45:20,000 --> 00:45:23,600 Very different type of task and just understanding where that 934 00:45:23,600 --> 00:45:27,300 space is for you leaving the rest of the responsibility to a 935 00:45:27,308 --> 00:45:29,900 team. Wow, a lovely wisdom indeed. 936 00:45:30,000 --> 00:45:32,300 So I like the first one. Leave your problems at the door. 937 00:45:32,300 --> 00:45:34,900 Although now these days working from home seems like the door. 938 00:45:34,900 --> 00:45:39,200 Is that a bit attractive. So Fernando it was a lovely 939 00:45:39,200 --> 00:45:42,000 conversation when can people expect to see your books? 940 00:45:42,200 --> 00:45:45,600 Like the cold well with others. So yeah, the books already 941 00:45:45,600 --> 00:45:49,100 available in mornings Early Access program of meat so they 942 00:45:49,100 --> 00:45:51,700 kind of ready It looks very demanding site. 943 00:45:51,800 --> 00:45:56,600 Get what's already available, which I think is four or five 944 00:45:56,600 --> 00:45:59,400 chapters already. Like I said, you have different 945 00:45:59,400 --> 00:46:02,800 filters in the process. Six chapters already finished 946 00:46:02,800 --> 00:46:05,000 by. It's not on me yet because it's 947 00:46:05,000 --> 00:46:07,500 going through a peer-review process first. 948 00:46:07,500 --> 00:46:09,500 They're sending it to other reviewers. 949 00:46:09,500 --> 00:46:13,600 That might be potential readers. They fit the profile of the 950 00:46:13,600 --> 00:46:16,000 reader. They'll just look at it first. 951 00:46:16,200 --> 00:46:19,700 Give me the feedback on the will adjust it if we think we need 952 00:46:19,800 --> 00:46:22,500 To. So essentially, the book is out 953 00:46:22,500 --> 00:46:24,000 already. You can get it. 954 00:46:24,000 --> 00:46:26,800 If you get it through the me program, you'll get updated 955 00:46:26,800 --> 00:46:29,600 every new chapter every time their new chapter is released. 956 00:46:29,800 --> 00:46:31,400 Otherwise in the next few months. 957 00:46:31,400 --> 00:46:33,900 The full book will be available through the website. 958 00:46:33,900 --> 00:46:36,600 Another combo channels looking forward for that. 959 00:46:36,600 --> 00:46:39,300 Good luck with the process. So hopefully we can be able to 960 00:46:39,300 --> 00:46:41,600 see the book soon. Thank you for having me. 961 00:46:41,600 --> 00:46:43,900 I mean, it was really fun and entertaining. 962 00:46:46,500 --> 00:46:49,700 Thank you for listening to this episode and for staying right. 963 00:46:49,900 --> 00:46:52,800 Till the end. If you're highly enjoyed, please 964 00:46:52,800 --> 00:46:55,600 share it with your friends and colleagues who you think would 965 00:46:55,600 --> 00:46:58,400 also benefit from listening to this episode. 966 00:46:58,600 --> 00:47:01,500 And if you're new to the podcast, make sure to subscribe 967 00:47:01,500 --> 00:47:04,400 and leave me your valuable review and feedback. 968 00:47:04,500 --> 00:47:08,200 It really, really helps me a lot in order to grow these podcasts 969 00:47:08,200 --> 00:47:10,800 better. You can also find the full show 970 00:47:10,800 --> 00:47:14,400 notes of this conversation on the episode page at technology. 971 00:47:14,400 --> 00:47:17,600 Know the death website, including the full transcript 972 00:47:17,700 --> 00:47:19,700 interesting quotes and links to the resources. 973 00:47:19,800 --> 00:47:22,300 Horses and mentions from the conversation. 974 00:47:22,800 --> 00:47:25,600 And lastly, make sure to subscribe to the show's mailing 975 00:47:25,600 --> 00:47:28,800 list on technology. No, the deaf to get notified for 976 00:47:28,800 --> 00:47:31,600 any future episodes. Stay tuned for the next 977 00:47:31,600 --> 00:47:34,100 technique Journal episode. And until then. 978 00:47:34,300 --> 00:47:34,900 Goodbye.