What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 134 Stack Exchange communities.

SO Careers does not allow the month of October to be spelled out in any date field (Oct works fine)

How could that possibly happen?

share|improve this question
18  
October knows what it did wrong! –  gnostradamus Mar 24 '10 at 20:31
2  
... Something about a revolution in October, once? –  Randolpho Mar 24 '10 at 20:33
10  
Jeff hates Sean Connery. Go ahead, try putting the word "Red" in there - it doesn't work either! –  Adam Davis Mar 24 '10 at 20:34
    
I'm sure the explanation will not be nearly as interesting as any cause I can imagine...or will it?!...no it won't :/ –  Michael Haren Mar 24 '10 at 21:06
5  
Oh, and did you notice October is the 10th month on the calendar, but according to its name "Oct," it should be the 8th!? If only Chacha102 could reveal more to us regarding this massive-coverup! –  Jonathan Sampson Mar 24 '10 at 21:10
7  
Why do programmers always get Halloween and Christmas confused? Because oct(31) == dec(25). –  Ether Mar 24 '10 at 21:33
3  
@Jonathan: blame the Romans, it's all their fault. October was named back before "January" and "February" were prepended to the year, so it was the 8th month. as Sept. was the 7th, Nov. the 9th, and Dec. the 10th. sadly no one remembers those old pre-Julian calendars: en.wikipedia.org/wiki/Roman_calendar en.wikipedia.org/wiki/September –  quack quixote Mar 24 '10 at 22:36

2 Answers 2

up vote 6 down vote accepted

Time Frames are... complex. This is (yet another) error resulting from tightening the data entry constraints on Time Frames .

Suffice to say that there (was) a point in the time frame parsing code where we split it into two different strings that can be converted directly into DateTimes.

This was accomplished with something roughly equivalents to:

Regex.Split(timeFrame, @"to|-");

The exact explanation of the error is left as an exercise to the reader.

We of course haven't written our own date parsing code, as down that path lies wailing and much gnashing of teeth.

share|improve this answer
    
LOL! That's pretty good. Thanks for checking into this! –  Adam Davis Mar 25 '10 at 0:03
5  
Note to self: add all full and partial months to date parsing unit test. –  C. Ross Mar 25 '10 at 0:22
2  
Why is it necessary to "tighten the data entry constraints"? –  Kyle Cronin Mar 25 '10 at 0:33
    
@Kyle - probably to make it easier to calculate length of employment. –  Adam Davis Mar 25 '10 at 0:41
    
It works now... –  SLaks Mar 25 '10 at 0:45
    
@Pollyanna But why is that necessary to do? Surely employers could determine that by reading the CV, and it seems like an odd thing to search by. –  Kyle Cronin Mar 25 '10 at 0:56
    
@Kyle Cronin - hResume is very stringent about date formatting, so in order to better support hResume export Time Frame data needed to be more readily parse-able. We still try and let you get away with a bunch of different formats, if only for convenience sake. –  Kevin Montrose Mar 25 '10 at 1:12
    
The time frame cannot hold, it is too late... –  Andrew Grimm Mar 25 '10 at 2:31
    
@kyle - I'm only guessing, I couldn't think of a good reason why an employer would need to search or know that detail either, but... @Kevin - Ah! That makes very good sense! –  Adam Davis Mar 25 '10 at 3:07
    
@Andrew - cthresume would like to have a word with you. –  Adam Davis Mar 25 '10 at 3:08

Confirmed:

alt text

I don't get a similar error with Oct 2005-2007

I'm thinking someone misspelled October in the date checking code. I should win a Pony if I'm right.

Also, the Red October conspiracy (as noted in the question comments) seems to be more likely given the color of the error box, and the month that causes the error.

Crazy Ivan indeed.

share|improve this answer
    
My bets are on Octber. –  snicker Mar 24 '10 at 23:26
    
fest. everyone forgets the fest in Octoberfest. it's not a month, it's a beer-drinking excuse! –  quack quixote Mar 24 '10 at 23:32
    
@snicker - nope. I've tried that and a few other spelling variations and they all have the same rejected result. I'm really curious as to what it is now... –  Adam Davis Mar 24 '10 at 23:34

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .