July 14, 2009 at 23:03The main thing is to crush things right
Today I want to tell (and discuss) with you one very useful skill in planning - the ability to correctly divide matters into components.
If you use a todo list, a diary, or any other tool for planning free tasks for daily planning, then I think it will be interesting for you to familiarize yourself with the contents.
So, when we use to-do lists for today, we most often pursue two goals:
- affairs are always before our eyes, you can go over them very easily and quickly
- the name of the case carries exactly the essence of what needs to be done.
This is exactly the second point that we will analyze in more detail .
There are several unwritten rules on how to name cases - the name should be short, but at the same time clearly reflect the essence of the matter.
Yes, that’s true, this rule is very useful. But not everyone understands to the end what it means.
Let's take a simple example: you are developing a site, there is still a lot of work to do, and for today you wanted to completely create a user model and an authorization / registration mechanism.
The easiest way to do this is to create a “site work” business for today.
This is completely impossible to do.
Let's take a step-by-step look at what will happen in our head if we leave this matter as it is:
1. You read the case in the todo-list
2. Your brain involuntarily wondered: “what did I want to do? "
3. remembered (or did not remember) all things and got to work
4. made a user model, returned to step 1
Do not you think that for such a simple action, how to remember what to do, too many points work out?
The most insidious here is the second point - because if you give the brain freedom to work, then it will definitely go to be distracted / dream and fantasize. At this stage, there is a very good chance that you will be distracted from work by reading rss or mail.
And now let's try to break the meaningless job "work on the site" into smaller ones.
We don’t need to think much here, it will come out:
1. think over the user model (note: DB fields, validations)
2. create the model
3. cover with tests
4. create registration
5. make registration templates
6. create authorization
7. make authorization templates
8. functional tests for registration and authorization controllers
Yes, there are much more tasks, but the algorithm for working with them will now be as simple as possible:
1. Read the task
2. Complete the task
Optimization is there! And most importantly - we cleared our brain of unnecessary information, because we no longer have to remember what exactly we need to do on the site, this is now the duty of the machine.
Well, as an element of motivation - marking 8 tasks completed is much nicer than one, but large.
I understand that for many I have not discovered America, but even such a simple thing as crushing tasks sometimes has to be thought out myself, although I read about it many times. The increase in performance from such a technique is simply huge, I do not exaggerate.
If you use a todo list, a diary, or any other tool for planning free tasks for daily planning, then I think it will be interesting for you to familiarize yourself with the contents.
So, when we use to-do lists for today, we most often pursue two goals:
- affairs are always before our eyes, you can go over them very easily and quickly
- the name of the case carries exactly the essence of what needs to be done.
This is exactly the second point that we will analyze in more detail .
There are several unwritten rules on how to name cases - the name should be short, but at the same time clearly reflect the essence of the matter.
Yes, that’s true, this rule is very useful. But not everyone understands to the end what it means.
Let's take a simple example: you are developing a site, there is still a lot of work to do, and for today you wanted to completely create a user model and an authorization / registration mechanism.
The easiest way to do this is to create a “site work” business for today.
This is completely impossible to do.
Let's take a step-by-step look at what will happen in our head if we leave this matter as it is:
1. You read the case in the todo-list
2. Your brain involuntarily wondered: “what did I want to do? "
3. remembered (or did not remember) all things and got to work
4. made a user model, returned to step 1
Do not you think that for such a simple action, how to remember what to do, too many points work out?
The most insidious here is the second point - because if you give the brain freedom to work, then it will definitely go to be distracted / dream and fantasize. At this stage, there is a very good chance that you will be distracted from work by reading rss or mail.
And now let's try to break the meaningless job "work on the site" into smaller ones.
We don’t need to think much here, it will come out:
1. think over the user model (note: DB fields, validations)
2. create the model
3. cover with tests
4. create registration
5. make registration templates
6. create authorization
7. make authorization templates
8. functional tests for registration and authorization controllers
Yes, there are much more tasks, but the algorithm for working with them will now be as simple as possible:
1. Read the task
2. Complete the task
Optimization is there! And most importantly - we cleared our brain of unnecessary information, because we no longer have to remember what exactly we need to do on the site, this is now the duty of the machine.
Well, as an element of motivation - marking 8 tasks completed is much nicer than one, but large.
I understand that for many I have not discovered America, but even such a simple thing as crushing tasks sometimes has to be thought out myself, although I read about it many times. The increase in performance from such a technique is simply huge, I do not exaggerate.