I could have as many monitors as I want, but I've developed a preference for virtual desktops instead. I mapped hotkeys to switching directly to 9 virtual desktops, then I developed a habit of using the hotkeys. That way, it's as if I have 9 monitors, not much desk space is consumed, I don't have to move the mouse very far, and I get all these benefits even on a plane. Pressing hotkeys really is as easy as turning my head.
My hotkeys are based on the mostly-unused Windows key. Windows-tab = show all desktops (using Compiz), windows-F1 = show desktop 1, etc.
A lot of my coding time happens in bursts. The process tends to go like this:
1. Look at a requirement and invent a strategy for implementing it.
2. Start writing the code.
3. Run into an issue that will require significant refactoring.
4. Plan a refactoring that will solve the issue.
5. Take a break. The break is required for stepping back and getting a big-picture view of how the refactoring will affect code quality. If the refactoring is large or complex, the break might take hours or even days. I might have to switch projects for a while.
6. Evaluate whether I am still happy with the planned refactoring. If I am not happy with it, go back to step 4.
7. Refactor and commit.
8. Write more code until I finally solve the original requirement. I may have to go back to step 3.
I don't know of any other way to maintain code quality. When I was a newbie coder, I painted myself into a corner fairly often by creating code so complicated that I was not smart enough to fix or improve it. Today, I recognize the limits of my brain, so I spend a good deal of time pondering how to simplify code and then simplifying it. That is the only way I know to remain productive.
Slashdot Mirror
Is this the sweetener that will attract users to laptops that can only boot DRM-laden Microsoft-certified OSs?
I could have as many monitors as I want, but I've developed a preference for virtual desktops instead. I mapped hotkeys to switching directly to 9 virtual desktops, then I developed a habit of using the hotkeys. That way, it's as if I have 9 monitors, not much desk space is consumed, I don't have to move the mouse very far, and I get all these benefits even on a plane. Pressing hotkeys really is as easy as turning my head.
My hotkeys are based on the mostly-unused Windows key. Windows-tab = show all desktops (using Compiz), windows-F1 = show desktop 1, etc.
Did anyone else read this headline as "Google Tracks Brainwaves As You Watch TV" and find it unsurprising? The Google is everywhere!
A lot of my coding time happens in bursts. The process tends to go like this:
1. Look at a requirement and invent a strategy for implementing it.
2. Start writing the code.
3. Run into an issue that will require significant refactoring.
4. Plan a refactoring that will solve the issue.
5. Take a break. The break is required for stepping back and getting a big-picture view of how the refactoring will affect code quality. If the refactoring is large or complex, the break might take hours or even days. I might have to switch projects for a while.
6. Evaluate whether I am still happy with the planned refactoring. If I am not happy with it, go back to step 4.
7. Refactor and commit.
8. Write more code until I finally solve the original requirement. I may have to go back to step 3.
I don't know of any other way to maintain code quality. When I was a newbie coder, I painted myself into a corner fairly often by creating code so complicated that I was not smart enough to fix or improve it. Today, I recognize the limits of my brain, so I spend a good deal of time pondering how to simplify code and then simplifying it. That is the only way I know to remain productive.