How long does it take you to program?

Not unless we are in a meeting, or taking a phone call that is via software on the computer. We have personal phones so we typically do not need headphones/headsets

Wow, pretty sure it's been proven to increase productivity in tasks that require great focus. 
Maybe slip in an earbud and ask for forgiveness later 

The rules here are quite odd honestly, and I completely agree that it increases productivity. Apparently there were issues in the past with previous employees that ruined it for everyone. I would love to, though.

Technically, that is the rule where I work.  The rule was originally meant for just the shop floor, for safety purposes, but it was applied across the company to keep things fair.  They were really strict about it when I started 5 years ago, but slowly over time they have become more lax about it. 

At first, some people like me would keep one small earbud in one ear and just try not to be obvious about it.  Some people on the shop floor would try to inconspicuously wear Bluetooth hearing protection earmuffs - I don't think they were fooling anyone, but it slid past the radar.  Little by little people got more bold about it.  Now, there are people walking around with earbuds all the time as if the rule doesn't exist. 

I'm a little concerned that they will put the smack down on that sometime soon.  I sure hope not.  I enjoy listening to podcasts and audiobooks when working on tedious stuff. 

Okay, this thread has inspired me to trace all my programming times along with the amount of features and characteristics to gather hard data.

If only we could just be treated like responsible adults... In the machine shop they mostly stuck to the one earbud, one earplug rule. However, if the boss walked up behind you, and you couldn't hear him speak in a normal voice it was a problem. 

There was an excel sheet I found from some other programmers a long time ago that gave a rough estimate on how long it would take to program the part. I have not used this spreadsheet in a while, so I am not sure how accurate it is to prove out the programming. It might encompass all of it. But here is the snapshot on your part.

Dual program with 2 parts, each has about 30 geometric tolerances (i use GeoTol only). Each part has own jig with datums and with 3 position bushings. First I have to measure all datums according to brushings. Then I transfer these datums as generic features and use only 3 brushings alignment. These jig programs are separated as Sub programs. In main program you can choose if you want measure both parts, left only or right only. You can choose if you want to remeasure jig positions or if you want to calibrate probe. Program has 2 separate reports with different header and partname. All position pins used during clamping parts into jigs have collision checks (many times operators left pins inside = big crash) so now i cannot happen. Jig sub programs also has clamp check if it's fully open during remeasuring in arease where collisions can occur. All features have relatives to other features to avoid colisions when parts have different conditions. Everything must run perfect without any issues because these programs are for operators using Inspect. They just fix jig and clamp parts. Everyting is fully automated. With PDF report there is also custom excel report and csv coordintes for customer. So program like this take me about 2 full days and 1 day of testing at least. so full duration 3 and more days.

I used to do quoting for a 3rd party metrology lab. We would always assign 2 minutes per dimension (regardless of if a feature could be used for multiple dimensions) for our quote. Unless there were complex dimensions that we noticed ahead of time. So for this theoretical part for setup, program and proving out the program I would say about 6 hours. And honestly using this method tends to be pretty spot on most of the time..... usually I would be done an hour or two before my quoted time. The extra time was used during any problem solving and data review.

Now run time is a different story..... That's the one thing I always sucked at calculating. Depending on if its a PPAP or a capability study it could be days of running non stop.

Wow, that's not much time. A 150 dimension probably would take me a minimum of a full 8 hour shift. And then another few hours to prove out the program (run it through, watch all the hit points, and take some manual measurements to verify accuracy as needed). However, sometimes I have other tasks at work and people inturruputing me.