[rubicon33]

Recommend this book, but honestly you don't need to read it:

Deep Work: Cal Newport

What you need to know from this book is that to write good software (both quality and quantity) you need to go deep. You need to fully absorb and understand the problem in your mind, BEFORE you begin writing code. And then, you need quiet undistracted time to map the thoughts in your mind, to code on paper.

This process of turning a mental model in your mind, into a well designed code model, takes more focus than you think (if you want to do it well). Give yourself a quiet room with no visual distractions. Just you, and your code. Set aside a few hours.

Most importantly of all - Remove the possibility in your mind, that a distraction could happen. I cannot emphasize this enough. Your mind will not go deep if, even on a subconscious level, you think a distraction could come. A text message, a spouse walking in, a co-worker asking a question, etc. These all need to be (as reasonably as possible) NOT possible so that your mind can go quiet, and you can take on the work.

[ArcMex]

I would have loved to see you talk about the part of the book that addresses working with others, as that seems topical to the OP.

Overall, it is also my recommendation, in that when you develop a good habit of churning out quality work, it enhances your contributions to the team.