Actual work, as opposed to real work.
I’ve spent half my 37+-year-long career cleaning up after idiots who think that “great software doesn’t need documentation”, or who file the “minimun necessary documentation” under “process artefacts”. Easily 3/4 of the failed projects I’ve seen in that time have a proximate cause of failure that is intimately tied to defective or missing documentation of key artefacts. I’m not one of those guys who favoured DOD 2167a “documentation by the boxcar load”, but your job as a developer is to communicate with the teams responsible for implementing, maintaining, and collaborating with your magnum oopus. That comes in two forms: working software, and working documentation. One is largely useless without the other.