News for hackers. Stuff that matters.
Re:Thinking of applying for a job at Google. Any tips or fee... by aaronbrethorst on Thursday January 07, 2010 @08:55PM (#1038560)
500,000 lines of Python and SQL?
Re:Thinking of applying for a job at Google. Any tips or fee... by benhoyt on Thursday January 07, 2010 @09:07PM (#1038586)
Oh dear! Good catch, that's embarrassing. I did a recursive "wc" but then read the wrong column. It's only 21,000 lines. :-| Fixed now: at 21kLOC, is it still a figure worth including?
Re:Thinking of applying for a job at Google. Any tips or fee... by Imprecate on Thursday January 07, 2010 @09:52PM (#1038692)
I don't really think so. You're really trying to measure the scale of your work. Better metrics would be what specifications you implemented, features you added, scalability (# of users or servers). You wrote 21k lines of code, but code wasn't your end result. That code did something beyond getting piped into wc, I hope. :)
Re:Thinking of applying for a job at Google. Any tips or fee... by gprisament on Thursday January 07, 2010 @09:03PM (#1038578)
I was thinking the same thing. I'd consider removing the "500 kLOC" line. Makes me suspect your code is verbose rather than elegant.
Re:Thinking of applying for a job at Google. Any tips or fee... by cmars232 on Thursday January 07, 2010 @09:21PM (#1038617)
Yeah, only quote LOC if its someone else's mess you cleaned up :)
Re:Thinking of applying for a job at Google. Any tips or fee... by lsb on Thursday January 07, 2010 @11:51PM (#1038892)
And then he discovered the LOOP statement!