| This reminds of the technical writing education I received in college. While I understand the goal of this guidance is to make technical communication as clear and concise as possible, I also feel like it leads to a world of boring writers. And (IMO) boring communication actually should be recognized as worse communication, in comparison to communication that combines technical detail with human deliverance. The problem is all the more exacerbated when the guidance uses a checklist-like rubric such as: -"this sentence exceeds X word count, consider splitting" -"this sentence uses passive voice, use active voice". I remember "revising" parts of my senior design to score higher against a similar rubric, despite being confident that the revision was overall worse. Writing quality is inherently subjective, maybe to the chagrin of engineering types. Even though there are horrendous emails and documentation in the wild, I still think teaching people how to write with tools like this isn't the solution. |
I'm sure a lot of it was me just being a headstrong young person, but I also know that according to grades, I was much better at writing than most of my peers, and I also continually felt like I was writing worse than I could have been, in order to satisfy teachers.