If I have a story to complete during a sprint, and I spend an hour looking through the specifications and looking at the existing code and APIs etc., the compan

If I have a story to complete during a sprint, and I spend an hour looking through the specifications and looking at the existing code and APIs etc., the company would probably be worse off if I immediately began coding a solution. I have two weeks to do the work, so why rush it? The company will be better off if I implement a better solution. We're not flipping hamburgers or soldering widgets on an assembly line. We're constantly adding to systems that get increasingly complex over time. The UX that the product manager sees is just a small percentage of the work. Haste makes waste, and a stitch in time can save nine. There are times I have spent a day banging on some problem, and I am up to even 1 AM trying to fix it and I give up and go to sleep, after a few hours of hitting my head against a brick wall. I wake up in the morning relaxed, and am hit with an epiphany, I go to the computer to code it and it works. I don't know if I am dreaming up a solution while I sleep, or a couple of seconds of a clear head beats hours of tiredly banging my head against the wall, but it has happened more than once to me, and I have heard the same from others.