video1.0<iframe src="https://www.loom.com/embed/576d954d6fb64c459391990db6420593" frameborder="0" width="773" height="580" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>580773Loomhttps://www.loom.com580773https://cdn.loom.com/sessions/thumbnails/576d954d6fb64c459391990db6420593-4ee6948b07618692.gif175.7This Loom shares the author’s experience learning the PyRevit challenge and how it improved their coding and tool robustness. They explain they already knew some Python and PyRevit tooling, but used it only on their own machine because others could break it. The challenges are described as practical, emphasizing planning, coding, and stress testing to fully understand the Revit API, with Eric Fritz highlighted as an especially down to earth teacher. They say the biggest accomplishment was learning a seven step code structure and adopting stress testing to avoid embarrassing errors when publishing tools to colleagues, and they also mention improving eye selection filtering.