Read the error messages. Reread them. Extract every piece of information from them. Never close an error popup without having read and understood what it means. Always read stack traces when you're blessed enough to have them.
100% of the juniors (and an awful lot of seniors) I've ever trained simply ignore those and then come ask for help debugging.
99% of the time, the explanation for their problem is literally the first line of the stack trace/error message/whatever is red on their screen.
If you successfully adopt the mindset of "whatever the computer is telling is true from the computer point of view, so I'd better make sure I've read it" instead of "Anyway, I'll try something else and run again", you'll debug 10 times faster. And since debugging is a good part of the job, you'll be a lot more productive.
100% of the juniors (and an awful lot of seniors) I've ever trained simply ignore those and then come ask for help debugging.
99% of the time, the explanation for their problem is literally the first line of the stack trace/error message/whatever is red on their screen.
If you successfully adopt the mindset of "whatever the computer is telling is true from the computer point of view, so I'd better make sure I've read it" instead of "Anyway, I'll try something else and run again", you'll debug 10 times faster. And since debugging is a good part of the job, you'll be a lot more productive.