Take a minute to write notes to yourself (on paper right in front of you) about the project you're putting down before you go and pick another up
Still messed up? Headphones on, music on, loud enough to drown out your surroundings and no lyrics
Really messed up? Go for lunch, take a walk, get out in the air and don't come back til the interruption has faded
Really really messed up? Don't accept interruptions any more. Be really firm about this with colleagues and managers. If you need to ringfence yourself to get stuff done they should be able to appreciate that, at the end of the day what's efficient for you is efficient for them.
Documentation. This gets you thinking about your project. If it's not easy to describe, it's probably not elegant enough yet
Static Code Analysis - FxCop, Lint, Cyclomatic Complexity, Security Analyzers. Now is a good time to step back from your code and check on best practices
Unit Tests. This again gets you thinking about the code and how to improve it.
I get interrupted frequently with phone calls, quotes for sales on more technical items, project managers asking me about feasability and time constraints, and junior developers asking for assistance with problem solving issues.
I've found the following, while not as ideal as being able to shut the office door and be left alone for hours on end, to be the most effective:
Install the Firefox add-on "LeechBlock" and add your most commonly used websites there. You could set a time-limit (i.e. 5 minutes every two hours) so you don't completely shut yourself off.
Wear headphones if you work in a cubicle or are busy.
Put your phone on do not disturb.
Turn off your email client and only open it at certain times (i.e. 11am, 3pm).
Ask co-workers to only see you during certain times as a courtesy (i.e. 11am, 3pm) but say you will still be available for emergencies.
Group as many like-tasks as possible together (i.e. Do maintenance tasks from 4pm to 5pm each day) and leave the remainder of your day for project work.
It's not ideal, but this is the best solution I have found.
Essentially what you are trying to do is get back into a productive "state" after an interruption and the key is to find the things that, for you, trigger that productive state. Although I am still learning about the subject, you may find some helpful answers in books on NLP (neuro linguistic programming).
Find small task to implement it first (for 1-6 hours long to do if you doesn't have interruption). During formulating what to do you slightly recall a state of the project. You can also look through the requirements from the customer or project manager.
Implement this task, but be in no hurry - you can spend much more time than you planned. Look around the code to recall deeper.
As for me after this I recall most things.
If you have a problem to continue after mentioned steps this can signal about some problems in the project like ugly design, absence of documentation, weak understanding of the purpose of the project or something else. And this is good time to have a fresh glance on the project. You can notice the problems which are difficult to catch when you are deep inside the project.
Of course this is useful for several days interruption, but not for several hours long.
Honestly, IMHO just sit down and do it. Complaining now is just a distraction from getting started. If you want to investigate how to ameliorate this problem in the future, do it in a few days, after you have picked the baton back up again.
发布评论
评论（7）
花一分钟时间给自己写笔记（在你面前的纸上），关于你正在放下的项目，然后再去拿起另一个项目
仍然一团糟？ 戴上耳机，打开音乐，声音大到足以淹没周围的环境，而且没有歌词
真的搞砸了吗？ 去吃午饭，散步，到空中散散心，直到干扰消失才回来
真的真的搞砸了吗？ 不再接受打扰。 对于同事和经理来说，要非常坚定地对待这一点。 如果你需要限制自己来完成工作，他们应该能够意识到，归根结底，对你有效的事情对他们来说也是有效的。
Take a minute to write notes to yourself (on paper right in front of you) about the project you're putting down before you go and pick another up
Still messed up? Headphones on, music on, loud enough to drown out your surroundings and no lyrics
Really messed up? Go for lunch, take a walk, get out in the air and don't come back til the interruption has faded
Really really messed up? Don't accept interruptions any more. Be really firm about this with colleagues and managers. If you need to ringfence yourself to get stuff done they should be able to appreciate that, at the end of the day what's efficient for you is efficient for them.
我的一些技术包括
Some of my techniques include
我经常被电话、更多技术项目的销售报价、项目经理询问可行性和时间限制以及初级开发人员寻求解决问题的帮助所打扰。
我发现以下方法虽然不如关上办公室门并连续几个小时独处那么理想，但却是最有效的：
安装 Firefox 附加组件“LeechBlock”并添加您最喜欢的内容那里有常用的网站。 您可以设置一个时间限制（即每两小时 5 分钟），这样您就不会完全关闭自己。
如果您在小隔间工作或很忙，请戴上耳机。
将您的手机设为“请勿打扰”。
关闭您的电子邮件客户端，仅在特定时间（即上午 11 点、下午 3 点）打开它。
关闭
出于礼貌，请同事仅在特定时间见您（即上午 11 点、下午 3 点），但表示您仍可以应对紧急情况。
将尽可能多的类似任务分组在一起（即每天下午 4 点到下午 5 点执行维护任务），并将当天剩余的时间用于项目工作。
将尽可能
这并不理想，但这是我找到的最好的解决方案。
I get interrupted frequently with phone calls, quotes for sales on more technical items, project managers asking me about feasability and time constraints, and junior developers asking for assistance with problem solving issues.
I've found the following, while not as ideal as being able to shut the office door and be left alone for hours on end, to be the most effective:
Install the Firefox add-on "LeechBlock" and add your most commonly used websites there. You could set a time-limit (i.e. 5 minutes every two hours) so you don't completely shut yourself off.
Wear headphones if you work in a cubicle or are busy.
Put your phone on do not disturb.
Turn off your email client and only open it at certain times (i.e. 11am, 3pm).
Ask co-workers to only see you during certain times as a courtesy (i.e. 11am, 3pm) but say you will still be available for emergencies.
Group as many like-tasks as possible together (i.e. Do maintenance tasks from 4pm to 5pm each day) and leave the remainder of your day for project work.
It's not ideal, but this is the best solution I have found.
本质上，您要做的就是在中断后恢复到高效的“状态”，关键是找到为您触发高效状态的事情。 虽然我仍在学习这个主题，但您可能会在有关 NLP（神经语言编程）。
Essentially what you are trying to do is get back into a productive "state" after an interruption and the key is to find the things that, for you, trigger that productive state. Although I am still learning about the subject, you may find some helpful answers in books on NLP (neuro linguistic programming).
如果您在执行上述步骤后遇到问题无法继续，这可能表明项目中存在一些问题，例如设计丑陋、缺乏文档、对项目目的理解不深或其他问题。 现在是重新审视该项目的好时机。 当你深入项目时，你会注意到那些很难发现的问题。
当然，这对于几天的中断是有用的，但对于几个小时的中断来说不是有用的。
If you have a problem to continue after mentioned steps this can signal about some problems in the project like ugly design, absence of documentation, weak understanding of the purpose of the project or something else. And this is good time to have a fresh glance on the project. You can notice the problems which are difficult to catch when you are deep inside the project.
Of course this is useful for several days interruption, but not for several hours long.
是的，祝你好运！ （我认为没有什么好的方法可以让打扰不完全被打扰。）
Yeah, good luck with that! (I don't think there are good ways for interruptions to not be complete interruptions.)
老实说，恕我直言，坐下来就可以了。 现在抱怨只会分散我们开始行动的注意力。 如果您想研究将来如何改善这个问题，请在几天后重新拿起接力棒后进行。
Honestly, IMHO just sit down and do it. Complaining now is just a distraction from getting started. If you want to investigate how to ameliorate this problem in the future, do it in a few days, after you have picked the baton back up again.