3 ms·
If you want to create a good piece of software (let's say Photoshop) in English, create it in English. If you want to create a good Photoshop in German, create
by immibis 2y ago
If you want to create a good piece of software (let's say Photoshop) in English, create it in English. If you want to create a good Photoshop in German, create it again but in German. You can use the English one as a base, but treat it as a new product that happens to have a lot of code reuse, not a variant of English Photoshop.
Then, to reduce maintenance costs, you can fold the changes back in to the original software, using conditional statements and so on. This creates International Photoshop, of which English Photoshop, German Photoshop and Chinese Photoshop are just configuration options.
What you should not do is create International Photoshop first, and then specialize it for English and German and Chinese. You'll find places where the localizations don't fit into the framework you created, and then you'll either go back and change the framework, or (more likely) you'll just use English conventions in the non-English versions to make them fit the framework, and people in other countries will just live with with their language's equivalent of Engrish.
This is related to "a library must have 3 clients", "make a game not a game engine", etc, also "red green refactor". You have to make several specific things before you can generalize anything. If you don't make the concrete things first, you don't know what has to be generalized and how, and what doesn't. When you make the framework first, it has all the wrong generalization points.
Of course, if you already did this for a previous project so you already know how the framework should be, then you can try the framework-first approach. But beware - with that approach you might get stuck in the second system effect.
This comment has been delayed for hours by HN's rate limit.