This is the second part of the OpenExchange: Age of Developers series and is meant to highlight a few benefits of getting involved in the translation industry as a developer.

Age of developers - table of contents

As I release parts of this series I will update this page with links to the articles.

  1. Introduction
  2. I'm a translator do I need to write code?
  3. I'm a developer, why bother with translation industry?
  4. Configure OpenExchange development environment
  5. OpenExchange:Where do I start?
  6. About SDL Studio SDK

Translation industry

I'm a developer, my heart beats 01010101..., so I'm not going to bore you with market shares, revenues and other big numbers about how big this industry is. If you are really curious about this have a look here. What I would like to say is how important this industry is in today's world and to sustain my affirmation look at these numbers:

  • Only 27% of Internet users speak English
  • 70% of internet traffic comes from non-English native countries
  • 34% of Twitter messages are in English
  • 75% of Facebook users are outside of US

Interesting numbers I must say and they clearly show how relevant this industry is. Now some of you might have heard about machine translation but the translation industry is much more than that. It's about language localization, interpretation and terminology.

Technology

Now let's get closer to what we as developers are interested in, which is the technology. Each industry has its own specific terminology so I would like to take this opportunity to briefly explain some of the terms:

  1. CAT tools (Computer-Assisted Translation) - typically these are desktop applications that aid translators and linguists to increase their translation productivity. While these applications will continue to be predominant on the desktop, web solutions will slowly appear that will add new options for translators and linguists.
  2. Translation Memories - this are databases that store segments, which can be sentences, paragraphs, headings, titles or elements, from any filetype, in a list that has been translated. CAT tools rely on translation memories to aid the translator during the translation.
  3. Termbase - this is a central repository, like a database, which allows translators to systematically manage approved terms.
  4. Machine translation - this is about automated translation of natural languages. Probably all of you have used free translation or google translate which are the great examples of machine translation at work. The examples I've given are just end-user products but each platform exposes machine translation capabilities through various api's as part of a cloud offering.
  5. Post-editing - this is the process of improving a machine generated translation and typically is done from a CAT tool.

Why bother?

Now that I've given you a brief overview of the translation industry the big question is why should I, as a developer, bother getting into this. I already know desktop, web, mobile and/or cloud technologies and I also have to keep up with the fast pace of technology changes. That might be true but if you really want to be a great specialist it's not enough just to know some technologies, you need to make them relevant. People expect solutions for their problems from developers and good solutions require industry expertise. If someone asks you to build them an accounting system you don't need to be an expert accountant but you need to know a few things about accounting. I highly recommend reading the article from John Sonmez "I'm not sure I want to be a specialist" which emphasizes on specializing as a developer.

Becoming a specialist will help you become a better professional, find interesting job opportunities or even become a freelance developer if this is something you're looking for.

Specializing in a specific industry makes perfect sense and this why I consider that you as a developer should take into consideration the translation industry.

Where do I start?

A great way to learn about the translation industry is to start develop plugins and apps for existing products. The SDL OpenExchange app store is nice way to publish your work and maybe even earn some money. At the very best you will gain exposure as a developer to those translations companies looking for development expertise to help them integrate their own systems or gain some competitive advantage by asking you to implement some ideas of their own. To publish an app on SDL OpenExchange you need to become an SDL OpenExchange developer. This is a simple process you can follow from here. You don't need to worry about licenses since SDL can offer dedicated developer licenses:

  1. CAT Tool - SDL's CAT tool name is SDL Trados Studio 2015 and in order to develop anything on top if it you'll need a license. In order to get a developer license please create an SDL OpenExchange developer account and then send an email to [email protected] and this will be sorted out
  2. Machine Translation - SDL's machine translation cloud solution is named Language Cloud and you can sign-up for a developer account here.

Every new journey might be a bit bumpy in the beginning and you should not hesitate to ask for help. I recommend to register in the language developer community and ask for help there.

Conclusion

My best advice is to have patience, practice as much as possible and don't be afraid to ask. I'm sure the results will come sooner or later. Happy coding.

Please leave a comment if you have any questions.