Hour of Code is an initiative put on by code.org to help introduce kids to computer science. When@ca55king approached the Weblinc team about a chance to work with Congresso to put on an Hour of Code for Computer Science Education Week, we all jumped at the opportunity to help local Latino kids write up their own website.
Even though it’s right in the name, sometimes we don’t fully realize that the Web is world wide. A platform enjoyed by millions of people of different languages. if you’re like me, you’ve gotten used what it means to make websites in your own language. But what of the other 230 languages? What does supporting a “world wide” audience mean for your website? Let’s review some of the “Ay, caramba” moments we might face when designing multilingual site.
Internationalization is the process of designing an application with the flexibility to adapt to any language or region. Developing for internationalization/localization (i18n/l10n) quickly illustrates how common front-end techniques prove to be problematic. How can we adapt techniques to serve the international user? In any language? And in any region? Let's examine how we can overcome these challenges and better serve the user.
It’s quite embarrassing when the bright spotlight of our peers' attention shines on our gaps of knowledge. Most of us quickly formulate a white lie to cover ourselves from this embarrassment. We work in a competitive and advancing industry after all; we need to prove our technical worth in hopes of maintaining our relevance as craftsmen.
At any given moment, vast amounts of personal data are being collected and stored across innumerable application databases. This data is owned and distributed by third parties, often without the user’s knowledge. The isolation of these third parties creates inconsistency in the way we as developers acquire information, frantically searching for the information we need using non-standardized APIs that may or may not be well documented.