Software Automation in a Polyglot Stack
summary
Argues for bringing languages in only when they add automation or libraries, then wires them into the org with concrete artifacts: uses MakeDocs (Ruby) and HTMLpref (Python) inside a Docker container so team members never install Ruby/Python locally, exposes branch previews via an Atomist trigger into Slack and Kubernetes, and automates repo seeds plus an alias that opens a PR so small fixes get turned into real PRs. These automations work and increase collaboration; also documents readme-driven development.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:40Assumptions
- 4:00Automation
- 4:55Language
- 7:20Language community
- 9:40Introducing a new language
- 12:40The problem with Java
- 14:50Building new armor
- 15:15Protective shell
- 16:10Atomist
- 17:40Readme
- 20:55Language API
- 24:55Local Automations
- 26:40Project Creation
- 28:25Reasons to automate
- 34:25Productivity vs generativity
- 37:25Risk and Impact
- 40:55Wrap Up
- 44:45Questions
related talks
06mMaking Automation like Docker Containers
22mAutomate your inner scout
57mRise of the Machines - Automate Your Development
12mHow we automated code maintenance
04mAutomate!
59mDevelop Your Development Automation
33mFrontend automation: bring it to the next level
09mThe Robots are coming for your job, and that's okay