Why Is It That I Can Learn Programming Faster Than Art
Now that you know for how many hours per day it's usually possible to learn programming, let's talk about how to utilize these hours in club to make your learning process as fruitful and quick as possible.
The solution is to apply the popular time management method chosen the Pomodoro Technique. It's very uncomplicated: yous piece of work for 25 minutes, and then yous have a 5-minute break. Equally a result, all your learning or working time is divided into such xxx-minute blocks.
Every 25-minute interval is called "pomodoro", afterwards the kitchen timer in a shape of a tomato ("pomodoro" in Italian) that was used in 1980s past the author of this technique Francesco Cirillo.
Of course, today yous needn't have the same device to use this method. Just install some free Pomodoro app on your smartphone or tablet PC, or fifty-fifty apply one of many such web applications in your web browser.
You will simply need a timer and a counter of pomodoro intervals you practise during one day. And so, don't spend too much time on choosing the best awarding of this kind, even though yous'll inevitably detect tons of them.
During a 25-minute pomodoro interval focus exclusively on learning programming. Don't bank check your electronic mail and social networks accounts.
Also, don't multitask. You have to be 100% focused on your current tutorial department, book chapter, coding do, etc.
As you're having 5 minutes of rest after a 25-minute pomodoro, try to relax. The best fashion to exercise this is mindfulness meditation. Sit, close your eyes, and focus on your breathing until you hear the signal of the next pomodoro. Your encephalon and eyes will say "thanks" for this thoughtfulness.
If you lot also want to feel the same gratitude from your body, alternating calm meditation breaks with more than active ones. Information technology'south not a proficient idea to always sit on a chair or a sofa, both when y'all learn and when you lot have a rest, anyway.
And so every second break get up, have a 5-infinitesimal stroll, practise some simple concrete exercises. Endeavour non to think near what yous were thinking during the last pomodoro.
Sometimes, when I'm very sleepy, I even use these 5 minutes for a quick refreshing nap.
Whatever type of residual you prefer, during pauses between pomodoros don't become to Facebook, or YouTube, or the website where you lot bank check news. The idea of these five minutes is to give your encephalon a interruption, not to switch from one source of data (a tutorial, a book, etc.) to another.
The Pomodoro Technique may double your productivity
When used properly, the Pomodoro Technique may double or fifty-fifty triple your productivity, and this is non a joke or a motivational nonsense. Before I started using this system, I could barely learn programming for 2 or iii hours a day, and the last hour was usually pretty weak in terms of quality of learning, since I was already tired.
With this organisation I could acquire for iv to vi hours a twenty-four hour period (these numbers include all five-minute breaks), and the quality of each of these hours was very high. So, with Pomodoro Technique my productivity increased practically thrice.
Sounds too skilful to exist true, I know. I was astonished myself and have been a huge fan of this organization ever since.
Usually, when y'all learn programming, you might aim at x pomodoros per mean solar day (v hours). It's more reasonable to be pretty content if you managed to do viii of them, happy if it's 10, and proud of yourself if you hitting the 12 pomodoros marker.
These 10 pomodoros needn't be sequent. In fact, according to the concept of the Pomodoro Technique, you've got to take a long pause (15 to 30 minutes) after each 4 pomodoros, only you can utilise this rule a little bit more loosely.
For example, you lot can carve up your daily portion of pomodoros into several sessions, similar vi plus 4, or 4 plus 4 plus 2. When you take a long break, it might last, say, for an hour.
Notice your ideal number of pomodoros
Naturally, once I discovered the "magic" of pomodoros (I volition explain how it works below), I got very excited, and started thinking that maybe with this system I could spend on learning programming even more time, similar ten highly productive hours a solar day (xx pomodoros).
And then, I decided to test my limits. The first day of my experiment I managed to do 16 or 18 pomodoros. Just, if I were completely honest with myself at that moment, I would acknowledge that the last two or four were not that efficient, and they were more about the number of pomodoros rather than most the quality of learning.
The next day I did 12 pomodoros, and they too weren't very productive, since I was still extremely tired after the previous day.
The third and the fourth days were completely skipped, as I was so fed up with programming that I couldn't fifty-fifty call back about it without cloy. Eventually I returned to my "8 to 12" system.
Of course, your numbers might look dissimilar — feel free to arrange them. Maybe, your ideal range is 6 to 10 or ten to fourteen pomodoros a twenty-four hours.
And, as I said before, it's as well normal to call information technology a day afterward simply iv pomodoros if information technology was ii hours of studying some really difficult topic. Ultimately, your sense of progress is much more precise indicator of your effectiveness than the number on the counter.
Why it works and why 25 minutes are plenty
Some people dislike the concept of the Pomodoro Technique since 25-infinitesimal intervals seem too short. They say: "I need to stay focused for a much longer flow of fourth dimension in club to get something done".
I've got to admit: I used to be ane of those skeptics also. Just eventually I decided to give this method a try, and it exceeded all my expectations.
It turned out that an supposition that such a "dashed" structure of learning time isn't applicable to any serious task is completely incorrect. On the contrary, it keeps you much more focused for much longer period of time than you could achieve without the Pomodoro Technique.
One of the "secrets" of loftier productivity is "accept a rest earlier you're tired". This is exactly what the Pomodoro Technique helps yous do. You piece of work hard for 25 minutes, and so charge your "batteries" for 5 minutes. Every bit a result, fifty-fifty though you exercise work hard, you lot don't really experience tired until it's your 8th or tenth pomodoro for today.
Remember simply well-nigh the next pomodoro
Another significant advantage of this method is that while using it you don't need to focus on the big motion-picture show when you're doing some particular task. This is very helpful from the psychological perspective.
Your task is pretty simple: you lot accept to acquire just for the next 25 minutes. That'due south it. No large goals, no overwhelming plans. Just do your best for less than one-half an hour.
Often y'all cannot predict correctly how much time some programming task volition take. Y'all may expect to complete information technology in two hours, but in reality y'all might be working on it for 5 hours and however be far from the finish line.
If you're focusing on the fact that you failed to stop the job every bit quickly as y'all imagined, you lot'll probably be annoyed and angry. But if your goal were to do your best for those v hours, one pomodoro after another, yous'd exist quite satisfied, since y'all'd attain what you wanted — x pomodoros a day are a wonderful issue.
Even though the task however wouldn't exist completed, the difference in perception of the state of affairs would be huge. Your nifty accomplishment — a highly productive day — would be noticed instead of beingness lost amidst waves of negative emotions. This is especially important in the world of programming, where the outcome of your work is not e'er instantly tangible.
The Pomodoro Technique helps tackling intimidating tasks
The Pomodoro Technique helps tackling huge intimidating tasks, since with this organisation you don't have to complete them correct away, merely just make a modest step at a time instead. Endeavour doing it for 25 minutes, and then another 25 minutes, and another ones.
At some betoken you lot all of a sudden realize that about fifty% of the job is washed, including the most difficult parts, and yous're and so inspired that the other half of the job is completed as easily as a walk in the park.
The Pomodoro Technique turns a bad 24-hour interval into a skillful ane
Sometimes you may have a day when you're very reluctant to start learning or doing something else equally important. Pomodoros aid in such situations too.
You just tell yourself: "Ok, I volition do one or two pomodoros. It'southward only 20-five or, maybe, 50 minutes, I can do it. If they turn out to be a complete waste matter of fourth dimension, I'll just stop it for today."
Usually a couple of pomodoros with no force per unit area of a large goal are enough to smoothly gear up you for a total working twenty-four hour period, and y'all go along working even after the pomodoros counter exceeds the number "two". Thus the Pomodoro Technique tin plow a bad day into a regular good i.
Why 5-minute breaks are useful in programming
Another i advantage of relatively brusk intervals is that this method helps you avoiding many consecutive hours of fruitless thinking about possible solutions for some hard problem yous stuck with.
Often a five-infinitesimal break is enough to reboot your mind and to notice the solution y'all crave correct subsequently the next pomodoro starts.
Don't skip these breaks, even when information technology seems to be a good thought. You might feel that you simply don't demand it correct now, merely this is natural for the Pomodoro Technique — nobody expects that you lot should be significantly tired after each pomodoro, particularly after the first ones.
Of class, from time to time you might be and so excited about what you're doing at the moment that any break might seem incommunicable — even if yous technically do it, y'all'll still exist thinking about your job, so actually information technology won't be a existent break. Simply this is rather an exception than a mutual situation. Usually if you try to take a break, it'south not that hard to exercise and you'll get used to it quite speedily.
Generally speaking, each skipped intermission reduces the aggregate number of pomodoros that you can do for a day roughly by ane. It will be a price for neglecting the necessity to take a residual. So, if you work for ii hours in a row with no pauses, you'll exist able to exercise just well-nigh one-half of the pomodoros that you could practise if you followed the Pomodoro Technique principles more firmly.
Source: https://progmap.com/learn-programming-faster-with-pomodoro-technique/
0 Response to "Why Is It That I Can Learn Programming Faster Than Art"
Postar um comentário