Desktop 1Desktop 2Desktop 3

別々のプロジェクトに複数のデスクトップ

複数のモニタは、効率を向上させることができますが, 複数のデスクトップには、生産性を向上: 彼らは私が勤務時間中にそうでない可能性よりも、より多くのプロジェクトで作業することができます.

Different projects can be logically separated from one another to eliminate distractions and intensify focus by placing them onto separate desktops. Switching between these desktops allows work to proceed on one specific project while other projects are in abeyance. This approach avoids the common pitfalls of multitasking while still allowing productive work to occur on multiple projects in parallel.

Blocking Problems

In the course of working on a project, I frequently run into roadblocks. These are situations when I am unsure of how to proceed or solve a problem that is blocking my work on the project. I observe diminishing returns in continuing to attempt to solve such problems if a solution does not become apparent after forty minutes of effort.

When my efforts fail, I will stop work on that project, write a note to my desktop on where I stopped and what I tried to achieve, and turn my attention to another project. Grouping different projects onto different desktops allow me to switch to a different project immediately.

I return to the blocking problem after a few hours. My work remains in the same state as before because the applications remained running and windows remained in the same position. All I do is navigate back to the desktop holding this project.

In this manner, I am able to quickly switch projects whenever I run into a blocking problem and return to that problem at a later time effortlessly.

Delays

My projects typically have delays. This can be caused by slow computers such as waiting for the software build, unit test, deploy, regression test process to complete or slow people on whom I am waiting to provide necessary information or complete a blocking task.

When such a delay occurs, I write a note on the desktop listing the project's next steps and then switch desktops to a different project.

Interruptions

One of my desktops is used as a "scratch pad" for miscellaneous work such as when:

  • an idea occurs to me while working on a project. I document the idea on the scratch pad desktop using OneNote and create a calendar reminder to review these ideas later in the week. Writing down the idea allows me to continue with my original project without further thinking about this distracting idea or burden or worrying that it will be forgotten. Switching between desktops allows this to occur easily.
  • an unplanned call or IM interrupts my work. I clear my desktops by switching to the scratch pad and can now focus attention on the call.

Examples of my Desktop Layouts

This is my typical grouping of projects when I work on SOFIns.

Desktop One
Desktop Two
Desktop Three
Desktop Four

Communication and Web

  1. Outlook Email
  2. Outlook Calendar
  3. Firefox

Software Development

  1. OneNoteの
  2. DokuWiki
  3. エンタープライズアーキテクト
  4. Redmin

IT Systems Development

  1. Puppet Master and Agent on separate VMWare Workstations
  2. Text Editors for Puppet Nodes and Roles
  3. Text Editors for Puppet Manifests
  4. Puppet Master Samba shares and Subversion client

"Scratch" Area

  • "Throw" emails and web pages to this desktop as a reminder to follow up
  • Switch to this desktop when interrupted by phone calls or meetings

Arranging Desktops

Projects are set up by navigating to the desired desktop and launching the required applications.

I also programmed the desktop software so that I can "Carry" または "Throw" an application between desktops.

Throwing a Window

Throwing a window is the process of moving the program to a different desktop while still remaining on the original desktop.

Carrying a Window

Carrying a window will move it to another desktop and also enable that desktop.

September 21st, 2012 投稿者 ジョンJaroker に提出された: Workstation, Workstation Software

コメントする最初の人になる. コメントを残す

あなたのメールアドレスは公開されません. 必須フィールドがマークされている *