The section on managing tidying reminds me of the practice of 3Sing (sweep, sort, standardize) in lean manufacturing. A daily, 30 minute session before core work begins can really transform a workplace (codebase). Looking forward to all this!
Hi Kent, thanks for the writing. I'm trying to better understand tidyings and I have a question. Some years ago I learned a lot by reading Martin Fowler's book about refactoring. I think I remember you participated in this book where there was a list of refactorings. It explained where to use them and which steps to do to safely execute on them. Do you think there's any kind of connection between tydyings and refactorings? Is tydyings a lower scale refactoring? Do they share a goal on structure but at different levels of abstraction (object vs method)?
Great question. Here's the thing about "refactoring". It's gotten a bad reputation. "Refactoring, where progress goes to die." I'm resetting the conversation. Rather than talk about things geeks do to please the business in the long run, we'll talk about cute little fuzzy things geeks do to make their own lives better. Let's get used to that, to taking care of ourselves and each other. Once we've made tidying a habit we can re-approach refactoring at larger scales with a firmer grasp on the underlying principles & intended outcomes. Tidyings are baby refactorings.
First of all, thank you for all your contributions and great content you've been producing.
I've been following this newsletter for a while, and I recently came back to it. Now I am kinda lost, on where does it start and what sequence should I read it? Is there some kind of updated Table of Contents?
The section on managing tidying reminds me of the practice of 3Sing (sweep, sort, standardize) in lean manufacturing. A daily, 30 minute session before core work begins can really transform a workplace (codebase). Looking forward to all this!
Hi Kent, thanks for the writing. I'm trying to better understand tidyings and I have a question. Some years ago I learned a lot by reading Martin Fowler's book about refactoring. I think I remember you participated in this book where there was a list of refactorings. It explained where to use them and which steps to do to safely execute on them. Do you think there's any kind of connection between tydyings and refactorings? Is tydyings a lower scale refactoring? Do they share a goal on structure but at different levels of abstraction (object vs method)?
Great question. Here's the thing about "refactoring". It's gotten a bad reputation. "Refactoring, where progress goes to die." I'm resetting the conversation. Rather than talk about things geeks do to please the business in the long run, we'll talk about cute little fuzzy things geeks do to make their own lives better. Let's get used to that, to taking care of ourselves and each other. Once we've made tidying a habit we can re-approach refactoring at larger scales with a firmer grasp on the underlying principles & intended outcomes. Tidyings are baby refactorings.
Sounds awesome. Feels like it will be a great treat! 🎉🧹
Hi,
First of all, thank you for all your contributions and great content you've been producing.
I've been following this newsletter for a while, and I recently came back to it. Now I am kinda lost, on where does it start and what sequence should I read it? Is there some kind of updated Table of Contents?
Thank you,
I've never read them, so I don't know 🤪
I'd suggest reading them in posting order. If someone wants to suggest a better order I'll re-post it.