Continuous Delivery to Cloud Foundry: Why Your Junior Devs Will Love It! - Robert Summers, Armakuni
summary
A junior-turned-developer reports a path that moves a bootcamp grad into daily feature delivery: a 12-week Makers Academy background, then a two-week onboarding before joining an agile team that uses pair programming and TDD. Concrete workflow: write tests, push small changes, let Concourse pipelines as code run unit/integration/preprod smoke tests and then allow daily production pushes to Cloud Foundry, giving immediate client feedback and rapid learning while reducing fear of breaking things.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:10Background
- 5:19What does it take
- 6:12What are the roadblocks
- 8:11How do we get there
- 10:03Pair Programming
- 10:50Pair Programming Setup
- 11:19TestDriven Development
- 12:23Roadblocks
- 13:38Cloud Foundry
- 14:25How do we overcome this
- 14:55Does anyone use continuous delivery
- 16:29Pipelines
- 17:21Concourse
- 18:35Pipeline
- 22:31Summary
- 23:50Pairing with senior developers
related talks
10mCloud Foundry Accelerates "DevOps+"
23mAccelerate DevOps Adoption With A Dojo
01h 09mContinuous Deployment to the Cloud
27mContinuous Delivery of Cloud Native Microservices on the PCF Platform
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
44mContinuous Delivery with Concourse CI
27mContinuous Delivery of Cloud Native Microservices on the PCF Platform
03mIntroduction to the Cloud Foundry for Developers Track