Sometimes, problems arise that appear to be resistant to being solved. A number of various quick solutions are attempted to no avail. Even after researching the problem and gathering different approaches to the problem, one remains blocked from making any progress. As a programmer, this is one of the most frustrating situations. When all options seem to be closed, what is the next step?
After exploring all the apparent self-reliant avenues, the last resort is to ask for help. Multiple methodologies find this experience sharing important enough to build in opportunities for it, such as daily stand ups for AGILE development. Most organizations have now realized the importance of pairing junior developers with more senior team members early in their career to help them adjust.
Facing Humility
This step is especially humbling for me as someone who enjoys figuring out problems independently. In a position where there is no defined “go-to” person, I’m hesitant to make an internet post due to the lack of personal connection and trust. Additionally, how do I know which forum is appropriate to post in? These combined factors present a mental blocker for overcoming technical roadblocks.
For example, I’m having a difficult time envisioning the orchestration of AWS components to enable user authentication in the AWS ecosystem. I’ve consumed pages and pages of AWS official documentation, various how-to guides for related but different AWS environments, and numerous StackOverflow exchanges to no avail. Where would be the best place to ask questions about my configurations? Who do I go to?
Keep Moving Forward
The reality of the situation is that no progress will be made if I do nothing. The solution is one I do not want to face. I need to swallow my pride, and start asking questions somewhere at the risk of a small roadblock turning into a unscalable mountain. Even if I start in the wrong location, eventually I will get to an answer. The question is do I start with StackOverflow? An AWS sub-reddit? Decisions, decisions…
