3 ms·
> first read the error message clearly and try understand it, Derail, but this right here is the key to debugging superpowers. I can't even count the number of
by bgribble 3y ago
> first read the error message clearly and try understand it,
Derail, but this right here is the key to debugging superpowers. I can't even count the number of times I have amazed juniors with my genius when all I did is read them the error message and ask them under what circumstances could that be true.
A corollary that's just as important is "believe the error messages - they are telling you the literal truth." Hard to believe how often we implicitly disbelieve what the compiler or runtime is telling us.
- lsaferite 3y agoI know this and do this, but I would add, make sure you _actually_ read the error message and don't _think_ you read it. This bit me just yesterday as I was encountering an issue and spent a good 30 minutes trying to solve a problem I thought I'd been having. When I re-read the error message it was clear that I'd been too careless and not fully understood the issue. It happens from time to time and then I'm more cautious for a while until I get _just_ complacent enough to have it happen again.