Other times, using a few different keywords together, such as the language, library, OS, and function name can lead you to useful posts. Sometimes you can paste an error message into the Google search box, remove the ids specific to your environment, and get helpful results. There’s so much information out there, though, that the key is to find the right search terms to get a relevant answer. Google, Stack Overflow, and various public searchable forums can be great resources for finding the answer to a technical problem. It’s not intended to be a comprehensive list, so feel free to share techniques that have helped you in the comments. I hope it helps other developers spend less time being frustrated. This article pulls together and shares techniques that I’ve learned over the years for getting unstuck. As a senior engineer and consultant, part of my job is helping others to get unstuck. But you still just wasted days of your time and your project manager and teammates are annoyed at you for taking so long.Įveryone gets stuck sometimes.
Other times, it’s due to a bug in a library you’re using, so it’s not even your fault and all it took was upgrading to a new version. The fix itself is often simple, sometimes as little as a type-o or a missing semicolon. You’ve been pulling your hair out and cursing for three days, trying everything you can think of until you try that one thing that makes it work. 26 Ways to Get Unstuck in Software DevelopmentĪnyone who’s written software has been there: The code you’ve written looks correct, it should work and yet it doesn’t.
0 kommentar(er)
