Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
After a stressful couple of days at work, Deirdre Bug is looking forward to a quiet evening in. But her plans are thwarted when the phone rings. “I know I’m the last person you want to hear from…but...I need your help!” Follow Deirdre as she embarks on an adventure that features a looming Demo Day with serious prize money up for grabs, a trip inside the walls of one of the Ruby community’s most revered institutions, and some broken code that appears to be much more simple than meets the eye.
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 keynote titled **"The Case Of The Vanished Variable - A Ruby Mystery Story"**, Nadia Odunayo, CEO of The StoryGraph, dives into a fictional mystery intertwined with Ruby programming challenges. The narrative follows Deirdre Buck, a private investigator for Ruby-related mysteries, as she is pulled into a high-stakes scenario involving the Ruby Institute of Professionals (RIP) and a coding error that jeopardizes a significant competition. Deirdre receives a call from a Ruby developer, Jenny, who explains that her team's automated grant assignment application malfunctioned, resulting in an incorrect number of grants awarded. With only hours until the competition's decisive moment, Deirdre reluctantly agrees to help. Throughout the case, key points include: - **The Setup:** Deirdre's background as a solo developer and investigator of Ruby crimes showcases her dual roles in the tech community. - **The Conflict:** Jenny's team is on the brink of disqualification due to a coding error that awarded 300 grants instead of the maximum capped at 100. - **Investigation Process:** Deirdre unravels the issue by working alongside the lead developer, Alex. They explore the code which reveals critical mismanagement of class instance variables that caused the bug. - **Resolution Discovery:** Deirdre's strategic thinking leads to a simplified conclusion that the persistent class instance variable was incorrectly overwritten due to careless code editing, ultimately marking the origin of the bug. - **Team Dynamics:** The story also highlights interpersonal conflicts as Deirdre navigates Alex's reluctance to accept help, reminiscent of common challenges in tech teams. Through this engaging narrative, the audience gains insights into debugging practices, teamwork in coding projects, and the importance of clear communication in development environments. Nadia's story emphasizes that coding obstacles are often less about complex issues and more about understanding code interactions. The main takeaway is that with collaboration, clarity, and communication, even the trickiest problems can be solved.
Suggest modifications
Cancel
