When there's an error or exception, read the error and the stack trace thoroughly and figure out what it means even if it means googling. Lately I've noticed that younger generation doesn't really understand error messages even in the simplest cases and people end up in wild goose chases when the real reason was incorrect permissions or something really mundane.
It was ever thus. I suspect what’s happened is that lately you’ve become the older generation.
In 2012 I had a stack trace that I could read and eventually figure out what happened.
Nowadays it's async framework method calls upon async framework method calls and that is an improvement in the tooling, because it can now glue them together.
Next-gen frameworks are undoing that mess, but god help you if you use some third party library for e.g. state management.
Other times, perhaps frequently, the error message is actually telling you something important.
Many people get stuck in the second case thinking it's the first case.
> When there's an error or exception, read the error and the stack trace thoroughly and figure out what it means even if it means googling.
The infuriating part is when there is no attempt to parse the error and just fire off a screenshot in chat and expect someone to do the first part too...