He said that the test names were essentially comments, and “comments quickly become lies”. Which, fine, we’ve all seen bad comments. But the test names are more like file names than comments, and no sensible person is going to suggest we get rid of file and folder names. Except the other guy who responded to me with the shell scripts with no names that each call each other, maybe.
He was on a different team at a large company so I didn’t get wind of this right away. We had a meeting scheduled to hash it out, but then there were mass layoffs that day and I left shortly after. For all I know he’s still there
I had a boss who didn’t allow comments. “I like clean code,” was what he said. He also didn’t like variables with easy to understand names, like config_file_path because he said, “this is a real company, not kindergarten.”
What was his reasoning? Did you not do pairing and or pull requests?
He said that the test names were essentially comments, and “comments quickly become lies”. Which, fine, we’ve all seen bad comments. But the test names are more like file names than comments, and no sensible person is going to suggest we get rid of file and folder names. Except the other guy who responded to me with the shell scripts with no names that each call each other, maybe.
He was on a different team at a large company so I didn’t get wind of this right away. We had a meeting scheduled to hash it out, but then there were mass layoffs that day and I left shortly after. For all I know he’s still there
I had a boss who didn’t allow comments. “I like clean code,” was what he said. He also didn’t like variables with easy to understand names, like config_file_path because he said, “this is a real company, not kindergarten.”