> Haha, wait until you hear how long and how many people it takes to change the text for a single button at a company like Google
I feel this is a needlessly obtuse statement. I'll explain you why, as I've worked professionally with frontend development. From your comment it seems you don't have that type of context.
The text that is expected to feature in a UI element is a critical factor in cross cutting concerns such as product management and UX design, and it involves things like internationalization and accessibility support. This means that if you change a line of text, it needs to be translated to all supported languages, and the translation needs to meet usability and GUI requirements. This check needs to be done in each and every single locale supported.
I can give you a very concrete example. Once I was tasked with changing a single line of text in a button featured in a dialog. It turns out the french translation ended up being too long that forced line breaks. The UI framework didn't handled those line breaks well and reflowed the whole UI, causing a huge mess. This required new translation requests, but it turned out that the new translations were too vague and ambiguous. Product Managers got involved because the french translation resulted in poor user experience. Ultimately the whole dialog was redesigned.
But to you it's just a text on a single button, isn't it?
I think the problem is the detachment of a developer from what is being done. Many developers want to treat coding like a crative work, while corporations try to make it an automatic job that turns tickets into code. The fact that the person working on a dialog isn't aware that there are translations where things might force a different layout is a proof of a broken system.
I'm not saying that developer should also be UI specialist, that's nonsense. But a developer should know who to talk to regarding advice, and the contact should be easy. The model where a dev doesn't even know that French translation exists is wrong. The correct model is having a dev think "wait, this might affect translation, better send a Slack message to some UI guy and let him know".
Actually, what I said is a pipe dream. The reality is, most devs are average devs, and companies need to optimize processes for that. This results in very official communication that takes years to get anything done, because you can't trust average developer that they'll contact the UI guy. This leads to a lot of frustration from above-average developers, who simply need a different environment to shine (more freedom but also more responsibility)
I feel this is a needlessly obtuse statement. I'll explain you why, as I've worked professionally with frontend development. From your comment it seems you don't have that type of context.
The text that is expected to feature in a UI element is a critical factor in cross cutting concerns such as product management and UX design, and it involves things like internationalization and accessibility support. This means that if you change a line of text, it needs to be translated to all supported languages, and the translation needs to meet usability and GUI requirements. This check needs to be done in each and every single locale supported.
I can give you a very concrete example. Once I was tasked with changing a single line of text in a button featured in a dialog. It turns out the french translation ended up being too long that forced line breaks. The UI framework didn't handled those line breaks well and reflowed the whole UI, causing a huge mess. This required new translation requests, but it turned out that the new translations were too vague and ambiguous. Product Managers got involved because the french translation resulted in poor user experience. Ultimately the whole dialog was redesigned.
But to you it's just a text on a single button, isn't it?