How I Got into Technical Writing

It's about Communication

When I look back over my education, everything I studied—languages, philosophy, teaching English, translation and interpreting, technical writing— turns out to be about communication.

It's about Writing

It was always about writing. When I graduated from college, I had written quite a few short stories and wanted to study creative writing. Rejected by two prestigious programs, I turned to other forms of writing instead.

“Translation has nothing to do with language!” That's one of my favorite quotes. For me, translation has little to do with foreign language, and a lot to do with English writing. I don't consider myself an expert in my foreign source languages. In fact, I once wrote an essay, “Push Me/Pull You” about how I “pull” information into my document using strong English style and logic.

Whatever you think about translation, it's true that in my work I formulated, edited, and proofed thousands of words a day (my own translations and others'). Some of them were published as original English (brochures, technical manuals, annual reports, etc.) by companies like Swatch and SAP.

It's about Information

Truth is, I don't traffic in words. I traffic in data, in ideas and intentions. Language is just a tool for facilitating their transport. My professor Arthur Braunstein used to say that words are just containers, and we pour our ideas and intentions into them.

I Believe in Text

I believe every text has a right to become the best text it can possibly be, to optimally transport its information and intentions from one person to another at a given place and time, whatever the medium.

More about Me

• Creative Writing
• Viaje a la Habana