How to stop making bugs?

Question

Work organization

I do a lot, sometimes 10 times more. I don't know how to overcome this.
I already write tests, I know what and how, but even this does not calm me down.

I wrote my own projects, learned to do tests, plan and stuff like that.

But bugs cannot be avoided, then I forget to take the file into the commit, then I forget to save it, then I forget to add functions, then I change functions and immediately forget something. Then I change the file and immediately go to the next branch, but I forgot to save it there and I think that I have already done it. I sometimes drag and drop a file and the paths are automatically saved there, but I forget to go into these files to save, sometimes I forget that I need to specify the types somewhere, because the code worked without errors. Or I misunderstood the documentation or read but did not pay attention to important points. I recently accumulated 70 commits in a pull request with only 70 lines. Which is why there are so many mistakes. + Added technical bugs from I don't know what.

But usually when I do a task for the first time, there are minimal or no bugs, usually due to the fact that I am maximally immersed and checking. But as soon as I return to the well-known task, 100 bugs immediately appear. Because I changed somewhere. And in general, I also noticed that even in the text the same thing, sometimes I correct it several times.

And usually I know the rule of clean code, I use eslint, I studied algorithms and solved problems.

Answer 1

I do a lot, sometimes 10 times more. I don't know how to overcome this.

Well, if you don't know, then you don't.

I already write tests, I know what and how, but even this does not calm me down.

Tests should not reassure, they should fulfill their task, namely to deal with regression and basic unit testing

But bugs cannot be avoided, then I forget to take the file to the commit, then I forget to save, then I forget to add functions, then I change functions and immediately forget something

How are the tests going then? You can take test-driven-development. First write the test, commit it, make sure it runs and fails, and then write the functionality. And here, until the test turns green, you will not miss it.

Or I misunderstood the documentation or read but did not pay attention to important points.

Read carefully, pay attention.

But as soon as I return to the well-known task, 100 bugs immediately appear. Because I changed somewhere. And in general, I also noticed that even in the text the same thing, sometimes I correct it several times.

Bad function/variable names? Not enough comments?

And usually I know the rule of clean code, I use eslint, I studied algorithms and solved problems.

It is necessary to know not usually, but always, it simplifies.
Well, and so - self-organization is to force yourself to do it carefully. There is no magic ingredient.