og Wild Forces Tech beta Hello everyone, this is a podcast about this not only with Sasha Kukushov, FisgetBrainz, Vanya Klychkov from DotaArt. Hello everyone. And Klyopyanikov from Blyna Petsa will be a company. Stop, you said you don't tell what company you are. So listen to you, we are listening to you. We are listening to you.
We are on Soundcheck, we are talking about Vanya for a long time, we are talking about the fact that Vindalemak is worse, I said that he is worse, because I am constantly working on it. Vanya says that Vindap is constantly working on it. You know, this is a reverse analog, classical halivar. And so we were talking about Vindap for everyone. Koltya, listen to me. Check it out, please, in the settings that you have set. Yes. And if we worked on the DDD, as if something changed.
But let's hear aboutetry and DNA to the video. So let's somere finally Floral se plinit говорить. You already have several more things left and one of them is the test of the Dreaming TV. And let's go to our previous question. And the question was not there. Because, you know, to ask questions about work, we had a release of the DVD. Half a year ago or a year ago. I don't remember. It was long ago. If someone was in the chat, please write down the previous release of the DVD.
So, we had already asked questions about the DVD. So, we asked the DVD today. And... Oh, I heard about it. Yes, it's great. Great. Great. And Nikolay Pianoikov, from a company that asked to ask, don't talk about any company. Why not? Yes, I'm a bit shy. I'm a bit shy. Great, great, great. Yes. So, let's see what our viewers said about the DVD. Test demo, development. It was a good offer. Tee, dream, development. And I'm a coffee. Okay, the chat is also cool. Tee, dream, development.
Tee, dream, development. Well, it's not your favorite. Tee, dream, development. Test-on-driven development. Well, it's a good offer. You know, we're going to make a link to such a big, a great DVD. What's your name? Yegor. I have a name, a problem. Yegor, a rich guy. Or a rich guy? A rich guy. I don't believe he's a rich guy. I don't believe. Well, a rich guy. A rich guy. A rich guy. A rich guy. A rich guy. A rich guy. And he's got good attitude about cool trying. Party keeping sectors.
How good is your opinion, understanding the opinion? How good is your opinion, understanding the opinion? How good is your opinion, understanding the opinion? How good is your opinion, understanding the opinion? Is the rich guy rich? In other words, is the rich guy rich? How good is your opinion? What does that mean to you?
I actually remember the situation in the city of Guayan, I was just one time a person wrote one time for me, maybe he didn't write it, he wrote it as if he thought, I don't know how it is, I felt it, but I did a lot of technical content, but I remember why he just wrote it,
I would have tested it myself, I would have been like a sad thing, I was a very many people, I was a very good person, and he continued to be a good person, he wrote it as if he felt it, I didn't see such content, I still remember the idea, maybe he thought, I didn't see anything, but I still remember it, I remember it, maybe he didn't know how it was, so you decided, you're done today, you invited him, you didn't meet up, but who will, who will, now the personsc命ается is the guy told you out.
Already had a Storm for 75 minutes, cap票 gets $1.9, I dont mind talking about nothing, whether the real world is asking about it A twist in which generals say there are courtchas which is the rule A legend find... are my favourite thing, my favourite dragon was a dragon posed by Teore, that Darth Vader To keep the walls normal and I have it. Vanya has designed his TbK�� as a solution to F Ivy trends. I didn't think about that. It must be a question.
I will involve you and I will try to resolve the conflict in his process. He's happily 10% I am a master of the Shafovka, who is DDD? Tire. That's a driven development. That's a driven development. Well, what? Well, let's start with a question. What is a TDD? Well, what can you see there? There are several links to the other books. Go to the Cloud, go to the DD. Go to the DD. We will talk about it. But what is a TDD?
Well, this is when you write a test, which will definitely fall, then you write a code that will make the test stand up. Well, this is a specific analysis. And in general, let's take a break. Can you or try to write a person in the TV to the Shafovka TV? Try to sleep in the warm night. Yes, let's break your mind. Can you or try to write one phrase? What is a TDD? I use the G, O, V and so on. One phrase. I think this marketing will be better. My opinion is about TDD. This is my opinion.
I've said it's a microservice, even more useful and clear. In any case, because TDD starts your TDD, you have this test, for example, and it starts there. And I've driven the world, I don't know, it's a real thing. My opinion is that TDD is very well written. One phrase, micro iterations. There's no even a word test. It's a part of the story, so it turns out that if you write a small, incremental change, and give them a test, it's more than TDD.
Imagine my favorite thing, when you try to find out some concept, make two things. First, remove some specific things, that is, we write tests. Second, remove the computer. Imagine that you're a slave to your own. You're trying to turn on the name of something, to realize that there's a possibility of concepts from our wanting concepts, to apply to people, who will understand how to understand how to use canonical examples, transistors and the theory of the task of three-dimensional.
In the book of the task of three-dimensional, it's very cool to tell how they tried to calculate these three-dimensional movements. The composition of the second-hand, the number of millions of soldiers, each of which was either transistors or transistors, or they were just... They were just saying that they were stupid. If you've already taken two bottles, you can take one bottle. If you have different bottles, then another one. And so on, that's the reason. So, now, to the TDD.
Again, this is my view. What is the TDD if you take a test? This is just a village. You sit next to your teacher. I'm sorry, my computer was chosen as a teacher. Yes, yes, it's a slave. Yes, it's a slave. And you sit and build a thing, and then you take a thing, and then you build it. You took a thing, you gave a test, you gave a pen, you quickly understand how to cut the top. They did it for a second, they did it for you, so everything works. Now you take it, for example.
So, I have a thing that I screwed up. It's not very good. Listen to him. I found the best example. Who made you with technique and then you put it on the table. Of course. Yes, imagine that you take me. Yes, you change the phone. I can tell you how to make a plate. No, no, no. I'll tell you how to make a plate. Yes, I'll tell you how to make a plate. Take a plate. And you don't know anything at all. What a mineral you need for a resistor.
And start to get the contents and the potatoes grow like this. You don't take it until you get it right. And then you get it right. And then you get it right. And then you get it right. You already order it from China. I need to... I'm against the other one. I'm against the other one. Look, I need to collect the phone. You're a guy. Okay, this is a big task. It's difficult task. You take it, for example. You just push the potatoes. And you don't get anything. You're a guy.
Now you connect the tape with the water to the steering wheel. And you also push the steering wheel. You start the steering wheel. You push the steering wheel. So that it can be removed. And you push it. And then you get it. And I don't like that. I have a steering wheel. I put it on the right. It doesn't work out. I turn it on the left. And say, hey, try it. They're already recording the steering wheel. They're all checking. They're working well. And then you connect the phone.
You connect the tape. And then you put it on the car. And you work. This is the TDD. So, every time your little step is running, you run a test car. It checks everything works. And the most important thing is that you look at each little step after every step. And then you see the steering wheel gets ranked. And you can choose or change the steering wheel in a different place. That way there was a smart toll. And you pull it out. The only option, is this test. What's the first experiment?
I wonder why.. We surely didn't青 suites in the development life. And i get a mistake.. So that's why I recommend it. like a developer, it is necessary to write these tests on these congresses. What are the users? Why? If you have... No, the players who are covering you. Bania! Bania! The players are covering you. Bania, you are now going to lose. Micro-iteration. You won't... You will send a build user every second. You've started to see what programs you have. Bania, we have a lot of questions.
I'm going to put it on micro-iteration. It seems to me that it's a bit different. Yes, you can use micro-iteration. But it seems to me that you've been waiting for them. But it seems to me that it's not the most important. For example, I don't know what it is. The idea is that you start to understand what you need. You are forming your head, nose or nose. Or if I was on the gallery, I was forming my head. I want the ship to come faster. I'm forming the ship. I'm doing something for it.
I'm making people to the ship. And I see that the ship became faster. I've been doing it before. I'm not so hot now. And the ship is getting faster. I formed the ship. And I'm doing a minimal action to make it more stable. In case of code, we just need to fix it. I'm automatizing it. Because you're trying to make a micro-iteration. Yes, you can move with small steps. It's a more effective approach. To avoid any contact. You need to go faster. Minimally, you need to fix code.
It's a formative requirement. And I'm putting my effort into it. And so on. I'm not going to write a set of tests. And then I'm going to write a code. What's not going to be written? No, it's not. I'm going to write it. It's going to be a TDD or not. I think it's a test. It's a complete test. We need to explain it in general. Let's go ahead. Let's go ahead. What is the version of the visitor who will be waiting for the test? Vanya, let's get started. We are programmers.
All these things are tools. And it's important to understand when you use a complete tool. In this case, testFest and TDD are two different tools. The key point is my personal opinion. TestFest is the best way to develop. And there is a problem. You can't write a test in 90% of the time. And if you can make a brain, you can understand how the system works, how the system works, the input and the output, then write a test immediately. It's very simple. It's a very good problem.
The problem is that you can make a brain to write a few tests. You can write a spec from the concept, and then write a realization. It's not the simplest thing. On the one hand, when we are all developers, we write a realization. And moreover, we write a realization in the process. Not only for the computer, but for some kind of computer controller. And we write a realization, and we have a lot of problems. Some are in the business, some are in the business.
And we are not as easy and easy to understand how the system works in Black Box. It's really hard to understand how the system works in Black Box and the input and output works. And the most important thing is to realize. You try to create a formula. Well, let's say, a Fibonacci. You are probably in the eyes now, there is no table, input, output, output, output, output, output. And you have a specific realization, a specific... A specific realization. A specific task. It's a very good question.
I'm not sure about that. I'm not sure about that. At the moment, the idea is, it's probably different from the fact that... The fact that you have some... Well, it's a good thing to have a requirement. You can take a real test, or I don't know, you can write a test, a copy that doesn't work. The idea is, a test here, like a Lisa, a folding, a straight-line Lisa. You write a test, it's a pure support, you're going to write it, and then you throw it into the principle.
You wrote it into the word, you can throw it into the principle. But it's... I like it. In reality. This word is, it's called metatology, but it's probably... It's like a working system. Where do I need to... I don't know, a key to the class, how often you have to make a mistake. It's probably a very remisting part. But, I don't like to give it to all of you. You have a great architecture, you have a great architecture. Where do you want to take it? Listen. I'm not sure about that.
I'm thinking about it. You have a great touch, and if you have a good touch, you'll have a different style. What's the other way? The story is that from what I've got a good touch, and TDD, it's the same story we take, and one of the things that we use for some rules, a great yellow arrow, we share it with a small task. And TDD doesn't write on my rules. It's written in my rules. You take small pieces of functionality. Look, I'm going to turn them on. You take a small piece of it.
The ring is already there. I also want to note that it's small. Where do I take a small task? Look, you took a phybanage, because you're comfortable to tell about small iterations. Let's take a small task. You have a micro-serving, which, I don't know, order, order, order, order, to use, draw, to the side, with orders. How do you do it? You'll always need to sit down. You have to think about the service. You have to think about it, or go to our work. We have to go to work.
There are some requirements that are written in some world. You have to design it. Okay, there are some requirements. There is a contract for this service. You have to look at it. Come on, come on, let's ask. Come on, let's ask. How do you take small iterations? You'll have to do it right away. Yes, I'll answer you. Yes, I'll answer you.
Remember, for those who don't remember our previous release, where we had a sample service, where we wrote some abstract work and people who took some basic work were given some instructions, and then later. Add some service, you already have some service to work on. How do you think, I'll answer you. How do you write it under the TDD? You start with some small thing. For example, this is the first thing. I write a service that if you come to user 0, then you come back to OK.
I wrote a very quick test that I checked if I came back to user 0, and then I did a test that was easy without any hif and wrote a TDD. And you put it in the next step. Now, we'll look at it. We have to do it in order to return to KSA when we have an ordinary user 42. OK, write a test. There is a new user method that we just did not use. And we'll check that the result is 42. I go to the method and just return it. And I got 0, and it's the next time. And I got 0, and now I write a test.
I add 0, and write a test that there is a ruby, and I put it in this code. The code is constantly changing. I add it in a little bit. And I add it all. Here is the key that we just took and we would write a code in the incremental. And we write a TDD. We write a code between each piece of this realization. In fact, every step we write a step and think about how to test it. And I write a test for it, and then do a step. In this way, you can see it. I'm glad to know how to test it.
What do you want from the code? Yes. A little bit of view as a person, who will you check it? And that's it. And you get as soon as you think about it, how you will check it. At first, and then the realization. And here, here is the most common thing. Because the most plus of this TDD is not the fact that we have a test. And the fact that we have a test is that we have a small micro-iteration.
And the fact that the realization is correct is that it is absolutely the probability because when you write a TDD, you practically don't turn on the brain. It's very powerful. That is, in fact, a drunk or a person who uses a TDD is very healthy because you really think, calm down, and that's it. You have turned on the test. Now you need to do the realization. You can't turn on the brain. You just have one plus of TDD. You don't turn on the brain. You just have to just make a test of green.
And you need to keep the abstraction. And suddenly, I just make a test of green. Write any code because there is a third shark refactoring. Optionally. But with them, it's pretty good because you can write a code and write a code and do something. It's okay. It's okay. So, Mr. Zurber does not need to do anything. But we will not do it. I do not know what it is. It's cool that the F is already. Yes. Well, how is it?
And so, in my opinion, when these TDD are said, it's the most important to remember that it's micro-transition, micro-iterration, micro-interesting. If we had the opportunity to write a TDD, to achieve micro-iterration without tests, we would have done it. But, unfortunately, this test is just a support without which you will not work with this mechanism. When you turn on the brain and just a certain absolute ditch, just to work with T. And that's all. Now we have to do it.
By the way, this is an important thing. One of the cool features of TDD is that this approach is completely allowed to be found. You are allowed to be found in a very simple way. Usually, we try to write a code to run a copy paste. You write a code and understand that you have to use a Control-C to make a method for 50-strikes. You have to make a one-strikes and then the Control-C and the rest of the method. Now, you have to do it like this. You are allowed to do it.
Yes. TDD allows you to do it. Moreover, the concept of TDD is that you when you are in a test and you are writing the fastest way. You are a D-Wobb, you just control the Control-C and then you are in the correct way. Then, you are in the right corner and you are in the right corner. I know that I have a code and I am in the wrong corner. This code is a code of TDD. It is a micro and a gradation. I think you have a black white and this TDD is not
TDD. Usually, in real life, there is a little different. There is a little iteration. I often think that I am in TDD. I am forming a check some cases of some inputs and results. There are many input parameters and many input results. I think that this is also TDD. Because it is more than I am not moving with such white stripes. But in principle, I am doing the minimum for my requirements. Yes, and this thing that you wrote, this is the best option to write a code.
If you can write a test and write a test, it is a problem that you do not get a test. And when you do not get a test, you can write a test. We have two ways. The first way is we look at our realization. We think how we do this realization complex. We do not think. The main thing is that in TDD, as an instrument, it allows you not to think.
To destroy our brain, to throw out the maximum thought, to stop thinking and to achieve this is the thing that we develop in this three tasks in each of the small inclement of functionalities. The second way is how to make this test with green. We do not get this kind of flashback that we have taken from the left. We think only about one thing. How to make this test with green. We do not even think how to make it beautiful. We do not think that it was a hyper-former.
We think that it was a hyper-former. We understand that if we break our test we will fix our test. Vanik says that this is not a real deal. This is just an instrument. This is such an instrument. Or can you write a realization with a complex thinking how it will work or what it will work. This is what it will work. Andrey Fazleev says that I am going to use only in my tests. This is a very important moment of Vanik test in TDD.
Because the concept of the exception of this one of the bugs is that it is going to work and it does not answer the question and how to make it work. And let's say, can you tell me what you have done? Well, it is a kind of remistential methodology based on the pattern of the method. You will write a test that checks the realization. Andrey Fazleev said that I am just trying to pass TDD. It is not very useful to use this method. It is not a benefit. This is a problem.
The problem is not the problem. It is not very useful to use a user or a writer. When I teach to call the settings, it is very useful to write a code in the second method. I am trying to use TDD.
I like TDD and I like TDD and another black white white one test and testing and not this test for any kind of testing, I when I work with some difficult system, for example, a little Lego or something like that, I usually such a step I try this system to break new requirements, I say, you should do something here it is, but it does not do it and the tube to even be afraid to even look how why it does not do it, I wrote this test, I understand why it is not doing it, and
as if I break the system so that it does and I look at the rest of the tests, I did not break if the test is there, here is another one, the option is created, as I do not go and do something in the system, the service that I do not understand, there is a lot of gossip, I do not
think I would do it, that is, I started creating, well, as a president, I am taking the conditions that she did not work before, but I want it to work and then somehow studying the device, studying code, understanding what you need to do, then I do this
change and then look at nothing I did not break, and then as if I bring it to a order, some changes are not small, here, here, here, it is also difficult to open such a large system, but to short, something to write at once, I think it is not real, yes, yes, you know what can be done, you are very correct, very correct, I noticed a good point, that is, to work with the legacy, make tests to break, again, the best change, again, in the head, imagine that the change is
TDD, the fact that after every change, you release the code and check how it was assembled, how it works, it does not work, it works great, everything is fine, and this is how you help you understand how to use the TDD, okay, good after every of my, after every step, to release the code, I check that everything works well, since I want to have a problem, without releasing the code, click UI to each step, how it can be optimized, and here is how our viewers write for me this
Andreev Fazleev, for me a test, it is the first difficult way to release the code, that is, it is, yes, I want to immediately apologize to Mr. Zuber-Belior, he writes, I write, I write, and you, Katana, you were a little drunk, he was not angry, and sorry, please, Mr. Zuber-Gelior,
on the other side, I want to say hello, yes, so, in general, the question is, yes, you are noticed, or you say that I did not listen to you, or you just just, like, with a little bit of, yes, I listened to the whole thing, yes, it turned out, the question itself is this, that is, where we have a test, where we have a TDD, and where we just have a test on the project, but look, if I, I, in general, one, firstly, the test always starts on each, well, not committed, but on each
push, in the repository, that is, the test is passed, as a local, also a number of people are not recognized, but they are not recognized in their local, I mean, the PR can be said that they use TDD in such a case, they have no tests, there are no micro-iterrations, no micro-iterrations, but what is the name of such micro-iterrations, as a micro-iterration, this is micro-iterration, this is the one-stroke, some parameters, there are minimal, these are automatic changes in code,
automatic changes in functionality, that is, a little bit added in functionality, already TDD, there, check it out, well, it is already this step, well, look, there is a bug that is one step fixed, that is, you take a test, in general, check that it is in the system, yes, but here is a fix, it turns out to be TDD, you do not release it later, but you will have to go, yes, but you think that you have made a small, small change, the initial test for it, then a small thing, by the way,
well, not at all, I am in fact, if you can understand how to fix it, then this is basically these micro-iterrations, so it is already a question, but I do not know how to fix it, I just write a test that repeats what I have, as bugs are written, but if you do it in your hands, yes, I create some kind of environment for my service, yes, let's start with the name, as if I did not know, let's say, yes, you can say, this is not for my sake, on the other hand, what is the difference, how to name it,
if, from my point of view, you have to go to the next format, the first thing is, we can write test, if we have all the systems, understand the Specs, what we expect from the system, so that we can metalize the test framework, we can do it, we can do it immediately and we are going to do some kind of a network of the perfect, if we can not, if we do not have any understanding of what there will be, but we do not understand, well, more than there, it is called a story,
how to say that you do not understand anything at all, and in this case, that you are considered a micro-iterrace on the simplest, just like that, check the null, make, return 42, make, return, and so on the piece, this is the ball, or that you can immediately analyze, that's right,
for this, immediately, analyze the functionality, as it is, or what, look, you need to understand where this check is on your own, but you are not just going to run on the keyboard, while the cat will not get it, the first one is to run the check on the null, so here is the
random one, while the thing will not work, if you are going to go, you can go to the keyboard and you have to go, you have to test further, the long-term keyboard, while this test is not needed, what test is needed, what do you want from your code, well, you thought at the beginning,
here for example, you should have A plus B, yes, then you wrote test, you are red, even if you are a sadistic keyboard, you are a kind of green at some point, you are fixed with a light, you do not do it, but the main thing is that this is written, everything, here, here, here,
here, plus B, everything is normal green, here, and you, it was a task of three to calculate, look, you wrote, you were a young man, you turned to a woman, you are a pretty I, you are green, you have divided the woman, you did not do it at the right time, let's say
if you say the task of three to the body, then our screen is made by test FES because you can collect a hidden set, by the way, it is called a solution, by the way, here, test FES, the screen is a purely method, you can use the set of these measurements and you
will take this set of measurements and the purely method you write the realization, so if you do not have it, that is, imagine, again, you will have three pieces of work, you will have three pieces of work, because we will now use it with a polarity of the sky, in general,
you have three pieces of work, no connection with the screen, no connection, and you, in every time, you do not know what will happen to you, that is, you have changed, this is after every operation, and you are the first change, you have shown that for these three points, you have a condition
of 42, you are just in the telemetry, you just write test, I will check that 42 in the telemetry, you just write a written 42, the next operation, you have 43, you are like, okay, and in this 42 and in this 43 test green, we go on, then we will see when you have a bunch of options, you are trying to find, how to do so, so that it was less code, I just saw this story, I saw it, I decided to code wars, in general, the fastest option was to use windows, which just, in short,
I put the table with the table, yes, yes, the solutions, and it actually did not solve it, it just took a very short time, it was a very strong method, I just counted it, I just wrote a small thing in general, a light thing, again, I think you are strong, forgive me, real life is very far away,
compared to when you are a code even to go ideas, you immediately think about it a little forward, and it is a problem, I'm like, no, no, no, no problem, you told the right, you think a little forward, and I
mix it all, because personally, I really write on the TDD, usually in two cases, the first case, when I am very bad, I don't want to think in general, but I have to write, and in the second case, when I sit, I understand, I just don't know how to solve, as I have no head, although it would be abstract solution to this task, the fact is that our brain, especially when it writes a code, it writes a code, it often already, you see the solution to the task, you already put your head in,
sometimes even in some images, how you implement it, and you, in my opinion, are the biggest problem of the TDD, because here, imagine yourself, you have this, it's like a lie that already wants to run, I'm like,
I'm going to say, I'm going to take it, I'm going to do it, I'm going to say, stand, stand, stand, he's not even starting, but when I run, or listen the example of a brain, this is a dog, this big dog which comes across, roughly enough, I'll put it on now, I'll fix the next one and now I'll say,
write the beginning letter, I'll do an evaluation, here's the comment, in other words, I was like, TDD isn't for DVD, I say, you are again good you can create a platform to perform an office, you accessories 1.3x to produce works and they are very easy to use right away that� primero peanut and use methods 3 and you can share which direction and understanding it or which direction does it need to reach Are you ready to decide which one you want to do? Or are you going to change your mind?
This is called, and I'm going to think a little bit about it. You try to make a certain argument for it, and you don't have to write a special one. But it's stupid, you don't know, you don't have to translate it, because you won't write it. Why do you do a support? You have a primitive idea of the idea. And you don't have a certain idea. Yes, but, damn, you can use this hybrid option. There are 10 ideas, there are a little bit of ideas.
And this works better than just a simple explanation of some kind of rule. At first, there is one test, it must be red, but damn, so peaceful. I agree with you 100%. Because I would have fixed the moment, that the theory, as any methodology, is hard to fix, it's not a pass, it's about our brain. It's just like it works, what happens to them.
And here, Andrey Fazlev, a shakarno, wrote a comment, if there is no abstract solution, I'll write a row of comments in the comments, then thoughts, then I'll explain. This is also a cool approach, I'll follow him. And he is one of the alternative options to work with micro-iterrances. At the same time, he is absolutely controversial, because the ideas of the approach are that we will realize how it will look, and we will not think about it.
And the approach, when we just go, I don't write a row of comments, I write what I need to do. He is probably going to follow the development, when we take and we take, we realize, the last few things. And you are absolutely right, that the hybrid can be hybridized. That is, the peculiarity, we are all different. Now I'm telling myself, I don't get hybridized by the idea. Because, well, I'm so focused on it.
If I start, if I'm not in the state of the ability to follow the whole structure, I'm very fast-reaching. I know how to make it beautiful. Now I'll do it literally for one code iteration, for one breath, I'll go into the state of the approach, and that's it. TDD, in my opinion, is a controversial state of the approach. That is, if you go into the state of the approach, then most likely TDD will not come to you, because it will be killed by the state of the approach.
On the other hand, you can hybridize this structure as Kolya says. I don't get it. I'm flying into the state of the approach, and that's all. Okay, let's go to Tesla. But if you balance it, it's great. It's also cool, it's also works. We are all different people. Three people are sitting on the stream in the podcast. We have different ways of thinking. So, by the way, we have found, I think, an interesting option. I use it as a good feeling when Kolya is using it.
But it's always a smooth transition from one methodology to another. And Vanya. I'm not sure where it is necessary to find different TDDs or whatever. Or just try to use them. I don't like that TDD is such a thing. I already talked about that. It's better to use it. You need to prove that you use these TDDs. You just write tests. Write tests. And all of that. I don't know what the test is. I have this whole month when it starts. And it's not TDD. And you use it. And you can just write tests.
Maybe you don't have TDDs. So, I need Kent Beck in the Vizitor's dressing room. He was walking with a faker. And he proved that he was a pure T-shirt. If he was a T-shirt, he would say that he is not the right one. I'm not sure. I'm not sure. I'm not sure. Vanya, I'm not sure. I'm not sure. I don't like it. Because it's not a great thing. It's a great thing. It's a great thing. And it's very good. I'm not sure. I can't write TDDs. But I'm just a 2-man. I'm not sure. And you're doing it as well.
Yes. We have a show-knots video. Playlist from TDDD. It's Meghalivart, which was Kent Beck. And the other cool guys. They wrote it right away. It's against the TDD card. That is, the TDD card is just an instrument. And the key thing, the key thing about this instrument is the micriteration. I would add that TDD is a recommendation set. Yes. Can you support them or not support them? And it will also be partially supported.
If Ivan likes TDDs, I believe that you started a program about the construction of a bug. I went to the test. You will make it a bug test. And then you will test it. You will say that you did it. It's called TDD. But it will be TDD. Well, the word says that if you don't have to support the black white, it will be fine to use the Xeromtonan. It's fine. Yes. Yes. But there are only few rules that need to be done. It's just an instrument that has some usefulness.
And you always need to understand that we are different people. And we have different conditions. And in different situations, in different moments of life, in different moments of special purpose, these instruments can be given or not. Ivan, try to take it. I don't know if it's not a situation that you are not going to be successful or if you are very bad, but you need to try. You have to follow these three steps. I just don't understand. I'm a test of a bug. I'm a test of a bug.
To the right, you say that it's a TDD. Do you understand? Yes. There is a test of these steps. And then you see, I have no idea what to do. I have to turn it off. I have to turn it off again. The problem of this methodology is that you need to write it down. No need. No need. No need. You have to write it down. And if you don't write it down, as a bug in the computer, you don't need to write down the code. And what's the point?
I'm talking about the fact that it's all connected to our work in our state. It's just an instrument. It's just that it's not related to the environment. It's just related to all things. It's just a religion. And in general, it's the same as the most important analogy. What kind of an idea can be brought to the world? What is this? This is an Israel world. I can't bring a simple analogy of an Israel world. It was just a simple analogy. Oh, that's it.
Most likely, you know, when you go to a product store, you can go to a product store and buy a list. And what about the number of numbers? The number of numbers. You're like, okay, today I'm going to go to a special methodology. You fill the list with the number of numbers. You don't want to eat them. And in the store you go to a list and you don't buy anything that's not in the list. This methodology is a methodology. It's a defense. If you don't have a list of numbers, there will be problems.
This methodology is not universal. But on the other hand, it's an instrument. It works. Let's analyze it. By the way, Alexander, Alexey, told me that the analogy is not a test. Let's go. Let's analyze it. I would say that the idea of this recommendation and if these recommendations someone will bring a пользo and destroy the brain or psychological destruction of a person. And in general, it's up to him to understand what his work is and to forgive his life, then you can follow him.
And how does it not matter? It can be a hybrid option from some useful recommendations, including the DVDs and anything. Well, Vanya? Yes, you can write a test. Do not look at all these DVDs, the main ones, write the tests before code, after code, the management of the video. During the code, you will write a book with any editor, what are the main ones, and the list of the purists. By the way, the list of the purists is the most correct.
I even think that the TDDs are more than all wrong, and the people who said that we only need to pay the TDDs. The TDDs will not be written by the code, it is not beautiful, but the code is really heard in the phrase that only the TDD will allow to write a beautiful code from the TDDs. My simple tip. The TDD is one of the tools. Always enjoy learning new tools. Thank you all, bye! Bye! Bye! Bye! Bye!