All geek questions in one place

How to deal with changing the names of functions and products in the source code?

What is a good strategy for working with changing the names of products and functions in the source code. Here's the situation I'm in over and over again (most of you can tell?) ...

  • Product name starts as "DaBomb"
  • Key features: Exploder, Lantern, and Flag.
  • Time passes, and the function names change to "Boom", "Lighthouse" and "MarkMan".
  • Time passes and the product name changes to "DaChronic"
  • ...
  • ...
  • Blah, blah, blah ... over and over

And now we have a large code base with 50 different names scattered across the directory tree and source files, most of which are outdated. Only veterans remember what each name means, a complete etymological history, etc.

What is the solution to this problem?

Explanation: I do not mean the names that customers see, I mean the names of directories, source files, classes, variables, etc. that developers see where the names of products and functions are woven into.

+3
source share
6 answers

, " , , [] , , , .., ", , .

, , , . , , . , . , 2 - : ", , , .

/ , , , " ", , .

+6

. , , unit/integration, commit, merge, repeat. , .

+4

, . , , . "Exploder" "Boom", : Exploder Boom , Exploder to Boom, Boom Exploder.

Exploder, Boom , .

, , , , , , , , /, , . Exploder TNT, , Exploder Boom?

+4

? ; .

0

. , ,

public static final String EXPLODER = "Boom";

EXPLODER. .. - . (, JS ini - ), , Exploder?

0

Source: https://habr.com/ru/post/1719412/

More articles:


All Articles