I&#x27;m in the middle of reading &quot;Punished by Rewards&quot; and it&#x27;s interesting to cast this particular predicament in light of the proposition of that book.<p><i>If you&#x27;re writing code to get the reward of a salary, you&#x27;re not going to enjoy it nearly as much as if you do it for its own sake!</i> Rather, you&#x27;ll enjoy less the more you&#x27;re doing it due to extrinsic motivation.<p>I&#x27;m not sure of the solution, but I suspect you need to cast any of these challenges, whether they are really <i>coding</i> challenges, or rather team communication challenges, as something you&#x27;re excited (rather than anxious) to overcome and improve your skills at doing. Forget (in those moments) that you&#x27;re doing it for a salary, but decide that, in order to later improve strictly coding skills, you are wise to currently work on improving your communication skills, your ability to discovering the capabilities of existing code and frameworks, and perhaps your ability to document anything you learn for future reference (for yourself and others.)