I think some of these questions are closed too quickly; especially when closed as too localized. In many cases a reformulated question would be helpful to future visitors. For example: http://programmers.stackexchange.com/questions/20289/mid-level-it-lead could be reformulated as 'What do you do when you get limited learning opportunities in your job'.

Closing a question is negative feedback to a user, and I think it should be avoided when possible. If it's not a real question, but just to vent, sure close it as non constructive. When it's a duplicate, close it; at least you're giving the user a place to find his/her answer. But with too localized you're closing the door to someone seeking help. If you can instead nudge the user into reformulating the question to make it more useful to other users everybody wins.

I think some of these questions are closed too quickly; especially when closed as too localized. In many cases a reformulated question would be helpful to future visitors. For example: https://softwareengineering.stackexchange.com/questions/20289/mid-level-it-lead could be reformulated as 'What do you do when you get limited learning opportunities in your job'.

Closing a question is negative feedback to a user, and I think it should be avoided when possible. If it's not a real question, but just to vent, sure close it as non constructive. When it's a duplicate, close it; at least you're giving the user a place to find his/her answer. But with too localized you're closing the door to someone seeking help. If you can instead nudge the user into reformulating the question to make it more useful to other users everybody wins.