Doing too much work on one's own before looping in others
I&#x27;m good at working on a team and looping in others. I also find it to be one of the most exhausting parts of software development. It&#x27;s so difficult to constantly need to get feedback and buy-in from other people, and takes away a lot of the creativity and joy in programming (for me).<p>Which isn&#x27;t to say you shouldn&#x27;t do it, just that it&#x27;s one of the things that makes me dislike working on a team. I actually think this may be one of the factors in burnout for a lot of developers. Writing code as a team is almost like writing a novel with a few dozen other people, all of which have differing ideas on how the book should be written, or even what it should be about. It&#x27;s hard to feel the joy in creating something when you&#x27;re only a small cog in the development machine, and every decision needs a dozen voices of input.<p>It&#x27;s disempowering to feel like you&#x27;re never able to make a decision yourself, despite supposedly being hired for your expertise in the field.<p>&gt; Always encourage engineers to show their work as quickly as possible – an engineer on a project should never go more than a week without showing something, and usually it should be more like a day.<p>&quot;usually it should be more like a day&quot; is bad advice in my opinion, and a likely source of micro management. Let professionals do their work.