3 ms·
The problem with the "all engineers should internalise it into their development process" mindset is that it's held by so many groups. Your architecture should
by Vinnl 8y ago
The problem with the "all engineers should internalise it into their development process" mindset is that it's held by so many groups. Your architecture should take into account internationalisation, security, accessibility, etc.
At a certain point, no single engineer can keep up with it all, and produce working and maintainable code - let alone all of them.
Unfortunately, I'm not sure what the solution is here.
- TeMPOraL 8y agoI don't know what the ultimate solution is either, but it seems to me that internalizing more and more things into the development process is one of, if not the main part of growing as a developer. It's not even about being a specialist, just getting an intuition for design features that make it easier to implement i18n/l10n/a11y/security features correctly. And performance. For the love of all that is pretty, do remember to internalize how to write non-wasteful code.
- lumost 8y agoPart of growing as a developer is also knowing what you can do without, if you have 3 months to bring an mvp in front of a single language customer - i18n is the last thing on anyones mind, and delaying for even a day is a waste of precious time. This does not mean that time is the only thing that matters, if you know that at month 6 you're going to launch in spanish - then you better look to avoid major i18n pain points, and think ahead to ensure that between months 3 and 6 there is a viable project to internationalize the product.
- derefr 8y agoIf you’re in the US, maybe. If you’re building an MVP of a dating site for the European market? i18n is feature #0.
- goldfeld 8y agoMaybe an MVP for an European dating platform starts at the minimum of your mother language, or say, the French market? What good is having every language if your MVP marketing budget doesn't stretch enough to warm up the dating scenes of several countries? Better hit big by divide and conquer than try to hug the continent with your legs (to use a Portuguese expression.)
- Mirioron 8y agoEurope is more like 20 different markets than it is one big market though. Internationalization only matters if you're targeting all of those markets at once.
- the8472 8y agoHire more people or be prepared for long development times if you want all of the above. Restrict scope otherwise. Internationalization is not a must if a single-language market is large enough for you. Tacking it on later will be painful of course. The same with security and accessibility, not having it may be acceptable in some environments.
- yoz-y 8y agoHire more people _and_ be prepared for long development times. Some i18n parts can only be reliably done once the applications is practically done and will necessarily blow up the required time.