I feel for your situation, 'cos coding for me is actually more like 50% writing code and 50% daydreaming/browsing/whatever. Coding is a creative task.
Typically though I'll think of an excellent shortcut/solution after an hour of staring into space, and that shortcut saves about a days work. Problem is, how do I quantify that saving?
In the past I've spec'ed work to my boss on how long it would take to do a project the 'typical way' and got approval, and then it's just a matter of delivering it in less time than that. But if your boss can't estimate time to do tasks anyway, that's not going to help.
As a short term fix, you might want to take up smoking , or start drinking a lot of water, or something else that will let you get out of your chair for 5 minutes every hour.
Typically though I'll think of an excellent shortcut/solution after an hour of staring into space, and that shortcut saves about a days work. Problem is, how do I quantify that saving?
In the past I've spec'ed work to my boss on how long it would take to do a project the 'typical way' and got approval, and then it's just a matter of delivering it in less time than that. But if your boss can't estimate time to do tasks anyway, that's not going to help.
As a short term fix, you might want to take up smoking , or start drinking a lot of water, or something else that will let you get out of your chair for 5 minutes every hour.