Shift left the proper way
summary
Claim: developers spend less than three hours a day actually writing code, so work is being shoved left instead of information. Shows concrete failures: running 30,000 unit tests for a 50-line change, 5,500 pipelines for 5,000 apps, surprise giant cloud bills from overprovisioning. Prescribes automating the entire SDLC, surfacing cost/security/test results at deploy time, using guard-rails and reusable templates, and advertises a CI built on Harness that it claims is 10x faster to speed builds while keeping governance and audits.
AI-written summary · about
chapters (9)
- 0:00Introduction to shift left
- 0:43The problem with shifting workload left
- 2:27Engineers' actual coding time
- 3:49Bring information left not workload
- 5:55Automate the software delivery lifecycle
- 7:40Empower teams with guardrails
- 9:47Standardize pipelines and templates
- 11:11Proper shift left principles
- 12:32Q&A and closing
related talks
16mShift Left, Not Off a Cliff: Why Your Testing Strategy Is Breaking Developers
37mDon’t Sh*t-Left: How to Actually Shift-Left
35mA Tale of Two Codebases
27mDeveloper Experience: It’s Time to Start Complaining
28mHow to prioritize dev experience in the development process
52mShift Left or Squish Right - Testing in a Shifting World
25mCI/CD Delays: Losing Time, Money & Sanity
27mThe Cost of a Bad Code and Pipelines