Poor physiological analogy is poor.<p>Having some familiarity with both technology and physical training, there are causes of pain in both which have various causes and implications.<p>In exercise, there are various types of pain which may indicate little more than a solid effort, while others indicate acute tissue damage or injury which can lead to chronic or debilitating issues if left untreated. There's a huge difference between the strain of exertion in lifting, lactic buildup from a sprint, weightlifting burn, blisters or other chafing injuries, DOMS, the pain of tendinitis, a cramp, and plantar fascitis.<p>Some of these are momentary and transient, disappearing in a few minutes. Others are the result of tissue damage but will heal, if properly treated, in a few days. Others indicate either damaged or traumatized tissues which heal very slowly if at all, and can be debilitating if left untreated. <i>None are of themselves an indication of progress or "goodness" of a workout: you measure progress in training by your success in acheiving goals, not through pain.</i><p>Sure, DOMS after a hard lifting session, or sore muscles after a long run or ride can feel "good" in a sense, but it's not a sign of progress of itself.<p>It's a similar situation in technology.<p>There are things I encounter in technology that are similar: practices which are tedious, or vaguely challenging, or require thought, vs. others which are automatic. But there are also patterns and trends which just feel obviously <i>wrong</i>, and which practice has shown are really bad ideas. The current trend is to call these "patterns" and "anti-patterns".<p>Again, the important things aren't the presence or absence of pain, or even its intensity. If you want to gauge your progress toward goals, then <i>measure</i> your progress toward goals, not how much pain you're experiencing en route.