[jasode]

Title says: "I Didn't Get Hired. Here's Why."

Body says: "Why didn't I get hired? I don't know why."

Real question to HN readers: Do you believe this type of inconsistency also affects writing code?

In other words... if a hiring manager notices this muddled writing in a blog post, is it fair to think the programming output will also be muddled? (e.g. function names, architecture, engineering the organization of microservices, code comments etc.?)

Or do you believe that the brain compartmentalizes and it's very easy to write disorganized prose simultaneously with organized code?

[GotAnyMegadeth]

The current HN title "I Didn't Get Hired to Google" makes it sound like someone quitting a job because it turned out their job was just googling things. Perhaps it should be "I Didn't Get Hired By Google".

PS or even better "I didn't get hired by Google".

[gvb]

PPS or even better "I didn't even get a Google phone screen."

[danmax]

As someone who has done a limited amount of hiring, I'm inclined to think that the inconsistency is something to be wary of. It's worrying to open the blog page and be able to simultaneously see titles reading both "I Didn't Get Hired. Here's Why" and "Why didn't I get hired? I don't know why". It leads me to believe that the author does not bother checking their own work, and/or has trouble articulating simple thoughts (ie. whether or not they know why they weren't hired, a yes or no question).

To your question - would this affect the author's code quality? Maybe, maybe not. They could be an absent-minded-professor-type who can easily do genius technical work, but misses things like this. However - Google looks for more than code quality.

[jps359]

It's just a typical click-baity title. I don't think it has anything to do with ability to write code.

[VLM]

Its just how journalism / clickbait is today. You want someone who writes docs to contemporary style.

I admit I do not look forward to the future when manpages will be titled "Top five sprintf format string length modifiers they don't want you to know; the last will shock you"

[minimaxir]

I do wonder what the parallel equivalent of headline clickbait in code is. Functions with very few LOC? :P

[philh]

    /* You won't believe the one weird trick this function uses to compute inverse square root */

[jasode]

>I do wonder what the parallel equivalent of headline clickbait in code is.

A common example would be business logic code polluting the "View" of MVC.

code reviewer: "Why are you retrieving the sales tax jurisdiction from the database and computing sales tax in the gui form?"

programmer: "Well, the form has the TOTAL amount displayed to the customer so it made sense to me to put that db-dependent code there."

code reviewer: "No, that's what the "Model" code is for. That's the "M" in "MVC".

programmer: "Oh, the model source code is where I update the GUI progress bar because that's where the state variable that keeps track rows processed is stored. "

[tyingq]

This one from Torvalds is close to clickbait, at least it made me want to find and read copy_page_range().

"Fork is rather simple, once you get the hang of it, but the memory management can be a bitch. See 'mm/memory.c': 'copy_page_range()'"

https://github.com/torvalds/linux/blob/master/kernel/fork.c#...

[euyyn]

I'd say functions and methods with overly generic names, like "process" or "prepare". You won't believe what happens inside!

[dTal]

Yes. I think the skill of writing down exactly what you mean is common to both code and prose - in particular, the kind of careful thought required to figure out what you're trying to say, well before you start working out how to say it.

[upatricck]

If the title was "Why didn't get hired? I don't know why". Most people including me wouldn't have bothered reading it. He's got journalism skills too