[RHSeeger]

I'm inclined to believe it's less about the time required to code specific feature... and more about the time required to

1. Figure out what features should be implemented (ie, will implementing this feature shoot us in the foot later)

2. Figure out the correct implementation

3. Be able to handle future feature requests

Sure, 1 & 2 will vary by skill/experience. However, the skill/experience with which 1 & 2 are handled can severely impact 3, causing it to easily take 10x longer if it can be done at all. As you move onto 4 and down the line, this becomes more and more pronounced.