When you open a file that you haven’t looked at in in a month, can you understand it in 30 seconds? Naming as a Process (NaaP) is a technique to get you there. Join Arlo’s whiskey talk this month on how you can start practicing NaaP today!
If you are reading this blog, you are probably a champion of tackling legacy code on your team. You may have already read Arlo’s Naming as a Process blog series from 2015 (reworked in 2019). But information doesn’t get you to practice.
At Deep Roots, we coach teams in adopting legacy code practices, including NaaP, but wouldn’t some teaching Cliff Notes be handy? Download this step-by-step tutorial for applying NaaP in your own practice.
While this tutorial will tell you what to adopt and when, it won’t predict or address the obstacles. The coaching is what solves the real world problems so that you end up doing it in your code as part of your daily work.
To that end, we have only 7 days remaining to register our first public class dedicated to Naming as a Process! Use the coupon code newsletter and get 25% discount.
Meanwhile, Marian presented Naming as a Process through the lens of refactoring a contract at Craft 2022 in early June. We encourage you to enjoy 20m of seeing how refactoring is a universally iterative gift, not to mention a bridge to explaining how refactoring code can be safely done to your product owners!
Create your profile
Only paid subscribers can comment on this post
Check your email
For your security, we need to re-authenticate you.
Click the link we sent to , or click here to sign in.