The use of Require.js

On the topic of procrastination I keep seeing people on the hacker news (you read it too, don't you?). , I feel it necessary to share with you how I have struggled with procrastination. However, what I am talking about here is mainly for programmers/artists, but in fact anyone can use it. First of all, the most important ....

It's not some old-fashioned motivational psychology talk.

I'm not saying that the traditional methods of coping with procrastination are wrong, but they are ineffective for me. When I am experiencing extreme depression, the last word of the theory I usually hear is "you just do it!". I have a lot of things to do. But I'm not going to read your 400-page Treatment Procrastination Handbook, nor do you have a self-adjusting action plan.

OK, here's a look at my method.

First, what do you want to accomplish?

Take the programmer as an example:

I need to add the discussion and message function in my program.

Take art as an example:

I need to make a logo for this client.

Answer the question. Have you got the answer? Very good, next.

Second, find the next step you need to do immediately, and without the pressure of a task.

The real art here is how I implement this step (note, how I implement it, not how it is scientifically implemented). Take a look at all your tasks, split them into small tasks, and split them up again until the task is as small as you think you can do without stress. Such a task should be able to use "too easy" to describe at this time.

Take the programmer as an example:

Create a path so I can access "myapplication.com/discussion"

Take art as an example:

Choose 3 of the most suitable fonts for this logo

Third, complete the task selected in the second step. Iv. start with the first step again. Why is this method useful?

First, the first reason is that this approach gives you no stress and allows you to be mentally prepared to do it easily. This task is so simple that you will want to simply do it. If you feel you have procrastination or depression, then this is what you need ... instead of a list of to-do that are filled with 100 tasks.

The second reason is the real reason-there is no need to worry about what needs to be done next. Or take a development or art design as an example. Each time you complete a task that is chosen for you in this way, the overall situation of the remaining tasks is likely to change. Before you finish x, you think y should be the next best thing to do. But when X is done, the task I chose with this method is Z .... For example:

Take the programmer as an example:

After establishing the path, the next step should be to query the database operation ... But after I've done this, I've chosen this method to develop the view layer.

An example of a artwork:

I want to pick 3 fonts, and the next thing to do is to select one, but because these three fonts are so nice ... The last thing I decided to do was to show them in Adobe Illustrator in 3 colors, respectively.

The last reason this method works for me is that it can trigger the starting power. Let you start to do. Once you've done it, you're not going to stop, and when you're done, you'll find it's so easy to do it step-by-step.

I have developed 4 large applications, all of which are used in this way to combat procrastination. This means that I'm not going to plan X and Y in the usual order, but go straight into design and coding. So, this approach is not just a small trick to use in an amateur project.

[English Original: How I fight procrastination]