|
|
|
many a times i have gotten an error while either compiling some program or while running some command/script and i immediately start looking at the man page and/or stare at the error in an attempt to understand what's going on. i consider this first-aid and it's usually enough to fix the problem.
but when it's not, it takes me a long time to realize that i should google the error message. googling provides more context around the problem, after a few minutes of reading on the web, we have a list of possible things causing the error which we can go over one at a time.
you usually find the solution in those discussions or hints to the solution. but if you can't figure out whats wrong, then asking your mentors and colleagues or other fellow hackers on irc is the next best step to get a quick solution.
if you don't find any reasonable solution, opening a ticket/issue to ask the project's devs is the only option you have, maybe ask the ai if it knows anything about it.
