I'm Process-Oriented in Coding, but Results-Oriented in Writing

I’m process-oriented in coding, but results-oriented in writing.

With coding, the work itself is the part I enjoy. I love building something, watching it breathe, and seeing how it responds every time I change it.

Writing feels almost like the opposite. The process is slow. It is agonizing. But it is worth it. I can finish a piece, look back at it fondly, and be proud that I made the thing I wanted to make. Once it is finished, it feels timeless in a way that most code cannot be.

It is a good thing that I am process-oriented in coding because, unlike writing, code is never finished. At least, customers never seem to think it is. There is always another bug, another feature request, or another dependency to update. The process needs to be enjoyable because otherwise it’s exhausting.

I code because I love doing it. I write because I love having written something.