1. Validate the problem
2. Find to root cause by tailing logs or stack tracing
3. Reproduce the bug. This is known as Test Case in QA discipline
4. Memorize error codes such as:
403 - Forbidden or no access to files on this path
404 - URL is wrong
401 - Credentials are wrong
429 - Server is timing out due to being too busy
500 - Internal Server Error related to permissions
501 - Server doesn't understand your web client
502 - Bad gateway, check the proxy
503 - Service unavailable, check the worker processes
5. Google error codes
6. Get a second set of eyes. Often, when explain an issue to a colleague the organization of thoughts can create clarity within itself. Besides, nobody knows everything.
Categories:
