Nothing here yet.
Nothing here yet.
No blogs yet.
I don't see an issue with it, provided everyone is comfortable with the level it's at. Personally, I think the corporate concept of "professionalism" is a large part of the problem with corporate culture. It's turned offices into stuffy, boring places where it's almost dangerous to have fun. And don't get me started on devs who will literally never be seen by clients/users wearing "business casual"... I will caveat, however, that shipping code on the web with such comments could cause your application to break on some users' machines if they're behind a content filter, as the filter could see the contents of the comment as something it needs to block.
Any dev who says they aren't searching for answers is a damn liar. The difference comes in how you're using search to figure things out. If you're just shotgun searching every problem, it's likely because you don't have a clear idea of what you need to do to get from A to B. What separates the children from the adults is the ability to break down the problem and then use the available tools to solve it. When you do this, you'll find yourself more often looking at actual documentation to solve problems. If this can't get you there, then we go for the question cannon.
A month or so ago, I was trying to split a string, but no matter what that string had in it, the split method just returned undefined. I spent 2 hours trying to figure out why I couldn't get it to work. I finally posted on a Slack team asking why it wasn't working. Turns out, I was using square brackets instead of parentheses for no discernible reason. It was pretty embarrassing, especially considering how long I've been writing JS.