I still prefer the one the right. I'm able to skip entire sections of code, and assume what the function does. Only if I require details do I go deeper.
The comments are metadata, and where function names are tied into the code. One is going to stay up to date. The other isn't.
People on HN have this weird distinction where if your an engineer you stay an engineer. In the real world, most career structures involve coming in a engineer and then progressing into management. A lot the skills used for management such as negation skills just come with age anyway.
I respectfully disagree. I believe that knowing when and how to say "no" is one of the most important management skills, and I suspect that understanding the need to say "no" a lot more than "yes" in the early days of a project (or a whole business) is quite strongly correlated with success.
I think he meant to type "negotiation" rather than "negation", which makes little sense even if he was trying to convey the point you just made. So I was making a little fun of that. I agree with you.
What makes you think mangers don't suffer from the same thing. Managers are also highly educated often more so(MBAs etc) etc except they will be trying to employ fancy management rather than fancy algorithms.
So you entire premise is wrong.