This week I need your help.
I want to grow this newsletter so that it becomes more and more useful to you, so I’d like to get your help in shaping the content.
I know that you, like me, are passionate about the internal quality of the software you create. And like me you’re frustrated that there’s very little practical advice out there to help with refactoring, and with test-driven development in general.
So how can I help? What do we, as a community, need this newsletter to provide?
I’ll put my own goals in the comments, and I’m looking forward to hearing from you too — what can I write about that will help you?
One final thing: Please also help to make this thread as useful as possible by sharing this post widely among people who share our need for better refactoring advice.
Thanks for your continuing support!
Here's a few of my thoughts...
I believe that what developers are missing most are:
What to improve:
Help identifying which code is likely to cause maintenance headaches in the future, and is therefore worth investing a little time in right now. This is the Implicit vs Explicit coupling theme.
How to improve:
Help and advice on how to make those improvements once the need has been identified. This probably has to consist of a mix of worked examples and recipes.
What do you think?