It seems that I didn’t communicate my feelings properly. I enjoy documenting and reading code. I also enjoy reading design documents that are very technical in

It seems that I didn’t communicate my feelings properly. I enjoy documenting and reading code. I also enjoy reading design documents that are very technical in nature and actually motivate the decisions and direction. I even read research papers on my free time. I also enjoy writing such documents and respective code. My issue is that I spent 4-5 days writing a darn excellent document on the proof of concept that I had built for a service we are supposed to launch this fall with a code freeze on September 1st. And today I had to spend all day writing yet another document summarizing what I had written in the first one so that I can have a discussion with other principals to get their comments (I got great comments from 2 in the presentation and follow up discussions), just to get an approval and the go ahead to productionise what I had already built that was shown to work. No other approach exists, no other poc exists, and most of my time is now fragmented because of the meetings. No other engineer working on this had an approach that could actually work for reasons I explained in yet another document, the more seniors had claimed they’d need a month to get the poc done. I did it in far less time, and had it all well documented. That was the most fun I have had in a while. Upper management (2-skip manager) gave me lots of praise and blew off another meeting he had to stay on for the additional questions and discussion, and scheduled another full on 1h meeting with me alone to discuss it further.