This week we're joined by internationalisation (i18n) expert Eli Schutze. Originally from Nicaragua, Eli is a London-based web engineer and speaker currently making money work for everyone at Monzo Bank. In this episode she clears up some common misconceptions around the issue of translating apps and websites. It turns out that doing i18n properly often runs counter to a lot of the principles developers are taught when they learn programming.
Why do we call it "i18n"? (Spoiler: because it's hard to say!) And why do developers need to do the hard work of i18n themselves? Why not just use automated tools? How does i18n work on a technical level, and what is likely to go horribly wrong when developers try to be too "smart"? Find out all this and more in this week's international instalment of A Question of Code.
Mentioned in this episode:
⚡️ How much time do you spending coding in a coding job?
⚡️ How long should you spend on a take home coding challenge?
⚡️ Tabs or spaces?
30: What do you get from going to a tech meetup?
29: What's wrong with developer culture?
28: How do you stay motivated?
27: How do you deal with crazy bugs?
26: What is functional programming?
25: Do you need to be good at maths to become a programmer?
24: Should you write about what you've learnt?
23: How do you write a good CV?
22: Why should you write tests?
⚡️ What does it mean to be a full stack developer?
⚡️ How closely should you match a job description before applying?
21: How do you get started with open source?
20: What's it like to attend a tech conference? (Live at Future Sync)
19: What's it like being a remote developer?
18: What's the interview process for a tech job?
17: How do you find a mentor?
16: When should you specialise?
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
Lex Fridman Podcast