Get old, go slow, write code!

Is the software industry's obsession with speed actually slowing you down? Learn how a deliberate pace builds better software and more sustainable careers.

#1about 2 minutes

The connection between aging and speed in software development

The industry's focus on speed and the challenges of aging as a developer are two deeply connected issues.

#2about 6 minutes

Defining what 'old' means for a software developer

An interactive poll reveals audience perceptions of age in the tech industry, contrasting personal feelings with industry norms.

#3about 5 minutes

Comparing the average age of developers to other professions

Statistics show that software developers are significantly younger on average than professionals in other fields, even those with less required education.

#4about 6 minutes

Why developers leave the profession so quickly

Developers often leave the profession after an average of only eight years due to burnout, promotions out of coding, or feeling unable to keep up.

#5about 4 minutes

The Peter Principle and the developer-to-manager pipeline

Promoting great developers into management roles they are unsuited for can lead to incompetence, a phenomenon known as the Peter Principle.

#6about 4 minutes

Embracing slowness as a strength in software development

Software development should be viewed as a marathon, not a sprint, where a sustainable pace is more valuable than short bursts of speed.

#7about 5 minutes

How deadlines and agile sprints create a culture of rushing

Arbitrary deadlines, the lean startup "first to market" mentality, and agile terminology like "sprint" contribute to a harmful culture of rushing.

#8about 6 minutes

The long-term cost of rushing and the value of internal quality

Cutting corners to meet short-term deadlines creates poor quality code that significantly slows down development within a few weeks.

#9about 4 minutes

Practical ways to slow down and improve code quality

Improve long-term velocity by deliberately slowing down to practice, refine processes, plan thoroughly, and consistently refactor code.

#10about 8 minutes

Q&A on convincing clients and handling learning pressure

The speaker answers audience questions on how to justify a slower, quality-focused pace to management and how to cope with the pressure of new technologies.