I recall when I entered college. The first thing was mandatory, required, english classes.

The logic was, if you cannot communicate, you cannot explain why your job, or what you're doing is important. If it has value. If you have value. You cannot hope to explain requirements to others. Or explain the logic or reasons, the "why" of a technical path.

You're likely correct that a lot of people think this unimportant. To them I'd say, they're severely limiting their career, if they don't think communicating is important.

That's really interesting to me. I consider writing to be a "raw technical skill." Programming and writing are inextricably linked. The lexicon of software borrows heavily from writing: language, syntax, grammar, statement, and expression. Even the way we critique code heavily overlaps with how an editor critiques writing: consistent, readable, elegant, concise or verbose, and follows a style guide.