Merge pull request #26183 from Donkey-Hao/master

translated
This commit is contained in:
六开箱
2022-06-23 16:04:47 +08:00
committed by GitHub
2 changed files with 70 additions and 70 deletions

View File

@@ -1,70 +0,0 @@
[#]: collector: (lujun9972)
[#]: translator: (Donkey)
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (3 stress-free steps to tackling your task list)
[#]: via: (https://opensource.com/article/21/1/break-down-tasks)
[#]: author: (Kevin Sonney https://opensource.com/users/ksonney)
3 stress-free steps to tackling your task list
======
Break your larger tasks into small steps to keep from being overwhelmed.
![Team checklist][1]
In prior years, this annual series covered individual apps. This year, we are looking at all-in-one solutions in addition to strategies to help in 2021. Welcome to day 14 of 21 Days of Productivity in 2021.
At the start of the week, I like to review my schedule and look at the things I either need or would like to accomplish. And often, there are some items on that list that are relatively big. Whether it is an issue for work, a series of articles on productivity, or maybe an improvement to the chicken enclosures, the task can seem really daunting when taken as a single job. The odds are good that I will not be able to sit down and finish something like (just as an example, mind you) 21 articles in a single block of time, or even a single day.
![21 Days of Productivity project screenshot][2]
21 Days of Productivity (Kevin Sonney, [CC BY-SA 4.0][3])
So the first thing I do when I have something like this on my list is to break it down into smaller pieces. As Nobel laureate [William Faulkner][4] famously said, "The man who removes a mountain begins by carrying away small stones." We need to take our big tasks (the mountain) and find the individual steps (the small stones) that need to be done.
I use the following steps to break down my big tasks into little ones:
1. I usually have a fair idea of what needs to be done to complete a task. If not, I do a little research to figure that out.
2. I write down the steps I think it will take, in order.
3. Finally, I sit down with my calendar and the list and start to spread the tasks out across several days (or weeks, or months) to get an idea of when I might finish it.
Now I have not only a plan but an idea of how long it is going to take. As I complete each step, I can see that big task get not only a little smaller but closer to completion.
There is an old military saying that goes, "No plan survives contact with the enemy." It is almost certain that there will be a point or two (or five) where I realize that something as simple as "take a screenshot" needs to be expanded into something _much_ more complex. In fact, taking the screenshots of [Easy!Appointments][5] turned out to be:
1. Install and configure Easy!Appointments.
2. Install and configure the Easy!Appointments WordPress plugin.
3. Generate the API keys needed to sync the calendar.
4. Take screenshots.
Even then, I had to break these tasks down into smaller pieces—download the software, configure NGINX, validate the installs…you get the idea. And that's OK. A plan, or set of tasks, is not set in stone and can be changed as needed.
![project completion pie chart][6]
About 2/3 done for this year! (Kevin Sonney, [CC BY-SA 4.0][3])
This is a learned skill and will take some effort the first few times. Learning how to break big tasks into smaller steps allows you to track progress towards a goal or completion of something big without getting overwhelmed in the process.
--------------------------------------------------------------------------------
via: https://opensource.com/article/21/1/break-down-tasks
作者:[Kevin Sonney][a]
选题:[lujun9972][b]
译者:[译者ID](https://github.com/译者ID)
校对:[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/ksonney
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/checklist_todo_clock_time_team.png?itok=1z528Q0y (Team checklist)
[2]: https://opensource.com/sites/default/files/day14-image1.png
[3]: https://creativecommons.org/licenses/by-sa/4.0/
[4]: https://en.wikipedia.org/wiki/William_Faulkner
[5]: https://opensource.com/article/21/1/open-source-scheduler
[6]: https://opensource.com/sites/default/files/day14-image2_1.png

View File

@@ -0,0 +1,70 @@
[#]: collector: (lujun9972)
[#]: translator: (Donkey)
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (3 stress-free steps to tackling your task list)
[#]: via: (https://opensource.com/article/21/1/break-down-tasks)
[#]: author: (Kevin Sonney https://opensource.com/users/ksonney)
轻松解决你的任务清单的三个步骤
======
将你的大任务分为小步骤,避免自己不堪重负。
![Team checklist][1]
去年,这个年度系列文章覆盖了个人应用。今年,除了在 2021 年提供帮助的策略外,我们还在寻找一体化解决方案。欢迎来到 2021 年 21 天生产力的第 14 天。
本周开始我先回顾我的日程安排看看我需要或想要完成的事情。通常列表上有些较大的项目。无论来自工作上的问题一系列关于生产力的文章或者改进鸡舍当作为一项工作时这个任务真的很艰巨。很有可能在一个时间段我不能坐下来甚至在一天内完成类似例如请注意21 篇文章之类的事情。
![21 Days of Productivity project screenshot][2]
21 天的生产力 (Kevin Sonney, [CC BY-SA 4.0][3])
所以当我的清单上有这样的东西时,我做的第一件事就是把它分解成更小的部分。如著名的诺贝尔文学奖得主 [William Faulkner][4] 说的“移山的人,从小石头开始。”(译注:感觉与“千里之行,始于足下”是一个意思) 我们要解决大任务(山)并且需要完成各个步骤(小石头)。
我使用下面的步骤将大任务分割为小步骤:
1. 我通常很清楚完成一项任务需要做什么。 如果没有,我会做一些研究来弄清楚这一点。
2. 我会顺序的写下完成的步骤。
3. 最后,我坐下来拿着我的日历和清单,开始将任务分散到几天(或几周或几个月),以了解我何时可以完成它。
现在我不仅有计划还知道多久能完成。逐步完成,我可以看到这项大任务不仅变得更小,而且更接近完成。
军队有句古话,“遇敌无计”。 几乎可以肯定的是,有一两点(或五点)我意识到像“截屏”这样简单的事情需要扩展到更复杂的事情。 事实上,在 [Easy!Appointments][5] 的截图中,竟然是:
1. 安装和配置 Easy!Appointments
2. 安装和配置 Easy!Appointments WordPress 插件
3. 生成 API 密钥来同步日历
4. 截屏
即便如此,我也不得不将这些任务分解成更小的部分——下载软件、配置 NGINX、验证安装……你明白了。 没关系。 一个计划或一组任务不是一成不变的,可以根据需要进行更改。
![project completion pie chart][6]
今年的计划已经完成了 2/3 ! (Kevin Sonney, [CC BY-SA 4.0][3])
这是一项后天习得的技能,最初几次需要一些努力。学习如何将大任务分解成更小的步骤可以让您跟踪实现目标或完成大任务的进度,而不会在过程中不知所措。
--------------------------------------------------------------------
via: https://opensource.com/article/21/1/break-down-tasks
作者:[Kevin Sonney][a]
选题:[lujun9972][b]
译者:[Donkey](https://github.com/Donkey-Hao)
校对:[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/ksonney
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/checklist_todo_clock_time_team.png?itok=1z528Q0y (Team checklist)
[2]: https://opensource.com/sites/default/files/day14-image1.png
[3]: https://creativecommons.org/licenses/by-sa/4.0/
[4]: https://en.wikipedia.org/wiki/William_Faulkner
[5]: https://opensource.com/article/21/1/open-source-scheduler
[6]: https://opensource.com/sites/default/files/day14-image2_1.png