One of the most hilarious ironies about technical writing is that the writer has to do so much more reasoning about the system as an interconnected and operatin

One of the most hilarious ironies about technical writing is that the writer has to do so much more reasoning about the system as an interconnected and operating system so they can describe how the user interacts with that system. I think you're correct about how PMs and technical writers are regarded and, as sad as it is, the truth is that engineers are usually rewarded through moving tickets from Not Started to Finished instead of building working and reasonable systems. If "finishing" tickets is where the money is, taking the time to reason about how any ticket fits into a coherent and correct system is an expensive process. More often than not, people are not successful because their projects are so good but that the project was good enough, long enough, and they moved on to greener pastures before the mistakes caught up with the system.