> My big peeve over the last few years is how often in software people want to talk answers before understanding the problem. My pet peve is people complaining

> My big peeve over the last few years is how often in software people want to talk answers before understanding the problem. My pet peve is people complaining about that. That you seem to think that's an issue shows how long it's been since the last time you really ventured out of your current comfort zone/domain knowledge. Trying to "understand" first means that you're just reading things for weeks or months if you barely know anything about a technology, domain and everything around it. That's a time period in which this less experienced person can gradually learn how the system, technology and domain works and they'll eventually graduate to prefer understanding over answers. Do keep in mind that these beginners can't distinguish between irrelevant and meaningful information, so they'd have to go through decades of documentation before they're able to "understand". Just give them a break and tell them the answer. After a while, (which you'll likely feel to be much too long) they'll grow a bigger knowledge base and will be able to meaningfully understand problems.