Hello Baron, None of this works if a trader is not making Alot of money trading. This does not work for losing traders. Losing traders should keep working hard and ignore burnout until profitable.
Incidentally, a related topic appeared on Hacker News: https://oilyraincloud.com/2021/08/16/mental-health-impacts-of-a-big-tech-job/ "The toxic environment of the job’s demands can often be expected from management. It’s a constant grind, and over the years that has become the norm."
I'm linking to this article because I want to debunk a very damaging red herring that has pretty much become the norm when pointing out the horrors of software developer burnout. It's almost a meme that the cause of burnout is "just" overwork (hours above the legal limit of 8 per day). "It wasn’t until the past few decades that the idea of “going home from work” changed." No motherfuckers, it's not email and general connectivity that burns people. And I think I know the reason even burned-out mentally drained guys keep repeating that instead of pointing at the real culprit. Because the real culprit is too painful to contemplate, so deeply are we fucked / conditioned by the malware system employing us. The cause is: YOUR OWN LIMITATION. Not incompetence, you might be an 150+ IQ individual, and I have a hypothesis that the higher the IQ the harder the fall. It's in fact easier for imbeciles shitting IQ 70 equivalent code for as long as they can till switching project than for really smart people who actually put the effort to comprehend. You don't think AS YOU SHOULD! This is so ridiculously beyond my mental capacity that I might as well fuck off and find another job. No, you are conditioned into thinking "if I put more effort, I can take this exam too".
Luckily I'm old enough to have lived before even Hacker News took the format of Joelonsoftware to a whole new level, and Joel himself split ways with his business partner who had codinghorror but I still read it. So please read this carefully: https://blog.codinghorror.com/everything-is-fast-for-small-n/ Everything Is Fast For Small n
https://blog.codinghorror.com/everything-is-fast-for-small-n/ The problem with software is that we have: 1) At the top a manager as in "N=1". If he ever programmed, he no longer does it anyways, he "escaped". For him it's "simple". A 4 Mhz ZX-Spectrum machine would have solved that yesterday already so what are you incompetents still lagging today when the client is waiting? 2) At the field level we have 10. A simple project involves at least 10: a) programming languages b) microservices c) classes d) objects within a class e) parametrizations / generics / templates of a class f) configurations / annotations of that class g) parameters to the constructor or any function in the object h) number of function call stack levels one gets before something happens g) number of people who originally had an idea why this got so complicated Now if you familiar with the mathematics of permutations, the cyclomatic complexity of that horror is 10 for #a. For every instance in #a there are 10 instances of #b. Overall 10 times 10, so 10^2. Raise another power for each level and the number of code paths in the program is 10^9. ONE BILLION POSSIBILITIES. With some "bugs to solve" and "additional features that must fit in perfectly to add" and you have exactly one fucking "sprint" (1 week) to fucking deliver or else you're labeled an incompetent slacker who hates the company.
This,in bold....but switch the ice cream for Armodafinil.hahaha Joking aside,if you are a biohacker and fond of Nootropics,I recommend Armo over the generic Modafinil.I think Modvigil was where I started.
I largely withdraw my above recommendation. Its not my place to advise medication in lieu of good habits,especially quality sleep and nutrition. I have found Nootropics to give me a mental boost but they are no magic bullet,they have side effects and I did significant research before dabbling.