Suggest modification to this talk

Title

Description

RailsConf 2019 - Getting Unstuck: Strategies For Solving Difficult Problems by Steven Hicks

_______________________________________________________________________________________________

Cloud 66 - Pain Free Rails Deployments
Cloud 66 for Rails acts like your in-house DevOps team to build, deploy and maintain your Rails applications on any cloud or server.

Get $100 Cloud 66 Free Credits with the code: RailsConf-19
($100 Cloud 66 Free Credits, for the new user only, valid till 31st December 2019)

Link to the website: https://cloud66.com/rails?utm_source=-&utm_medium=-&utm_campaign=RailsConf19
Link to sign up: https://app.cloud66.com/users/sign_in?utm_source=-&utm_medium=-&utm_campaign=RailsConf19
_______________________________________________________________________________________________

Even with the simplest of problems, we can get stuck on code. It happens to engineers of all experience levels. This session will show you many strategies for getting unstuck.

We'll start by reframing the act of getting stuck as a positive. Then we'll talk about many strategies for identifying the problem and moving on. We'll discuss the psychology behind these strategies, and answer questions like "Why do my best ideas come to me in the shower?" Finally, we'll look at ways to harden yourself for the next time you get stuck.

Getting unstuck is a skill. This session will help you sharpen that skill, and prepare you for the next time you want to throw your keyboard out a window.

Date

Summarized using AI?

If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.

Show "Summarized using AI" badge on summary page

Summary

Markdown supported

In the video titled **"Getting Unstuck: Strategies For Solving Difficult Problems"** presented by Steven Hicks at RailsConf 2019, the speaker addresses the common challenges faced by developers when encountering difficult problems in coding, emphasizing that getting stuck is an inherent part of the engineering process. Hicks provides a variety of strategies designed to help developers reframe their mindset about getting stuck as part of their job.

### Key Points Discussed:
- **Mindset Shift**: Understand that feeling stuck is normal for all developers, regardless of experience level. Getting stuck is part of the job, emphasizing that solving problems is the primary responsibility of developers.
- **Explain the Problem**: Start by verbalizing the problem, either by writing it down or explaining it to someone else (even a rubber duck). This method allows you to articulate your thoughts and often leads to insights that help solve the issue.
- **Isolation Techniques**: Hicks advocates for isolating the problem by analyzing it, removing non-essential code, or using version control to identify when an issue arose. This can simplify complex issues into manageable parts.
- **Taking a Break**: One of the most effective strategies is to step away from the problem. Engaging in physical activities, taking a nap, or doing something unrelated can lead to a fresh perspective and unexpected insights through concepts like incubation and analogical problem-solving.
- **Conditioning for Future Challenges**: To prepare for future challenges, Hicks recommends learning new skills, regularly pairing with others for brainstorming sessions, and maintaining a positive mindset, for instance by keeping a journal of achievements.

### Examples and Illustrations:
- Hicks employs an anecdote about feeling good while helping colleagues get unstuck, portraying the camaraderie in development teams. He also mentions the “Protege effect,” illustrating how teaching others deepens your understanding of a topic.
- Programmers can benefit from keeping a record of their successes to build confidence and combat self-doubt when they face new challenges.

### Conclusions/Takeaways:
- Getting stuck is an integral part of programming, and learning to embrace it will lead to more effective problem resolution.
- The strategies shared, especially explaining problems, isolating issues, taking breaks, and cultivating a growth mindset, can significantly enhance a developer's problem-solving skills.
- Developers should actively train their minds to tackle future challenges by learning and collaborating, reinforcing that problem-solving is both a skill set and a mindset.

Ultimately, the session encourages developers to view challenges as opportunities for growth rather than setbacks, effectively turning frustration into productive learning experiences.

Cancel