Planning a code walkthrough
Finding what’s helpful in doing so
Synthesising what I have learned through small experiments and projects
Making do with a heatwave leading to some school closures locally
Newsletter WoR #63: quitter son job au bout d'une semaine ?, le crash de Google, le bingo des dév front-end..., Women on Rails
Take-home vs whiteboard coding: The problem is bad interviews, Andrew Rondeau
The Day That Git Saved My Life, Nadia Odunayo
Why I Write My Tests First, Elise Shaffer
Strong Engineering Cultures, Stacy Devino
Paul Sesay: The dangers of tokenism, Paul Sesay
Lessons Learned from Ruby on Rails Projects: Common Challenges & Fixes, Patryk Gramatowski
Quand les IA font des rapprochements trompeurs, Pierre-Emmanuel Arduin & Myriam Merad
Nadia chats with... Sarah Mei (Brighton Ruby 2019)
RubyConf 2016 - Lightning Talks by Various Presenters
In large, divided teams, comprehensive documentation ensures that all team members, regardless of their unit, can understand the project's structure, logic, and goals. We adopted clear API documentation and internal wikis to bridge knowledge gaps and support smooth onboarding for new developers. — Patryk Gramatowski
The End of Fun, Sarah Mei
Five Things to Avoid in Ruby, Martin Streicher