The time working remotely worked best for me, I spent three to three and a half days a week interacting with coworkers, meeting, troubleshooting and identifying problems. Then on fridays I sat in a coffee shop coding like mad to address one or more of the things I learned by talking to people.

My code (central library six products used to interchange data) was good because I saw it reflected in the experiences of my coworkers.

To experience that I had to train people to interact with me when they got stuck. I needed to be absent one day a week so that I had an opportunity to do something about what I learned. To execute the plan I had built up all week. Almost half of the code I wrote all week was done on fridays. But it was often the most useful.