Ruby Video
Talks
Speakers
Events
Topics
Leaderboard
Sign in
Talks
Speakers
Events
Topics
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Keep Ruby Weird 2017- Lightning Talks by Various Speakers Amanda 0:00 Dave Rupert 7:22 Jordan Reuter 12:46 Nickolas Means 20:45
Date
Summary
Markdown supported
The video 'Lightning Talks' from the Keep Ruby Weird 2017 event features a series of quick presentations from various speakers discussing their experiences in coding and development. **Main Topic:** Each speaker shares valuable lessons learned through their unique journeys in the coding world, with an emphasis on personal growth and the challenges faced in programming. **Key Points Discussed:** - **Amanda Chang:** - Shared her transition from a theater major to a coding educator at a boot camp. - Discussed the courage required to be a beginner and how struggles foster growth. - Highlighted the positive impact of a beginner’s mindset on mental health. - Gave an example of a student club that enhanced learning through positivity. - Emphasized the importance of continuous learning and personal happiness in a coding career. - **Dave Rupert:** - Focused on the Ruby ecosystem's compatibility with Windows after his switch to the platform for a year. - Discussed challenges faced, such as gem compatibility issues and the impact of Microsoft’s enhancements for development on Windows. - Encouraged developers to explore compatibility solutions and highlighted the evolving nature of technology. - **Jordan Reuter:** - Introduced Elm as a functional programming alternative to JavaScript. - Described Elm’s architectural principles, emphasizing one-way data flow and reducing side effects. - Explained how Elm’s design can facilitate clearer and more predictable programming, reflecting a shift in modern development practices. - **Nickolas Means:** - Presented a case study on the Crofts Folly nuclear disaster to draw parallels with software development. - Discussed the importance of balancing pragmatism and idealism in engineering practices to avoid technical debt and disaster. - Concluded that the insights gleaned from historical errors can inform better decision-making in coding projects. **Conclusion and Takeaways:** - The talks collectively illustrate that learning to code involves both personal and technical challenges, and fostering a supportive environment can enhance this experience. - Understanding historical lessons in engineering can improve current practices in software development. - Emphasis on the importance of continuous learning and a positive mindset in the ever-evolving tech landscape.
Suggest modifications
Cancel