About me
With a master’s in Japanology and a postgraduate degree in Computer-Assisted Language Mediation, I don’t have the most obvious background for a technical writer. But besides languages and learning, I also have a great interest in logical thinking. I really enjoy logic puzzles and making something make sense, which is what attracted me to technical writing.
Technical documentation is a field that keeps on growing and renewing itself. So, the problems we encounter and the solutions we discover are constantly changing. The problem-solving aspect of this line of work makes every day interesting and different.
Doing research about a subject, often starting from scratch until you have thorough understanding of it, is already quite rewarding. But then, shaping your hard work into a manual or user guide that is approachable and easy to understand for everyone is even more fulfilling.
The quick-fire question round
Flow: Software or hardware documentation?
Maxence: “I like the variety of hardware documentation, but I would also like to try out writing software documentation.”
Flow: Internal documentation or end user documentation?
Maxence: “The goal remains the same: writing documentation as clear, simple and helpful as possible. Only the audience is different, so I find both interesting.”
Flow: Agile or waterfall development?
Maxence: “Agile development! I really enjoy projects in which you can brainstorm with colleagues and receive feedback from them. For me, it is a great way to learn fast and on your feet.”
Flow: Time travel to the past or to the future?
Maxence: “It is a bit embarrassing to say, but I quite enjoy a good historical romance book. So, I would have to take a peek into the past.”
A glimpse of the future
In one month I have already learned so many new things, also about myself. I am very excited to continue this path to gain more knowledge and grow as a technical writer.