About This Course
Learn how to code world-ready software. In this Part 3, we will have several coding challenges where you will be able to apply what you learned in Developing International Software, Part 1 and Developing International Software, Part 2.
In Part 1 we covered the fundamentals and definitions of developing international software and introduced you to what it means to be "world-ready" and how to make localization work for you. In Part 2 we talked about the importance of designing for cross-cultural applications.
Senior Director for Technical Content, Learning Experiences
Björn is the Senior Director for Technical Content in the Learning team at Microsoft, a husband, a father of two STEM girls, and proud geek. #DFTBA!
After 23 years at Microsoft in different engineering roles Björn got exposed to MOOCs through an intern in his team. He then set his goal to join the Learning Experience team to be part of the learning revolution. The French revolution was also exciting, but this one has fewer guillotines, which is a pretty big plus in his book.
The Arioso Group, LLC
Nadine spent twenty-three years at Microsoft working in a variety of technical and business roles. Straight out of college, she joined the Word for Windows team, eventually signing off on several dozen Western European versions of Word, from Word for Windows 1.0 through Word for Windows 6.0. Although writing code was fun, she found she actually liked teaching better. So she transferred to the Windows team, where she lectured on software internationalization, wrote the landmark book Developing International Software, and a ton of articles for publications like Microsoft Systems Journal, Microsoft Developer Network and Multilingual Computing Magazine.
Principal Software Engineer
Erik Fortune is a Principal Software Engineer at Microsoft, working on developer platforms. Previously he worked at IBM, Digital, Silicon Graphics, and WebTV. Erik has more than 30 years of experience in the high-tech industry, including 20+ years of globalization & world readiness work as individual contributor, architect and Lead Developer.