![]() ![]() Keyboards (and mice) won’t necessarily help you get into a flow state, but the good ones like MX Master Series can help keep you there. For those of us chasing the productive rush of a flow state, it’ll often start with the interface between your fingers and the computer: the humble keyboard. However, it’s true that a lot of a developer’s time is spent gliding atop a keyboard, translating their thoughts into code-doubly so if they use Vim, Emacs, or another console-based text editor. This is the mistake that bossware applications make, gauging whether employees are doing their jobs well by watching their keystrokes and mouse movements. Your speed on a keyboard doesn’t indicate how productive you are, just as the number of lines of code or commits you make doesn’t indicate how good an application is. This is, in fact, a terrible measure of productivity. ![]() After all, your programming speed is limited by the speed you can enter in the characters needed to create the lines of code that compose software. ![]() It may be tempting to think that a developer’s productivity directly correlates with their speed on the keyboard.
0 Comments
Leave a Reply. |