PS or even better "I didn't get hired by Google".
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.
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"
/* You won't believe the one weird trick this function uses to compute inverse square root */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. "
"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#...
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?