I'd take poor grammar and interesting ideas over clear grammar devoid of real content any day of the week.
It helps if your technical writers already adhere to a voice/tone guide, which can be pretty easily adapted/extended for automated documentation generation. If one doesn't exist, you'll definitely want to create that first. Some good examples:
Google: https://developers.google.com/style
IBM: https://ptgmedia.pearsoncmg.com/images/9780132101301/samplep...
Microsoft: https://learn.microsoft.com/en-us/style-guide/welcome/
Red Hat: https://stylepedia.net/style/
Are you kidding me? This is the laziest, campiest, knee-jerk point I've run into in quite sometime.
I expect, as my co-workers expect of me, to learn and improve. Writing is a core part of engineering, and management.
I'd have some choice words for my co-worker (or vice-versa) if we just gave up and "ChatGpt'd our way to the top."
Network Engineering design docs can be somewhat formulaic structurally, making the LLMs job simpler. I imagine in the near future we’ll just ask them to follow doc templates or reference other designs within a RAG system to ensure there aren’t gaps in the doc, etc.