Other parts of this problem, however, are very much under our control. Good practices can help us handle the amount of fatigue we feel at the end of the working day, so we still have some juice left to see friends, read a book or play a game.<\/p>\n\n\n\n
Let\u2019s look at what the manageable problems are, one at a time, and what good practices there are to take care of each.<\/p>\n\n\n\n
Cause #1 Thinking Too Hard (Yes, Really)<\/h2>\n\n\n\n
There are few jobs that are so preponderantly about thinking hard<\/em> and thinking well<\/em> as that of the developer. Said simply, there is very much that your brain has to process: different technologies, the way each of them works and how they interact with each other, problems both concrete and extremely abstract, line by line debugging, visualising projects before they exist and then holding that mental model in your head, logic, research, documentation… the list goes on. All of these things require intense concentration, sustaining the which for extended stretches of time typically leads to mental exhaustion.<\/p>\n\n\n\n There are two things that can be done to counter this. The first is an old mantra of programmers, which I expect you will have heard before: break your problems into smaller parts, and then work on those parts one at a time. This keeps the information that your brain has to juggle at reasonable levels.<\/p>\n\n\n\n The second thing you can do is very simply to give yourself time. Tasks that make you want to bang your head against the wall as a beginner will become simple with experience, solutions to recurring problems will be reusable (or even automated), and while you won\u2019t \u2013 nor should \u2013 ever reach a point where there is no mental challenge to coding at all, things are going to get easier. Ever heard the saying that \u201cyour brain is like a muscle\u201d? It gets stronger with training.<\/p>\n\n\n\n Work in a shop, and there will be times when there are simply no customers coming in, and your mind is allowed to wander. Programming, alas, doesn\u2019t always have this sort of downtime. If you\u2019re working on a hard problem, it doesn\u2019t matter if it\u2019s 9 a.m., 3 p.m., or after midnight \u2013 it\u2019s going to feel just as hard at all times of the day, which means that if you spend eight consecutive hours coding, you will experience it as the equivalent of a torrid, totally non-stop shift at a regular job.<\/p>\n\n\n\n Thankfully, this problem is the easiest one to manage. If breaks are not already in your schedule, put them there yourself. Several times a day, you should pause your work and do something else, like going for a walk and enjoying some fresh air.<\/p>\n\n\n\n You can do this spontaneously when you\u2019re beginning to feel tired, but if you find that difficult, get methodical. Create a timetable for your work which includes breaks, and then set alarms or reminders to make sure you actually take them. Usually this is recommended because it is conducive to problem solving \u2013 and it is! \u2013 but it\u2019s also essential to make sure your brain can regularly refill its tank.<\/p>\n\n\n\n \u2018Choose a job you love\u2019, goes the famous saying, \u2018and you\u2019ll never have to work a day in your life\u2019. The trouble with coding is that it is a skill<\/em>, not a job. As a developer, you could just as easily find yourself working on your childhood dream as you could end up doing drudge work. The reasons you should try and go for the former over the latter are many and obvious, but they are relevant to this particular topic because the nature of your work will inevitably affect how tired you feel at the end of it.<\/p>\n\n\n\n I\u2019ve known many people who learned to code purely out of material interest, as a way to access high paying jobs. If this is what you want to do and you have the resilience and discipline for it, that\u2019s absolutely fine.<\/p>\n\n\n\n But if you\u2019re concerned that the problems you\u2019re working on are leading to excessive stress and exhaustion, you should probably consider changing the type of problems to which you dedicate yourself. This may take time, especially if you have committed yourself to a professional specialisation and realised too late it was not for you, but it can be done and is very much worth doing. If you can bring yourself to code something that you truly love, not only is it not nearly as tiring \u2013 it can actually be energizing.<\/p>\n\n\n\n A common mistake among young developers \u2013 one that infallibly leads to regret in later years \u2013 is to ignore the long-term effects that programming can have on your body and health. Sitting down for too long can be very bad for your back, typing too much can be awful for your wrists, and staring at a screen all day will be hard on your eyes. Your body will translate all of this pressure as fatigue at first, and in due time, as pain.<\/p>\n\n\n\n If you haven\u2019t taken any steps to counter this, you should start right now, even if you are not yet feeling any symptoms. A standing desk, a mechanical keyboard, and a good chair are all valuable, but at the end of the day the most crucial factor by far is physical form. Go on walks at least once a day, not least to get away from the screen, and\/or get some exercise. Research routines that will strengthen your back and core. No amount of fancy equipment will make you feel<\/em> good if it is your own body that isn\u2019t doing well.<\/p>\n\n\n\n While the above are general guidelines that, I hope, can help some people feel more comfortable during work, it is important to remember that each of us is unique \u2013 physically, physiologically, and metabolically. Your energy levels on the job will depend on factors that only you can really know \u2013 and in fact you may very well be one of those people who don\u2019t find coding tiring in the slightest (in which case this entire article is off the mark!).<\/p>\n\n\n\n Know yourself, know your body, and find the solutions that work best for you. And if that means disregarding every last thing I have written here, then so be it.<\/p>\n","protected":false},"excerpt":{"rendered":" And what can I do about it?<\/p>\n","protected":false},"author":17,"featured_media":21532,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","footnotes":""},"categories":[42],"tags":[],"class_list":["post-21534","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-coding"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/posts\/21534","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/comments?post=21534"}],"version-history":[{"count":1,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/posts\/21534\/revisions"}],"predecessor-version":[{"id":62586,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/posts\/21534\/revisions\/62586"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/media\/21532"}],"wp:attachment":[{"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/media?parent=21534"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/categories?post=21534"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/tags?post=21534"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/www.wbscodingschool.com\/files\/AdobeStock-by-pressmaster_215707724-1024x682.jpeg\")
Cause #2 There Is No Downtime<\/h2>\n\n\n\n
Cause #3 Problems And Stress<\/h2>\n\n\n\n
Cause #4 It\u2019s Physical<\/h2>\n\n\n\n
Conclusion<\/h2>\n\n\n\n