Bad software is often created by the conditions around engineers, which are shaped by leadership decisions, not a lack of technical skill.
While AI tools can accelerate code execution, they cannot replace the essential human leadership functions of creating trust, setting priorities, and managing pressure.
When leaders are held accountable for quality without having real influence over deadlines and decisions, it creates a cycle of technical debt and team burnout.
Micromanagement and metrics like billable hours create a culture of control that discourages deep thinking and prioritizes measurable output over sustainable quality.
A culture of fear prevents engineers from speaking up about risks, creating silent vulnerabilities that no security tool can detect.
Leadership decisions about deadlines and risk directly translate into technical outcomes, creating a feedback loop where pressure leads to shortcuts and more pressure.
Strong engineering leaders translate external business pressure into clarity for their teams by defining priorities and trade-offs, rather than simply passing it on.
Providing teams with the problem context rather than a pre-defined solution fosters engagement, better questions, and a deep sense of ownership.
Involving the team in deadline negotiations creates transparency and shared commitment, turning pressure into a manageable challenge rather than a source of debt.
Recognizing engineers as creative people with judgment, not just execution units, is essential for building teams that can innovate and solve complex problems.
Actionable advice is provided for developers, tech leads, and formal managers on how to identify and change negative patterns within their sphere of influence.
The most impactful code a leader writes is the team culture, as it shapes every decision, interaction, and line of software the team produces.
Jobs that call for the skills explored in this talk.