Earlier quoted context omitted.
> I didn't expect this simple concept will need so many explanations. You and me both brother :) > No programmer will ever say "making the computer slower really helped a lot to write code". I guess I'll be the first, as a programmer I do this all the time, when developing browser stuff I frequently throttle the available bandwidth and introduce jitter in the network connections so I can see and understand how things…
You do that because your goal s “optimized code” not just “code”. Your constraints are a tool that helps you achieve your goal. For most others the constraints are limitations from achieving their goal. For me wearing a parachute is a constrain and carrying it is an act of will. For a skydiver not so much.
Again, my goal is "Ship working software", I don't care about optimizing at all, just baselevel "working" state of things, that's why I test things like reliability. But also again, our perspectives and understanding of terms seems to diverge a bunch, so much that discussing them seems relatively fruitless, at least seemingly to the two of us.