831 karma · joined October 26, 2009
Correct === Tradition + Lots 'o' Time
And Matt wasn't arguing this, but I have to link to Eric Lippert whenever I can so:
The idea programming language isn't 'correct' is kinda wonky. As I learned from Eric Lippert's [Three umpires](http://blogs.msdn.com/b/ericlippert/archive/2009/11/09/three...):
Three baseball umpires are having lunch together.
The first umpire says "Well, a lot of them are balls, and a lot of them are
strikes, but I always calls 'em as I sees 'em."
The second umpire says "Hmph. I calls 'em as they are."
The third umpire slowly looks at his two colleagues and declares "They ain't
nothin' until I calls 'em."
When a designed language is presented to you, you can't really argue about correctness, only suitability to a particular purpose or taste.If you use random UUID's (as opposed to sequential UUID's) for your primary key your database will spend an extra hunk of time on reordering your PK index on disk on insert. This bit us at Stackoverflow. So remember: just because you can do something doesn't mean you should.
I'd like to think that working on Stack Overflow's Careers service will help keep at least a few people from taking finance jobs like I did by providing them an alternative to needing to throw their lot in with a technical recruiter in a big city. Due to the economics of recruiting, recruiters tend to work with big finance (big salaries mean big commissions) instead of companies that y'know, make things but have lower salaries. I'd like to think we provide a slightly more level playing field to regular jobs (because we don't get paid on commission, therefore won't send applicants towards a finance position before all others).
"You can't change the world, but you can make a dent" - Sheldon Mopes
So if someone decides on using SO Reputation alone to qualify candidates, they can't effectively solve the primary problem of sourcing those candidates.
http://webapps.stackexchange.com/questions/1/how-do-i-delete...