DEV Community

Discussion on: What do you do when your stuck?

Collapse
 
andrewlucker profile image
Andrew Lucker

If you doubt yourself, keep working on it. If you doubt your tools, workaround it. Being able to place the blame is a learned skill.

If you continue with your chosen approach, but don't find a match on Google or Stack Overflow, then try narrowing down the scope of the problem until you can place the blame. Some people like debuggers for this, personally I like checkpointing print statements and logs. If the problem continues into a library, then go to the source.

Sometimes there is nothing you can do except workaround. There are compiler bugs. There are OS bugs. There are hardware bugs. These are exceptionally rare.

Much more common is your program or a library is corrupt. My personal peeve is double freed memory. It is really common in code or libraries and causes exceedingly strange failures.

Collapse
 
emmanuelobo profile image
Emmanuel Obogbaimhe

Thanks for the feedback Andrew, I agree with this approach. This issue happens to me mainly because of third party libraries. Which kinda sucks because sometimes its completely out of your control or hard to find which other dependency is causing the issue with that specific library.