5 ms·
I think bad refactorability is a weak-point of your code, not of the tooling. I used to think so too when I was doing Rails but since switching to static langu
by cageface 14y ago
I think bad refactorability is a weak-point of your code, not of the tooling.
I used to think so too when I was doing Rails but since switching to static languages for mobile development I've changed my thinking.
There's something a little bit magical about quickly renaming a function and knowing that every caller of that function has been instantly updated. It changes the way you write code. I'm constantly, aggressively refactoring when I write Obj-C or Java and my code is cleaner for it.
- Argorak 14y agoThats why I said mitigated: you are not going to make the problem go away, but you can lessen the impact. I have a similar workflow as you have in Ruby, but it takes great care to make sure that this kind of workflow is possible. Usually, I use a regexp and sign off every change by hand. Considering that I read my own code a lot, I also get to see my own stuff again. Thanks for catching this one.