|
Why do many software projects tend toward so much responsibility falling on a single engineer? We discuss some of the perceptions around feeling like someone else would be better suited to a task than we are, why developers might defer decision-making to others, and how a series of small breakdowns can lead to a siloed, burned-out lead developer.
Our discussion ultimately leads to a review of a project lifecycle on a healthy team — from design phase, to documentation, to creating clear development processes. Ultimately, the problems that lead to a single point of failure are small, frequent problems over a long period and can only be solved by small, frequent effort every day.
Speakers Bryan Forbes on Twitter Neil Roberts on Twitter Paul Shannon on Twitter Nick Nisi on Twitter
Listen Now!
The post Episode 53: Single Point of Failure appeared first on SitePen. |