I work in a small company with 4 other developers. Essentially all projects are solo projects.
Our manager has a strong sales background, but can write "hello worlds".
He knows words like server, front end, back end, database.
He tells us what client has requested and it is our job to make it happen.
We report back to him about what tasks we did and how long we spent on them.
To my understanding my manager understands documentation as following:
- Most likely it is a wiki or a pdf, but it can be a issue description etc. It is something that can be read.
- Intent of documentation is to make developer's work easier. To enable them to produce business value faster.
He doesn't grasp how one can spend time on class/method names, version control, automation etc.
I see that he significantly underestimates value that clean code, automated tests and CI/CD pipelines can be for other developer. (Although as I mentioned that we have solo-projects, but we are in pain when we need to take over other projects).
So instead of reporting that I have spent a 2 days for refactoring and getting "customer didn't pay for that" look, I just tell him that I wrote documentation for a 2 days.
Is it unprofessional to keep details for myself that would otherwise put me into same battle all over again?
I wouldn't mind to share details if he asks and I will take responsibility for all the work that I have done.