Shumin did a very good job of explaining how the compliance in a language standard like STE varies from one industry to another, and is nothing like the law that enforces strict rules based on deterrence. Rather, it is a user-friendly standard that writers can turn to in times of need for consistency and standardising. My favourite STE rule is simply to use only approved technical words with the correct meaning and part of speech assigned.

The Simplified Technical English course content and requirements provided by Shumin Chen were an absolute good fit with the TCLoc Master's program. A technical communicator has to know about the existing specifications for technical documentation. Furthermore, this course helps the students to acquire new skills in order to enhance the accuracy and clarity of contents.

The course provided a strong foundation in Simplified Technical English. While the core principles were familiar, the emphasis on practical application was invaluable. I particularly appreciated the concise and clear writing style promoted throughout the training. However, to truly maximize the learning experience, additional time for hands-on exercises and in-depth discussions would be beneficial. Prior exposure to the writing rules could have optimized class time for more interactive learning and focused question-and-answer sessions. Despite these suggestions, the trainer's expertise and engaging delivery significantly enhanced the overall experience. The course content was well-structured and informative, providing a solid understanding of STE principles. I would confidently recommend this course to colleagues seeking to improve their technical writing skills.

The introduction was a good and concise way to familiarize yourself with STE basics. I’ve a background in plain language, so for example the rule on noun clusters makes perfect sense. I’m all about simplification, so substituting verbs like “eliminate” for verbs like “remove” or “stop” will be my new quest. The STE exercises were helpful in getting to grasp with STE during the training workshop. I'd very likely recommend this course to anyone planning to introduce STE as it’s got a great practical angle.

I find that STE rule 2.1 extremely useful in technical documentation to avoid ambiguity. Rule 3.6 is one of my favorites because you need to master well syntax and language to always avoid passive voice. It was a good excercise, thanks Shumin for this interesting and challenging topic!

This was a very useful training course for understanding the meaning and goals of Simplified Technical English. The trainer's performance is very good and experienced. My favourite STE verbs are: COLLECT, EXAMINE, and GET. The exercises in this course are helpful and reinforced learning. STE should be the standard for any technical contect written. I would recommend this STE training workshop to any suppliers and colleagues in the field.

I've worked with Shumin Chen when she was a Localization Program Manager for large projects into multiple languages. She was always very professional and confident. I would work with her again in the future.

I am giving this training a 10/10. There was a good introductory and explanation to describe the 2-day training seminar. Rule 1.1 0 lets me use words that are: approved in the dictionary / technical names / technical verbs and is one rule I like very much because of its flexibility. I think rule 1.1 is the most critical and important for STE dictionary. Sometimes I have to use non-approved words as an exception, but I will try to keep this rule 1.1 in my documents for good measure. Although some of the exercises were tricky, they remind me of each rule application at that time. So they were practical for my role as a technical writer. I want to recommend this course to current technical writers in Korea or engineers who are interested in writing their own documents effectively.  

I worked with Frans on a project for translation for technical manuals. It was a pleasure to work with him and he was very professional. He responded to our queries quickly and informatively and he was an asset to have on the project, as he has a vast knowledge of technical translation. Top qualities: Great Results, Expert, On Time.

My favorite STE writing rules: * Rule 1.9 and Rule 1.10 When you must select a technical name, use one which is short and easy to understand. Both rules ensure a better understanding of technical contents. * Rule 3.6 Do not use a past participle with a helping verb to make a complex verb. Past tenses may be adequate for marketing texts due to stylistic reasons, but not for technical contents, where precision and clarity play a major role. * Rule 5.1 Keep procedural sentences as short as possible. The description of procedures in technical manuals has to be as simple as possible to avoid confusing the reader.