Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
The basic premise is that we should be spending significantly more time thinking than we do programming and there are wide reaching ramifications to this point. Subtleties in how our non programming coworkers perceive some of us wandering around the office pacing or arguing at the white board are all to be covered as well as discussing the body of research that supports the ideas behind thinking more and working less. Help us caption & translate this video! http://amara.org/v/FGbU/
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 presentation "Think Twice, Code Once" by Bill Chapman at MountainWest RubyConf 2013, the speaker emphasizes the importance of dedicating more time to thinking rather than simply coding. He introduces the idea that effective problem-solving in software development requires a shift in mindset, where programmers must understand the value of thoughtful contemplation in addition to active coding. Chapman discusses various thought processes and cognitive models to argue that most individuals remain stuck in the 'advanced beginner' phase of problem-solving, often overlooking the depth of thought required to excel at software development. Key points include: - **Cognitive Awareness**: Chapman highlights that productivity is affected by how much time is dedicated to thinking, rather than just coding. He references the Dreyfus model of skill acquisition and the Dunning-Kruger effect, asserting that most developers may not realize their limitations in expertise. - **Miscommunication in Work Environments**: He points out that programmers often encounter misunderstandings with non-programming colleagues about their work processes, including time spent away from the computer as an essential thinking activity. - **Examples of Programmers**: - **The Freshman**: Typically inexperienced programmers who fail to think through problems, producing code that may pass tests but lacks depth. - **Mrs. Roberts**: Developers who patch problems without understanding the larger context, leading to repeating the same mistakes. - **Bob Ross Fan**: Coders who create layers upon layers that obfuscate actual functionality due to an intuitive approach rather than structured thinking. - **The Mercenary**: Those who work for profit without genuine investment in their craft, often producing mediocre results. - **Pointy-Haired Boss**: Managers who focus on quantifying productivity without understanding the complexities of the thought processes behind programming. - **Research Insights**: Chapman cites studies showing the importance of cognitive breaks and varied work environments to foster higher productivity and creativity, emphasizing that maintaining mental agility is as crucial as technical expertise. - **Practical Takeaways**: He encourages developers to evaluate their environments and approaches to problem-solving, suggesting they stop overcommitting, understand their mental states, and allow breaks to foster organic idea development. In conclusion, Chapman asserts that developers are indeed professional thinkers and must prioritize thoughtful consideration over hasty coding to enhance effectiveness and innovation in software development.
Suggest modifications
Cancel
