Continuous Delivery and Continuous Self-Improvement

Remote Ruby

In this episode, Jason, Chris, and Andrew reflect of their experiences of developing software, focusing on aspects such as the Fast and Furious franchise, writing in Ruby, React development, and grappling with OAuth 2.0 issues.
They dive into testing, specifically the challenges of maintaining a meaningful test suite and the revelations from addressing test suite problems.
A discussion on containerization touches on Docker and CI setup frustrations, while also exploring web accessibility standards and the potential of Web Components, specifically through the new Web Awesome project.
The conversation takes us through various technical and personal insights, highlighting the continual learning and adaptation inherent in software development. Press download to hear much more!
Panelists:
Jason Charnes
Chris Oliver
Andrew Mason
Links:

• Jason Charnes X/Twitter
• Chris Oliver X/Twitter
• Andrew Mason X/Twitter
• Once a Maintainer: Rafael França
• OrbStack
• Lob
• Ahoy.js
• Font Awesome
• Shoelace
• Kickstarter for Web Awesome by Font Awesome
• Ruby for All Podcast

• Jason Charnes X/Twitter
• Chris Oliver X/Twitter
• Andrew Mason X/Twitter

Kapitel

1. Continuous Delivery and Continuous Self-Improvement (00:00:00)

2. Andrew talks about his transition from writing React back to Ruby and his interactions with a coworker who helped him improve his JavaScript and React skills. (00:01:05)

3. We hear about Andrew’s frustrations with understanding OAuth and using OmniAuth gems without tests, humorously suggesting an alternative authentication method involving driver’s licenses. (00:02:44)

4. Jason discusses his experiences and concerns with handling personal data and API keys, emphasizing the need for secure and manageable systems. (00:03:52)

5. The guys extensively discuss the challenges and strategies related to testing software, including continuous integration (CI), the impact of test suites on development, and different approaches to running tests. (00:05:36)

6. Chris expresses his frustration with Docker, particularly with debugging issues related to user permissions and Dockerfile configurations. (00:14:43)

7. Chris mentions recent fixes to Ruby and compatibility issues with Docker on Intel Macs, particularly problems with Node and Tailwind causing segmentations faults. (00:16:02)

8. Jason discusses his preference for running tests locally due to the simplicity and speed, despite the growing size of his codebase. (00:17:09)

9. Chris explains his work on automating Ruby gem publishing with GitHub actions using OAuth for secure, immediate updates. (00:18:02)

10. Chris touches on the benefits of reproducible builds, which help ensure that software remains consistent and secure across different environments. (00:19:52)

11. Andrew shares his thoughts about OrbStack and having issues with Docker working locally, and mentions containerization is a great pattern and he loves it. (00:22:23)

12. Jason shares something he wants to do for pagination. Chris proposes “reverse attacking” as a novel method to deal with cyber-attacks. (00:25:03)

13. Jason discusses using Ahoy to track visits and events in his Rails apps and explores adding geocoding to those requests. (00:29:19)

14. Jason elaborates on the complexities of handling different types of domain configurations directing to his service. He’s aiming to consolidate these to simplify management and improve security. (00:32:57)

15. Chris and Jason discuss updates in Ruby on Rails, focusing on new features, upcoming releases, and the integration of modern web technologies like Hotwire and Tailwind. (00:38:01)

16. Chris discusses the challenges of working with Hotwire, noting that it lacks a regular update cadence compared to Rails. (00:40:22)

17. Jason brings up a comparison of site accessibility, noting that React scored highly due to its robust component system, whereas Rails scored lower. (00:43:45)

18. Chris expresses enthusiasm for the integration of web components into Rails applications, hoping they will bridge accessibility gaps without needing to rely solely on React. (00:45:16)