How to automate engineering workflows with Claude Code

TL;DR

Claude Code’s co creator Boris argues that the skills engineers spent years perfecting, like automation, lint rules, and tests, matter more now as AI assistants scale. The video highlights how automation speeds up developer experience, makes previews valuable, and enables code based solutions that replace one off fixes. The message is that clever automation is the core leverage today.

Transcript

Engineering's changed a lot over the last few years, and I can understand why many people feel almost betrayed by this. Back in the day, I had so much fun customizing my setups in VS Code and Atom and even Sublime Text where I got started. And when I started my channel with the T3 stack, that blew up, too. I had so much fun with this type of work, ... Read More

Key Insights

• Claude Code’s co creator Boris reframes automation as central to modern engineering
• Automation speeds up infer and developer experience for all agents
• Preview environments gain value when code runs in the cloud and across fleets
• Custom automations, like file upload skills, demonstrate practical benefits
• Teams are more willing to invest time in automations now than in the past
• Moving repetitive tasks into code yields long term efficiency gains
• Lint rules and tests are high leverage automation targets
• A tight feedback loop with analytics improves reliability and output

Questions & Answers

Q: How can Claude Code's co creator Boris's post influence engineers today

Boris’s post reframes automation as a core capability beyond flashy AI tricks, urging engineers to lean into repeatable, code driven processes. It suggests that automations speed up both individual work and large scale agent based workflows, making it easier to build, test, and maintain complex systems across teams and projects.

Q: What is the role of automation in developer experience according to the video

Automation is described as a key multiplier of output, improving the speed and reliability of development efforts. By codifying repetitive tasks into lint rules, tests, or CI steps, engineers can reduce manual toil, catch failures earlier, and enable agents to operate more effectively across environments and tasks.

Q: Why are preview environments considered valuable in this new era

Preview environments are valuable because when code can be built and tested in the cloud or by agents anywhere, they provide quick, visible feedback without heavy local setup. This accelerates iteration, supports collaboration, and helps teams validate changes in realistic contexts before merging.

Q: What practical example of automation is given in the video

The video describes building a custom file upload service on Cloudflare to attach video assets to pull requests via the CLI. This example shows how small, purposeful automations can solve real workflow problems, improving efficiency and enabling teams to post richer context in PRs automatically.

Q: How has team attitudes toward automation changed

Teams are now more willing to invest time in crafting automations because the perceived payoff is clearer and the cost of experimentation is lower. The video notes that coworkers previously push back on such work, but AI and distributed workflows are changing the calculus.

Q: What is the long term benefit of moving tasks into code, according to the talk

Moving tasks into code creates durable, repeatable processes that run without constant manual intervention. This approach reduces token usage variability, ensures consistency, and enables continuous improvement through automated checks, lint rules, and CI steps, ultimately increasing reliability and throughput.

Q: How do lint rules and tests fit into the automation vision

Lint rules and tests act as scalable automation that can validate code across many cases automatically. They represent the kind of high leverage work that previously required heavy manual effort, enabling engineers to codify checks and protections that catch issues early and repeatedly.

Q: What is the sponsor segment advocating in relation to automation

The sponsor promotes a tool that helps agents run CI directly and access logs quickly, enabling faster diagnosis and fixes. This aligns with the automation theme by emphasizing faster feedback loops, lower costs, and better observability to empower autonomous agent workflows.

Summary & Key Takeaways

• The video explains that engineering automation and environment tooling remain highly valuable as coding work shifts with AI, encouraging developers to embrace automation. It emphasizes the shift from manual tweaks to repeatable code driven solutions and previews in a cloud oriented workflow.

• It illustrates how teams benefit from faster feedback loops, better analytics, and scalable automation, including examples like custom upload skills and cloud based previews to improve efficiency and reduce downtime.

• A takeaway is that investing time in automations now is rewarded with increased output per unit of time and more productive collaboration across teams, aligning with Boris's call for smarter tooling and workflows.