Hello my dear umumbleuser! In this post I am going to discuss the sleep and productive activity. I am interested in the topic of my own productive sleep. The last few years I thought that the sleep is just a waste of time, and therefore, I tried to shorten the time of my sleep. But the more I did it, the more I began to look like a zombie, and then I began to look for an alternative. Consequently, this post will be a synthesis of all the information I found. Let us begin!
We learn during our sleep
I would like to begin that sleep is not a waste of time. It was a great discovery for me. Our brain does not rest during our sleep, it processes the information. All the time while we are peacefully sleeping and dreaming, the brain is processing all the received information for the day. What it finds useful it puts in long-term memory for years to come, but that is not needed it throws out. Thus, when we are awake, we only collect information for further processing in our sleep. So, how does this happen? Here we need to get acquainted with concepts such as the types of sleep.
The PHP blog touts more often the examples of bad code and anti-patterns. Well, someone else is criticizing the Hindus for the code ...
The code quality is something that should not be ignored or put aside for later. Such a delay is technical debt or code debt that will backfire for sure. You have to spend more time creating quality code and application architecture.
It is highly recommend to read Uncle Bob's principles of SOLID: butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod.
This text can greatly improve your ability to build scalable systems, particularly the principle of SRP.
Perhaps, the title of this article may be misleading, but the most of those that have been doing the programming and the designing of software products for a long enough will understand, what will be discussed further in this article. In the first place, it is addressed to the independent developers.
Let us ask themselves a few questions. How often do we rewrite the code from a scratch and try to improve it? How often do we change the design of an application during its development? Do we work too long with each method (or function) and try to think through all aspects of its use? Do we think that any programming serves as a lesson and source of experience? Do we try to use something new in the new code in order to develop ourselves? Do we pay more attention to the laconic brevity / beauty of code than the laconic brevity / beauty of applications in general?
If we answered yes on the most of these questions, congratulations - we are suffering from the perfectionism.
How can perfectionism ruin our life?
Let us start with the fact that the ideals do not exist in our world. We have to get used to this idea and try to live with it. There are no resources that will allow to write the perfect application or just the perfect code, whether we like it or not.