What is your take on refactoring without changing behaviour? A concrete example would help explain the choice. What would you capture before touching the old function? Developers, please describe the environment and the smallest example that shows the problem. What would you check first, and what result would change your next step? Keep passwords, tokens and other private values out of any code you share. What is the one thing you would want clarified before deciding?
Bintroom Forum
Registered members: 1 · 1,244 topics. Date: Saturday, 14 November 2026 at 09:53 am
Programming
Refactoring without changing behaviour: What would you capture before touching the old function?
Refactoring without changing behaviour: What would you capture before touching the old function?
Share Likes: 0