Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Measure Twice, Cut Once by Alec Clarke "Woodworking and writing code go hand in hand, right? On the surface these two activities may seem different, but the skills, tools, and mindset required to create quality furniture are consistent with the qualities required to write code that delights both the customer and developer. As a woodworking hobbyist and software developer, I was amazed at how learning to build a table taught me to be a more impactful developer. In this talk we’ll discover how woodworking can teach us to move fast and not break things, be more consistent in our execution, and deliver lasting value to customers." __________ Alec is a software developer and woodworking enthusiast who works remotely from Kingston, Ontario for Clio where he focuses on creating an enjoyable and effortless experience between law firms and their clients.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video "Measure Twice, Cut Once" by Alec Clarke explores the parallels between woodworking and software development, illustrating how lessons from one discipline can enhance skills in the other. Alec, a senior software developer and woodworking enthusiast, shares his journey of learning to build a shaker table and the insights he gained, which can also be applicable to coding practices. **Key Points Discussed:** - **Safety First**: Just like safety precautions in woodworking are crucial to prevent accidents, preventative measures in coding, such as careful error handling and rollback plans, are essential for avoiding critical issues in software development. Alec emphasizes implementing safety mechanisms to mitigate risks when deploying new code. - **Solid Foundations**: Preparation of raw materials in woodworking mirrors the need for a stable codebase. Alec underscores the importance of refining code structure before implementing new changes. He uses the example of changing a material purchase method to show how preparing the code for new implementations can prevent bugs and errors. - **Quality Control**: The speaker explains the process of creating jigs for consistent and high-quality cuts in woodworking, paralleling this with the need for templates and generators in coding. He suggests using Rails' features to streamline the creation of maintenance jobs, ensuring quality while reducing overhead for developers. **Significant Examples:** - Alec relates his experience with the table saw, explaining tools to prevent mishaps and how this mindset can transfer to coding practices by managing risk during development. - The construction of the shaker table acts as a metaphor throughout the video, illustrating the methodical approach required in both woodworking and software development, reinforcing that careful planning, attention to detail, and consistent quality lead to successful outcomes. **Conclusions/Takeaways:** - Alec concludes that integrating a safety-first mindset, a solid foundational approach in code structuring, and ensuring quality control can significantly enhance a developer's impact. These strategies not only promote personal growth in woodworking but also cultivate effective coding practices that lead to better software development outcomes. He invites viewers to consider how skills in one area can enrich and improve capabilities in another, particularly emphasizing the ongoing influence of woodworking on his coding skills.
Suggest modifications
Cancel
