Retooling and refactoring - an investment in people.

Your developers don't need a dedicated DevOps team to run Kubernetes effectively. Learn a new approach to upskilling on the job.

#1about 2 minutes

Using instructional design to deliver technical outcomes

The entire consulting approach is framed as designing a learning journey with clear educational objectives for tech teams.

#2about 4 minutes

Why agile teams struggle with adopting new technologies

Agile methodologies work well for feature development within a known stack but fail when introducing new tools due to research pressure and the difficulty of finding correct patterns.

#3about 3 minutes

The failure of traditional training and external consultants

Abstract training is ineffective due to the forgetting curve and the tacit nature of tech skills, while consultants often remove ownership from internal teams.

#4about 5 minutes

A simple pattern for Kubernetes adoption without complex tools

A case study shows how to succeed with Kubernetes by avoiding complex abstractions like Terraform and Helm and instead using basic CLI tools.

#5about 2 minutes

Separating platform and developer team responsibilities

A clear model where a platform team provides core services like Kubernetes and databases, while developers own the application lifecycle and CI/CD within that platform.

#6about 2 minutes

Comparing AWS and Google Cloud for team productivity

Google Cloud is presented as a more modern and easier-to-learn platform with better defaults, reducing the need for a dedicated platform team compared to the complexity of AWS.

#7about 5 minutes

Investing in people through on-the-job skill sprints

The proposed solution is a hands-on, on-the-job learning model where a company's own staff implements new technologies with expert guidance, ensuring knowledge retention and ownership.

#8about 27 minutes

Q&A: Key skills, complex projects, and the future of tech

Discussion covers essential skills for developers like Kubernetes and Golang, a case study on retooling a legacy team, and predictions for technologies that will succeed Kubernetes.