When I was young, one of my mentors said "half of engineering is knowing the vocabulary". The older I get, the more I'm convinced he's right. The names of part

When I was young, one of my mentors said "half of engineering is knowing the vocabulary". The older I get, the more I'm convinced he's right. The names of parts helps give some amount of context and purpose to why a thing was done, what it's role is, etc. This gives a much quicker comprehension to the thing you're trying to understand - consider someone handing you a codebase you've never seen, and a vague description of what it does. Is it easier to understand with well named functions, variables and types? What if the all function names were replaced with f1, f2, ... fn, and variable names were replaced with v1, v2, ... vn, and so on? What if it wasn't a complete codebase, but only part of it, and had gone through a bit of a scramble (the Carthaginian ship in question had been wrecked as I understand it)? What if you were a brand new programmer (Rome was new to the whole ship thing then...)? You're absolutely right that it's not strictly necessary to have the labels for reverse engineering, but the labels certainly help... for context it was 8 years from the start of the war until the battle in question, and the fleet was built in just 4 years. At that rate, I find the label thing a plausible contributing factor.