About this talk
In this talk, Netko Hristov discusses the concept of craftsmanship in the IT profession, emphasizing the importance of precision and skill in creating quality code. He reflects on his transition from a QA engineer to a DevOps role and the challenges he faced along the way. The speaker shares anecdotes from his career to illustrate how rapid work pace and pressure often lead to poor quality output, detracting from the mastery developers should strive for. He argues for adopting a mindset of craftsmanship, advocating for cleaner, more thoughtful code and discussing the necessity of mastering tools and concepts in the ever-evolving tech landscape. Ultimately, Hristov encourages developers to take pride in their work and dedicate time to improve their craft.
Full transcript
Now I want to present to you the next lecture of a person who is known to me at least as Adasha, otherwise known as Netko Hristov. And he will talk about Craft FTmanship inyti. And in general, he is a person who has spoken at a lot of conferences recently and is quite well-known in the IT industry, a person who started in QA, then moved to DevOps, has
a lot of experience and will really show you a lot of things. In addition, this year he participated in the Danube Ultra, I don't know if he did it in previous years, to be honest, I wasn't interested. Four years in a row. Four years. Little, horror. Oh, yes. I present to you Netko Hristov and his topic. Applause. Oh, yes, we'll be talking about this for four years
Wait a minute. No one will hack me, please. I am Netko. Hello. Adasha and I know each other as Adasha, because I'm Nedelcho, but only mom and dad know he's dating me. And today we're going to talk about the master. For the master in our profession, for the master in general. And as someone who should give the best example of what a mastermind is, I wrote the
theme for about 17 beers in total and there was no time to rehearse it. So we'll try it together and see what happens. And so this is just me, my natural habitat. This is an official profile picture of the company I worked for because they told me to stop. I didn't know, I panicked and put the pizza on my head. And the rest of the time I
ride a bike. I don't have a pretty picture. So, right, I 'm a hasty person. The easiest way, if some such charka comes here, I hope there are no charkas now, but if some charka asks me, right, imagine one word and I will tell you one word. I am a father. That's the main thing. This is something I say that defines me. By the way, I hear
that they are clapping for Bojo. Honestly, no one will be angry if I go to the lecture. Even I want to run away right now to go listen to Bojo, because that's right, I'm a DevOps engineer, as Dasha said, I was QA before, then I went to the dark side and became DevOps. Oh, the enthusiasm, I do things, I read about things, I don't have time for
other things, but overall I'm interested in almost everything that can be in our world. I am a Homer. I have several machines at home. It starts with Enterprise hardware, like any normal person. Start a new hobby. Why don't you get some machine there with some hundreds of gigabytes of ram stuff? Now it's down right now, I'll have an up, right, so I'm preparing myself on the topic
little by little. Oh, I guess there are people who have some hobbies at home and I send memes that are usually borderline like, oh Why are you speaking in public? Now, it probably won't come as a surprise to you to find out that we don't get paid for this, but I've been to many big conferences, including the biggest ones in the country this year, and for Sadasha,
they're from conference to conference, see you there. Oh, no one pays us for this. He often does n't even pay for our transportation. I 'm from Varna here. Ah, but why do we do it? Why do we get such bad reviews on stage? Because we want to share things. Like there was a lecture about mutikas, which was great. By the way, I don't know if it's a
joke, but it was wonderful. And all of us here who are speaking want to share something. We want to share our motives that we have set out to achieve. We want to share good practices. Why should I, if I've been struggling for two weeks, do something and finally got it done, why should I share it with someone else who hasn't struggled for two weeks, well, let's start
from where I left off and where it doesn't look good at all, but let's start from where, oh yes, I left off . Anyway, they told me at the office that I was old, so I put up memes of old people. And wait a minute, first of all, because everyone says how long the guy has been in the industry, I think that's a lie, because even though
I've been in the industry for 20 years, I can still be as dumb as a dog. But my knowledge back then about open source, how I even found out about it, and things like that came from computer news. Have any of you read computer newspapers? Four people. Okay, so the bad news is that he needs to go get his prostate checked because it's about time. So yes,
they told me in the office that I was old and I started to accept myself as such and oh my, that's how the topic of craftsmanship actually came to me, because what is craftsmanship, right? Craftsmanship, half of the topic is in Bulgarian, half is in English, I think you'll get the hang of it . Ah, by definition, craftsmanship is the skill, the art of creating something, and
that something is not necessarily dated. We don't have to produce code, we don't have to give away any marble things or write code, whatever, right? It's more like a mainsette. Now, I'm not going to read you the definitions they made. You will read them yourself, but we pay special attention to precision And about cleanliness, no matter what we say, we are developers, developers and such, but in
fact we are craftsmen, or at least that's how I'm starting to see our profession, because when you go somewhere to have someone make you a knife, you're going to a master knifemaker. You don't go to Netko, who for the first time picks up a drill and starts doing things, you go to someone who understands. Why do n't we call ourselves that? We understand some things. Why not
take advantage of it? Let's be like that . And now, because mastery is now I will say that it is close to signority, yes, but it is not the same. For me, it was the same at first. I'm saying now that mastery is equal to the lords, which is not the case. It is a prerequisite, as you can see in the definition, which I won't read to
you again, right, because it's quite common to read that way in presentations. main question is can we boast of some code snippet, no matter what it is, whether it's some piece of yamalo, whether it's documentation, whether it's code, functionality, whatever it is , to boast about it, to be proud of it, and even more so to let someone who understands more than us see it. I haven't
produced anything like this in years. Why? Now wait for the next lecture, the next slide. Um why? Because we are constantly in a hurry, and I have written about it before. They constantly push, and at some point, when you want to do something like people, you can't, because the light is on, it starts to turn red and says, no, this is done. Clear, right? Yes, but we
have to do it, make it beautiful, make it nice. They say yes, but it won't be like that today, next week, right? We all know how this goes, and as you start to have more years of experience, and every time in every sprint, this happens to you in some way and you say: "Okay, fine, right, I'll just be ashamed." And when an intern or junior comes to
us to show us things and we say, "Look at my code now, don't look at this, and he doesn't look at that, he doesn't look at you either, because I only write nonsense and I even forget who writes good code, because they constantly fill it up, right, to provoke a lot, to chat, chat, chat, and the more the quantity, the less the quality. It's not mandatory, but
it's common now. Oh, they told me here that we can't swear, so I'll try my best. I have been Q for many years. This was my first profession. I've never done anything else before and I thought I'd die like Q. It turned out that DevOps is a different topic, but at some point I became DevOps and in my first month as DevOps, I was expecting a child
and we were buying, we were already in the final steps of buying apartments, I'm changing professions and I'm 30 plus. And all this and this was shortly before Covid, right, we didn't know about it. And all this is some kind of big catch, which is ready, right, for some things to happen and I'm kind of growing up, I'm super diligent to be able to, right, because I'm
starting not as a janitor like an intern, because I don't have experience and as a wall administrator I have, but I've clicked some things, not a full-time job dev and my friend caught me, he was my mentor. Vlado, you bastard, I'm starting to do some work and I still have stupid machines. There is no bau. I'm here, I 'm on Linux. He says now we need to
set up a database, we provision the database, but it takes about a hundred GB of space. You're out of disk space. He shouts, you know what? We will make one instance. This is a reproduction base. We're going to do some other things with this data. I'm shouting nicely. And now I'm going to drop it and he says no, because he's 100%. The operating system even starts to
show off in some way and says now we have to delete it as a file, because it's stupid, but we'll have to delete it. I'm Come in here. I have blackened the screen through varnish. He looks at my screen and tells me to come in here. Delete these files. We'll probably break the post-heat, but it wo n't happen anyway, right? Take it off. Nice. RMRF. Am I
sure it's falling? I'm sure. My team leader is there. I press enter and say good bye. And I get some kind of message at the same time, right, that there's no room for the gnome. I'm watching the dufa again, 100% silent panic. I shout, "What's going on here?" And he shouts, "Don't worry, we know where he is." Just stand there. I'm standing. Mhm. Yes. Where are you
logged in? Are you logged in too? Yes , I'm logged in. He shouted locally. Not locally. And so I [ __ ] up my first database. I cleaned it with RMRF in the most Chubanian way. So what was the difference, really? What would have happened, how could I have avoided this? It's disgusting what I did . If I had added no in my prompt, where I am,
then I did it, but first it has to be and then these things follow. A very small change that took me 30 seconds to add to the prompt and everything would be fine. We will shine red, full stop. No problem, I didn't do it. This is a great story because I tell it at conferences, when I go to conferences, and in interviews, I also tell it, and
now I deleted a database that could be produced, it could be produced, it could be eaten, it doesn't matter what it is. Someone could have been doing something on it all day, for example, all day, and there were backup copies anywhere else, and in the end, they just deleted their work. This is disgusting. And why is our masterologist actually dying ? Now, a little here may sound
like a little, but what we do, if we want to be good at it, is raise some signorti, which can, as we said a moment ago, be translated as a masterologist, a kind of mastery, and it is dying and we see it every day. Everyone produces ungodly. Are there children here? We produce tons of [ __ ] because that's how it has to be, because terraform I
can't write it. It will only take me an hour. I'm making him write it. We make 8500 rows. It works, I don't need to supplement it. I wo n't open this up, okay, but if the plan goes through and he's approved and everything works out, then the next guy will take care of it, right? We produce garbage every day and we produce garbage with something that is
trained on the garbage that we make and then the garbage that I post somewhere, which it has generated based on my decent generations, it makes things even worse and everything becomes one big pile of a [ __ ] [ __ ]. And what do we do? We copy, paste, and try to make it all happen faster because they push us to do it every time . I
haven't been to a single company where anyone has told us to hurry up now, if possible, you can raise this part by two or three days. We need a month, two or three days is a maximum, four is great, right? And you're bursting with work and we have time to be, to show that we're proud of it. We don't have time to show what we can do.
We don't have time to make it so that the next person who catches it does n't want to come and get it, but actually says, okay, this is pretty cool. We are no longer becoming you, we are not developers, but QA developers or whatever we are. We just produce some Frankenstein and this applies to almost everyone, because of course there are exceptions, excuse me for the exceptions,
but almost all of us produce such nonsense at some point in our careers. Before, there was also a copycat version of Uncle Akhmat, for example, he wrote some code that would work and you paste, paste, delete some stuff and some ugly things happen. And now what is happening? And we said it's complexity, so we'll talk about it in a moment, it'll be a very interesting topic and
delivery should always be fast, fast, fast. Come on, come on. There's no need, right, if we can do beautifully. It must be ready. We do n't give a [ __ ] about the other. And you're constantly giving me technology. I had one project that was on Asure and one project that was on Self Hosted, right, station. One ran on Python, the other on Java. Two separate ecosystems
in two separate clades that I managed simultaneously. Most of you have probably been in a situation where you don't have a single point of contact, only your browsers and console are the same. Everything else is a kind of brake and you manage them differently. Package managers are completely different. And the pipelines are also different. Everything, everything is different. And it's a random context that we do every
30 minutes, because you go to do something on air and they call me out of nowhere because something isn't working. Come see it. Okay. You go there, do something there for half an hour, come back, dig, dig, and so on all day. And at some point, oh at some point, it becomes very difficult. And so his complexes are rising infinitely. And what are we talking about? We
no longer have up togate and let's get this over with. We have mpm, we have PP, and all of this comes with its absurd details that we need to understand. I'm speaking from the perspective of a developer system administrator, but you get the idea, because even developers these days are half developers. By the way, I am very proud. There are some people who are just top notch
and our cognitive overload is constantly at maximum. What? Because when we get tired of work, we go to the bathroom to hide and cry for a while, open TikTok and start clicking there. And this brain, it doesn't have time to reflect a little , to be able to, to have our natural processes, which are there, to process all the stress, what's going on, it's left to us,
there's no car left and we constantly do it, I go to bed, we go home, we go to bed early, because we've read that we should go to bed early, to rest, I go to bed early and scroll through Facebook for four hours, is great. Now for complexity, LOC is Alliance of C and it's some relatively made-up benchmark, but people give it as an example of how
Linux's complexity has grown over the years and starts from version 1. And around 25 somewhere you can see how the complexity went up and in 6171 it reached about 40 million lines of code. This 40 is in millions, if I didn't write it. Yes. A million codes. And this just proves that the amount we generate, the complexity, everything is increasing, and it's not increasing by 5-10%, it's
increasing by a factor of times. That's what it looks like. Oh, if we make a request, no matter what, some request to oh oh wait, they're filming me here, I was worried about oh to Apache. A request looks like this in apparnally. How complex the whole thing is. All this dirt. And because I was looking for some diagrams, some things, and this one came up, which is
about bad words that are used in this, yes, from version 01, right, from the very first one to version 55 onwards, I haven't looked. By the way, it's very interesting. I promise to do some research, to see what these words are used for, that is , how many lines are used, and who uses them, because I'm almost convinced that the same person, and we all know who
he is, is using them. And the most interesting thing is that besides shtkra buard we have the word penguin. Apparently people are offended by penguins, but he's not a penguin, he 's just PR, he just can't throw himself out of nowhere now. Okay. Okay. And he very much means the purple line and it is constant. Someone has been ordering people around and calling them penguins since the
beginning. Do you see? Very jajin. That's right. When I was little, when I was little, and my grandfather, he's a craftsman, he was a craftsman, a master cartwright and he made carts, but the whole thing in the sense that there was no part to buy, he took some big boards, small boards, big trees, small trees, metals, things and you get lost in everything yourself, you do everything
yourself. And I remember it very well, because when I went crazy, we started making some traps with my brother. I don't know how he smelled it, the man, but there were some files lined up very well, I remember some files that were some generational from his grandfather, I think they came, which were some, it seems, they are mega old, perfectly cleaned, because sometimes you have fuel, oils
and some other things there, paints are also absolutely clean, lined up and in place, in order. So there's a board that they stand on there and most of your grandfathers, right, and our fathers do that. My father does this too. My father works in metal. His focus is this and he also has his tools lined up and if he has his hands covered in oil all day,
for example, his tools are not. And very often we will see all half of the masters, right, they other half do not deserve to be called such, but how did they arrange their tools? They are very important because they don't take out the money. And it's good that grandpa can have tools that he takes care of, that he understands how to work with. To see how he
worked with There was also a tiny dog that he used to make little homemade cakes, which are, because I'm from Dobrudja and there, the ear of wheat is a symbol, right? And he had a few ears of wheat on it like that, and all the time, delicately, every time, the same one, because that was the masterstroke, because you can't put something on it and give it to
people and they'll say, lady, you're no longer a masterstroke. You're doing something here that's not right. Dad in the same way. Okay, why shouldn't we be like that? We also have a toolkit. We also maintain the toolkit. We make sure our tools are good and where we need them, but they're digital. You've made some kind of bash script that backs up something for some project and hangs
it somewhere. This is also a tool, and if we maintain it and do our best to make a cool, clean bash script, who wouldn't do the backups, right? One of my first projects on GitHub was a fork of one such script that backed up files to and from MySQL. It's been a while since I've done it, that is, understood it, read it, and refined it to the
point where it suits me and I'm proud of it. Why shouldn't we have such a toolkit? Now, some nonsense here, because I have 23 minutes left. Aa daily we work with many things and make a huge context case. time. But I 've chosen some things here, right, most of you probably use the same sense, but just getting a Docker takes days, sometimes keeping your tools organized and
adequate, using it properly takes days. Learning over is not small at all. And back when I was in the middle of my QA career, everyone said, "Well, come work as a programmer, it 's easy." I was very against it even then , because it's not easy to be a programmer. What do we say? It's not easy being a programmer. Not everyone can be like that. For example,
I tried and failed, so I became a and and and it takes us a really long time. Here's our toolkit, which looks like this . Well, I keep discovering new things about Open ZTS. I haven't been using it for like a few years, let alone VM. Have I written vim here? I wrote it and removed it, because the picture below remained because someone was going to beat
me up. Someone like Maxf. And the context of the uching is huge, like blood. And now I'm saying some things, but let's see how I think we can do it to be a little better. And the purpose of the lecture is not to show you how to become a senior, right, to do some things that others can't. No. The goal is to add a little bit of
color to what we do. So let's not have another peace of crap, but let's invest a little of ourselves so that we can think about it, stop for a moment, say: "Okay, let's not make that script do it for me , like I do, I also do it sometimes, let's write it myself, let's learn something new with it, why not." The purpose of this lecture is rather
to think and say to ourselves: "Here we can actually improve our craftsmanship or craftsmanship or whatever we call it and make it a little better. And this will sooner or later lead to an increase in the signors, because it's one thing to give you a product that has been dropped on the ground seven or eight times, crushed and some dog has chewed on it. It's another to
see a nice box that is presented to you. The two things most likely mean the same thing, but one of them does n't have dog poop on it. So. Two two parts. Soft skills and hard skills. I believe that soft skills are much more difficult than hard skills. First and second, I believe that soft skills are learned. For example, I learned not to have panic attacks on
stage. Adasha and I were talking about this a while ago. And my peak in my career as a presenter was a few years ago, when I did some challenge accepted in front of about 700-800 people. the person. I went out, stepped on stage and had a panic attack and said to myself from now on while I was still talking and I was thinking and saying to myself
I will never go on stage again because I do n't want to go through this again. I do n't know how many of you have gone through this. I hope they haven't. It's a terrible thing . But I learned, now I'm not comfortable with it either, but I learned to get over it . I learned to be a communicator, I learned to let people, some people, know
that I don't want to wait for them in a street, to strangle them because they're doing stupid things. These things are learned. Proactivity is one of the most important things we can have. Why? Because we show that we are active. Because no one likes that idiot who sits at his computer and you have to go and push and poke him. Come on man, come on do something,
do something. When you can say okay, don't tell him to do it. You won't do more anyway and or less work, because personally I can't stand around like that and scratch the apricots, because it still burdens me in some way. So whether you're going to work, produce something or you're going to stand and look at the ceiling, count flies, for me like the cognitive load is also
down. Why not say it nicely, let's do this in such a way, let's read a little. They talked a little while ago about Dora. Let's implement some kind of framework, why not. Ah, this is super difficult. And let's listen and learn and gamify, because now I'm gamifying my head a lot and I'm constantly measuring some things. I'm ah, I measure some things, for example, I ride a
bike and I don't feel like going to see nature, because with good protection I'll get some pepper. I go and look at my average speed, and how many meters of elevation I've done, how far I've come, so that next time I can go further more, the third time even more and finally the first time when I successfully finished the Danube morning. That's 700 km there in 48
hours. And my mother asks me: "Now you see, he's from Vidin, he's been there for two days and my mother says" you saw a lot of beautiful things, tell us. I'm not saying anything, I did n't see anything, man. I was like this the whole time and I was looking, I apologize, I was like this the whole time and I was looking and looking, I was Well,
sit down and read it and see. Usually we write, right, when we have a meeting, we write, right, what is your agent. What am I going to talk to you about? Read it well. Let's talk about architecture in AWS, for example. Okay, let's remember something. We have AI on top of our chests, which is already relatively adequate. We have a little bit, we have a slide about
AI, please, because otherwise here I ca n't leave PCI, but who can tell us everything we are interested in. Good practices. Give me a good practice on how to do this project in AWS and it will tell you something. It may be true, it may not, but it will show us. We have to be prepared and preparation is a huge part, because otherwise we leave some fish
who just stand there, stare blankly at the camera and wait for them to ask you something and some I didn't hear the question well and they repeat it to you again. You have absolutely no idea what these people are talking about. We have to be prepared, because this is a sign of very high professionalism and it feels and it shows. The fact that our managers tell us,
right, for example, you're not prepared again, you're still scratching your head, right? That's another matter. And when you become a senior, you don't become like that, you just do it, you do it, you learn these eight libraries, these three technologies, you become a senior, for example, it happens gradually and when you do, then they change your position. One of the things that was very difficult for me
was making decisions. Let's say, for example, we'll do it this way. In AW, I can especially say, well, this same instance can now become a lambda function, because it's elementary and it will do this. However, I changed my mind a little and I think this will be done this way, because you need to be a decisive person and it doesn't matter if you're going to be a
QA, a developer, a developer, or something else, which is a perversion. It doesn't We said that communication is super, super important, very good, very important and this is a very good indicator of a person's maturity and Ownership. That is, let's take this project into our hands, let's do our project, our thing. Let's work on this. It may sound a little corporate, but the way I work, the
way I associate myself with it, actually helps me a lot, and empathy or, as I wrote it, the ability not to hit someone in the face when I start talking nonsense or when I get down on you. I have a story here on Friday about how I was wiped out by some instances. I wanted to go there to the person and, yes, to talk to him. It
didn't happen, because, right, hard skills, now I'm going through some topics here. I even wrote some things. There's no, there's no. We won't talk to them, but I believe that every professional, I was talking about an asthmatic administrator here, especially devops, programmers, everything else, should have some basic knowledge of everything, not only how it works, how to make a sheikh's Python to write later on your CV,
right, you understand Python, as I do. Well, let's know that there are some things here like, for example, the well-known Cors or ITREDS, it had some cache, but what is this thing? But why is it used? And when we started working with some parallelism, it suddenly turned out that it made sense to understand how the processor works here, how books work, how the network works, because a
little while ago at the lecture of Stor with the mutikas, a huge part of this was implemented there, because they use it. We teach operating systems at the university, no one is interested in how operating systems work. And why should n't we be interested in something that ours, our toolkit, our systems, our editor, everything works on this operating system and we need to understand, we need to
know how this thing works in order to be able to use it. Especially when we start to tinker with some things. Especially the first time I came in, when we were doing, we had some kind of attage at my first job as a DevOps and my boss says, now I'll show you something. You probably haven't been there. I'm shouting even if I have n't been there. Let's
see. And he enters a tilted proc and I'm some kind of person. I've never been here and he showed me some things and I'm just some kind of person and you have to operating system works. Especially since it's on Linux, right Linux. And we're not going to go into it, we're not going to give definitions. But there will be a few memes that will show us the
difference between one and the other. A wizard by the way, this is it , if they ask, right? And here's the first person out. If they ask, if they ask you what the difference is between teraphom and anble, you can easily sit there. By the way, all this will be on the net.info blog there after some time. And a package manager, something that we use every day
and that messes up all kinds of parts of the body every time, because you can use pip. Okay, but which version of Python will you use? But how will you install it as packages , how will you install it? How will you do it? How will you configure it? But where will the files with the ads be? And they are such a big list things that he
should know. I'm not even a developer, I should understand them. Aminangle Bundler is kind of terrible at this, but he has more. But since it starts now with the operating system, I've got them backwards , but up get install. Come on, um, we know what it can do and how much it can do. Well, homeb pakma. These are huge, huge projects with huge possibilities that we need
to understand how they work. Yes, yes. We'll finish in a moment. suddenly we start to wonder, let's say here it gets a little bit complicated and because they tell us that it's easy or at least until recently they told us everything was easy, it's not easy. Everything is complex and in fact it's super difficult, because being a Python developer doesn't mean that you understand Python. You have
to understand cloud, you have to understand databases, you have to understand NoS. What the [ __ ]? I mean why? And now I'm going to write some stupid things here. I guess most of you use them, so I won't stop a lot of them. And the things that I found, that I like so much, that I use in my daily life, may seem stupid, but in fact,
it is the stupid little things that help us a lot. And, I use OM ZSH, which I assume that most of you or OMZ, and OMI is just one of the two, depending on what we use. Aa I use it daily, I use its prompts, I use its themes, which are super convenient and the themes are actually from there, right, I added them and aa what I
told you earlier, I deleted that database. And there are various plugins that I use, right, we just pay attention to fifinder, because it is a game changer and has some kind of list. These are links, all the things, but you can't click on them. So you have to go to you have to go to the blog, yes to visit, so that there are at least two visits
this year, except for the Chinese and some small things that I use almost every day. You have probably forgotten those that are not styles places what the two do amazing in bash, right? Or for example, that you can do these and bray is expansion here. Where have you been man? And here here for example and to make several different files, if you test something or for example
this to return you the status. This for pйплаине does a super good job for me to return you the status from the previous command. What if something has failed, well here we can now handle this. Elementary little things. Two symbols are mine. And the most important thing in my entire life, which I always put where it is not, is to put on r alias minus. Come on,
minuses and preserfrott, because sometimes when you do rmrf slash and some variable that was not defined in advance and it becomes ugly. Netko cries, as well as the production environment that broke that time and we do some net stats for example, because we always often use things, why not we don't find them , why not make ourselves a grid, for example It's not colorful. These are little
things that help us and increase our toolset so much that it's convenient for us, it's cool for us. Most of the people who work here, most likely their bash or ZTSRC files are so big and this one with and this is normal, as well as VM, for example, if you're a fan of VM, some huge customizations, because on the one hand it's inconvenient and QBCL, right, the
classic is short, because it starts writing QBCL every time, right, we're not some people here. And most importantly, who will remember what's written here? Because we have to read the thick documentation. Everything is written inside. It 's complicated, it's hard. But in order to be good at what we do, we have to know how the technology works. I've added four comics on XX Headcd, which I can
never pronounce. FM side, the most important thing is. we use MAN, right, for Linux and users and for and for Onix users and it writes everything inside. It's very difficult. Okay, we use cheat SH, we use Expl, it's great. You put some parameters, it tells you do you know what? This command does something like this or SHcheck, which is something like a linter for bash and not
only, which also helps a lot. And just these four things can push you light years ahead. What you are at the moment, what I am at the moment, because it helped me a lot and let's read the ratafoma again. Also when I started my career, I wasn't still a student, wait for me to put it back here , don't read nonsense. And when I was a student,
I joined IRC then it was fashionable and I click on CC and I enter the Linux Bulgaria channel there or it was, I haven't forgotten anymore and ask things. Every second answer was because someone had to read it, right? Theфм fu men and here now we'll hurry up a little, because time is not running out. And my personal example or the price I had to pay to
become devops, and it is the following. A few very small things. Odem We all know World with Nana. Has anyone not heard of it? Are you the only one who has heard of it, man? Ofak. You write, you go to YouTube, write with Nana. This is great. She makes free courses on YouTube. She is great. She is simply the only resource after Akhmat and there and Bat
Khalip, right, who are randoms, right, who paid us a lot too, right, no kidding. And she is great. Take world with nana. I wrote here this morning on Mintinga. Yes. And it is free for most things. Most of it is free, for example, there are courses for kubernetes, for docker, for teraphom, for anbol, some for one or two hours , which are great or for a price
of 10 kibachas or so, maybe even less. You can now buy a course in VMI and do AWS and prepare for AWS certification, like I did, but you have to pay the heaviest tax, which is of all and it is not money, but time. time, attention and change some habits, because if I remove social networks and LinkedIn, which has also become a kind of social network to
scroll and is replaced by, for example, yudemy, I will become a freak, but I won't, because I'm lazy. And here are the academies that I have moderated. All of us have probably heard of all or most of these academies, like some that code for example is expensive, but yudemy has millions of millions of italics, which are 10 by 910, and most of the companies we work for
don't even accept them. In a sense, there is no obstacle anymore. Back when I was like a noob and when I asked my dad to explain to me, for example, how Apache works, because I do n't even know what that is and they said, "Dude, read the book, I don't understand English," there was a guy from ours with a book ordered in Bulgarian, who didn't give it
to anyone because we were like that, right? Back then, knowledge wasn't shared, but now it's shared, you can even get them. probably some Tuesday you can download them if you want there is everything there is even playgrounds already I clicked on the code of the codec cloud there you can enter you have your sbox If you enter, click, test, you don't even need to upload to your
computer. You don't need anything, except a browser, desire and some other lev. And, and here I have described the Indian man here, the Indian man is here again, but Jeff Gerling, that is, he is very much involved with NBA devices. Techot gives first place. Develops to kit. Now it is now called Develops NI tokit. Great guy. New work big beard. Their team. These are people who make
free content. Absolutely free. We want to do some project, we enter, we look for the project bam. People explain as if for noobs, there are some things written down. What helped me a lot is the first thing I bought on the third . We are waiting. And Stefan Marek, I do n't know how many of you have heard of him, but in AW is the world. In
the AW world, he pushed 80% of people to take the aa what was the name of this exam. Aahte Solutions Architect Yes, thank you Solutions Architect. 80% of the people in the world who called have read or watched Stefan Marek 's videos, which are great. It cost me $10. Well, of course the course costs money, that is, the exam costs money. The course, the preparation only $10.
And Maximilian Maximilian Schwarz Muller, did I say it right? Do cbenat bam. you read, the guy explains to you as if you've been picking potatoes so far, you take this, put it here, this, it works here. You want more information, bam, read, read, everything works and he explains it in a way that you can build something and then upgrade. And Hussein Nsar is great, he also has
a YouTube channel. He talks a lot about backend technologies and talks about very serious things that I don't understand at the moment. I understand, but I have a stick and I'm glad, right, the guy does crazy And the things that helped me improve my career. First of all, interesting are the documentation. Okay, the document. I still have 20 slides left, no problem. The documentation in Digital Ocean.
I don't know, most of you must have gotten there sooner or later. Great documentation, well written. They fired my entire team. Now it says I'm writing this already. I don't know if you know. And I bought a VPS from now on, it doesn't matter where I was first, now on digital $5 for $5 I clicked a virtual machine and based on this virtual machine when I went
to an interview for DevOps on zate they asked me what you did I said I have a VPS here show me it I logged in and started showing them $5 they secured me a career in Develops and I'm not kidding because there's something to show me because otherwise it's a bit difficult now if you've seen a person who does some visualization to show me this I did
I did otherwise I have a working block that runs on a VPS that costs $5 a month. He gave me the certification I was talking about a while ago and I clicked on a face every day, because otherwise without daily learning and clicking you can't become a good mentor. And so in five years I became a signor. Now how blue I am is another matter, but in
it check and I work with different brands of technology, we do things, but starting from the top down, we'll see $5 a month it cost me to get a VPS, install a stupid WordPress. Oh, yes. The most expensive thing that is actually left is time, attention and changing habits, as well as a few books that will later be posted. A few books that helped me a lot
to improve myself to improve my skills to become a good professional, right, as I said, there will be. Oh, by the way, Mark Mestri has a YouTube channel. He's great, isn't he? Oh, yes, you were everything, right. Bravo. And now we have to talk about AI, because I was at another conference the other day and there was only talk and I didn't stay. EAI is like a
drunk, tired programmer who knows too much, but doesn't hear very well, does whatever he wants. Sometimes it helps with small tasks, but sometimes it creates this. we can use it and it will help us, but it has to be in moderation, because otherwise it becomes a lot of Yes. And if we have to follow what is happening in the Opa, I apologize in the E world, right,
it takes time and energy. we have and we have a topic about security, which I couldn't even start, because as I see, my time is up. running. I'm just going to post my favorite meme, which I've been called out to the HR department of another company about several times. This is from a famous site, I don't know if they've seen it, but we're talking about pink promises
here, how security doesn't actually work at all. And so I talk a lot, if anyone has any questions or needs contacts or something like that, there's my email, my blog, where I 'll post the lecture in a few days. Plus a little more information along the way, because here I had to write some big sheets, so I had to give them away, I'm quite skilled, but if
anyone needs contact, here are my contacts and if anyone has any questions, they can come. Thank you very much. Thanю, addash. 2 minutes left. 2 minutes. So, we have time for exactly one question, which should be quick. So, if someone dares, there's a microphone over there in the lobby, they stand at it, ask a question, but they have to worry about what he'll answer, because Yes, you
can say it too, if you want. We have 2 minutes, 1 minute and 40 seconds. Otherwise he will say it's getting worse. Aha. I'll tell you, the organizers will get you used to it here. No, yes, I'll talk about the hamster later. Okay, someone, if there is one. I'm going to walk around here today and tomorrow I'll be in the bag. Come on, bamtini, please. A man
with tennis. That's right. Do I hear you? Extra. Well, what I'm talking about with increasing lines of cold, isn't that right, when it becomes quite adopted everywhere and drivers start to be used for everything there, because a huge part of the over and over is drivers that are integrated into it. Yes, Exactly. In fact, about 20% of the entire kernel are GPU drivers. By the way. That's
right. Accordingly, this is not such a problem because this is super isolated code. What is super super isolated code? I support the driver for everything possible. How much of it will I have to be? Yes. Yeah, that's why I said that we don't have a good metric for how complex it has become, because you have to choose, right? But I saw that people at Rady, for example,
use this and say: "Well, you know, let's compare it to something that we can measure." Someone took the version of some versions, right, of the kurnala and it just shows the amount that is what we have collected, right, what are what we have generated. This doesn't mean it has to be more complex, but it's usually a secondary indicator of that. I'm just saying, this is a case
of Gamy Find the Statistics. A Game Find the Statistics. In the way finding the statistics. If you will, that was a lie. No, no problem. You are right. Yes. But Reidy directed me there. Well, you can ask her. I asked him things. Okay, okay. Again, applause for Dasha. Stop, stop, stop. It's okay, people. Speech, speech, speech, speech. It's okay, people. Has no one entered this site? Honestly,
I'll leave it open for 30 seconds. No one decided to go in to see what was there. Imauser Imauser password. Well, lucky you. Do you know how long I wrote it, that Yes. Okay, that's it. If someone was interested, they took a picture to enter. Does
