meks.quest
I recently attended the Goatmire Elixir Conf and one of the standout talks for me was Saša Jurić's "Tell Me a Story". It was an incredible presentation that combined theatrical storytelling with practical technical advice. Saša performed parts of his talk in character, turning technical topics into a compelling narrative that was part comedy, part tragedy, and fully packed with useful insights I've started implementing myself. The recording will eventually be released online for viewing. I highly recommend that people watch it, and I'll endeavor to add a link to it here when it becomes available. The talk focused on Code Review and Pull Requests (PRs). Saša laid out common problems most software engineers face. Too often, engineers dread code reviews even though they're a significant part of team collaboration. We avoid them because PRs tend to be too large, too complex, too difficult to comprehend, and too painful to test. So we end up commenting "Looks Good To Me" and suggesting a fe
Photo Credit to Petter Boström I recently attended the Goatmire Elixir Conf and one of the standout talks for me was Saša Jurić’s “Tell Me a Story” . It was an incredible presentation that combined theatrical storytelling with practical technical advice. Saša performed parts of his talk in character, turning technical topics into a compelling narrative that was part comedy, part tragedy, and fully packed with useful insights I’ve started implementing myself. The recording will eventually be released online for viewing. I highly recommend that people watch it, and I’ll endeavor to add a link to
Explore this link on the map →related reading
- Writing commit messageschiark.greenend.org.uk
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- Conventional Commitsconventionalcommits.org
- Mistakes I see engineers making in their code reviewsseangoedecke.com
- How to Write a Git Commit Messagecbea.ms
- How to Do Code Reviews Like a Human (Part One) · mtlynch.iomtlynch.io
- How to Write Better Git Commit Messages – A Step-By-Step Guidefreecodecamp.org
- The comprehensive guide to writing the best PR title of all timegraphite.dev
- The ideal PR is 50 lines longgraphite.dev
- How to Make Your Code Reviewer Fall in Love with You · mtlynch.iomtlynch.io
- How to Do Code Reviews Like a Human (Part Two) · mtlynch.iomtlynch.io
- Semantic Commit Messages · GitHubgist.github.com