How many scenarios are there where the rename both matters (beyond taste and philosophy) and is across interface boundaries?
Surely if it is an advantage to rename once in a ginormous, single code base there must also be leaky abstractions, poorly defined interfaces, god objects, etc present at the same time?
Whenever I find I need to rename anything across domains, it's a matter of updating the "core" repository and then just pulling the newest version.
Surely if it is an advantage to rename once in a ginormous, single code base there must also be leaky abstractions, poorly defined interfaces, god objects, etc present at the same time?
Whenever I find I need to rename anything across domains, it's a matter of updating the "core" repository and then just pulling the newest version.