Five ways to increase productivity.

    At first, I thought it would be just a translation of one very funny text . But it turned out that he was very bad, so only theses remained from him.

    Let's immediately agree - these tips are mainly suitable for programmers, and, well, let's say, very technical people. We ask ourselves a question - what is “productivity”? I don’t know about you, but I put in this word a very simple meaning. A person is productive when he performs the actions he needs with minimal strain for himself and maximum return for others. In the case of a programmer, a person who easily and naturally writes good code in a minimal amount of time is ideally productive. Enough words - here are some tips for you:

    1. Never look with your eyes, use the search functions. Always, always use the search if you are typing fast. A good example is opening a file in an editor. Use search or compliant (depending on the editor) and you will see how much faster it is. The same applies to the choice of a tab / buffer, if the editor does not allow you to go to the desired buffer - throw it out, otherwise look at point 4. The ideal editor works like this - press the button (in my case Ctrl-X + b) and enter the first in the input line several letters of a file opened in another tab. Finish everything by pressing tab and enter. With this method, I switch the open buffer in 0.2 seconds. With the mouse and eyes, I switch it in 1.4 seconds. Which brings us to the next point.

    2. Do not repeat anything more than 10 times. This critical number is different for everyone, for me it is exactly ten. Automate. More. More often, but not carried away by globalism. And not only in the code, in the editor, in the environment, but also in life. Need to break 20 chicken eggs? Make a box with holes and cut off the sharp part of the egg. 11 times to write a trigramaton on a fence? Make a template and buy a paint can. Do not forget that keyboard shortcuts are in almost all software. Every time you take your hands off the keyboard, you lose time.

    3. Learn scripting languages. Python, Ruby, Perl, Bash, Javascript, CMD, VBasic. Just grab the one that is closer to you and write-write-write. It is clear that it is easy to choose if you work in windows - for you only CMD and VBasic. Unixoids are available a little more, I think this is one of the reasons why geeks are so actively switching to Linux. I know that learning is not easy - but necessary. There is one strange recipe - try working from the console for 2-3 weeks. No, do not refuse windows and so on - just open a terminal window or cmd and work from it by running the script interpreter you need. And for God's sake, no far / mc / nc, etc. - Your goal is to learn how to write scripts. After these 2 weeks, you will return to the familiar environment with quite a lot of knowledge about how the scripting language works. Let me remind you that for python and ruby ​​there are ipython and iruby.

    4. Examine your IDE as much as possible. Ideally, discard the IDE in favor of a good text editor. I mean the editor . For example, ViM or Emacs. MacOS users can use TextMate, but it seems to me a miserable likeness of the left hand (a weak parody of MicroEmacs) Yes, and I assure you - both editors, and ViM, and Emacs have as many features as could not be dreamed of by any other. At the same time, both of them work fine without tuning, although I prefer Emacs. Of course, many still remember that Emacs stands for Eight Megs And Constantly Swaping, but 8 meters of memory have long ceased to be something out of the ordinary. Okay, back. Select an editor. And now use it wherever you can. Drive it into your head - you are using ONLY this editor. Because it’s impossible to know two editors well enough. Experts say that working with your editor to the fullest you get a boost to productivity of 200-500%. And looking at Bacek , for example, I believe in it. And the only minus from this knowledge is only in one thing - you cannot get used to it.

    5. Learn technology and write small programs. Allow yourself 20-30 percent of the time picking in new engines or databases. Yes, twenty to thirty percent of the time. I know that usually a lot less will stand out - but you don’t have to cheat me, I was like that myself, and I know how much percent of the time a programmer writes code. Move a little bit of the time you set aside for reading LiveJournal and dig yourself in the elbow in Django . Or sit down and write a script for winding up votes on Habré . In general, have fun and usefully. This greatly helps to relax at work without losing pace. And most importantly - it affects the structure of your code very well - now you know how and what others do.

    In general, what I want to say. It’s worth a little exertion, and your code will fly out from under your fingers. This is not to say that your hair will become clean and silky, and the girls from the reception will come to you themselves. Good luck.

    Also popular now: