proomt

Search

Search posts, papers, and topics

All posts

Zapier EngineeringLane Gillespie5 min readintro

63% of developers have more work since non-devs began coding with AI, but most say it's good for the industry

Read on zapier.com

Summary

A Zapier survey of 797 U.S. developers finds 63% see more work as non‑technical coworkers use AI coding tools, yet two‑thirds view the shift positively. Developers are moving toward higher‑value strategy, governance, and cross‑functional work, and the top future‑proof skills are security, AI/ML, low‑code QA, strategy, and data engineering.

  • 63% of developers report increased workload due to non‑technical staff using AI coding tools, but 66% see it as a positive industry shift.
  • 84% say their role has changed, with 56% moving toward higher‑value strategy, architecture, and governance tasks.
  • Top future‑proof skills identified are security/privacy, AI/ML understanding, low‑code QA, technical strategy, and data engineering.
  • Only 14% feel their day‑to‑day scope has shrunk, indicating AI automates boilerplate rather than eliminating developer work.

Engineering leaders and developers should care because AI tools are reshaping workloads, emphasizing strategic and governance skills over routine coding.

5/10
aicareergovernanceai codingdeveloper productivity

Related reading

  1. The 2026 State of Code Abundance Report: Exposing the Enterprise AI Readiness Gap

    A report highlights a significant gap between enterprise confidence in AI-generated code and operational reality, with 81% of leaders reporting increased production issues despite high readiness scores. This "code abundance" means code is generated faster than organizations can effectively test, govern, and manage it, leading to challenges in cost attribution and governance.

    Codeshipcloudbees.com5 min

  3. Agentic DevOps World 2026: Key Takeaways

    Enterprise AI code generation is outpacing governance: 92% of leaders feel confident but 81% see more production issues; post‑generation stages (review, testing, deployment) are now the bottleneck. Successful adoption requires up‑skilling, end‑to‑end metrics, and tooling (e.g., CloudBees DevOps Agent Kit, PR‑auto‑approval agents).

    Codeshipcloudbees.com8 min

  5. Should you read the code, is RAG dead, and did Skills kill MCP?

    The article debunks five common AI‑tool hot takes, arguing you still must read AI‑generated code, AI fluency matters in hiring, MCP and Skills serve different purposes, RAG remains useful, and needing fine‑tuning signals a messy codebase. It offers concrete rules for reviewing generated code and integrating AI components responsibly.

    GitHub Oldgithub.blog5 minHN3

  6. Who Owns AI-Generated Code Failures?

    AI‑generated code breaks the traditional chain of ownership: developers merge PRs they didn’t write, reviewers approve logic they didn’t originate, and QA validates tests chosen by a model. A CloudBees survey shows 81% of firms see more production failures from AI code, and accountability often drifts upward to CTO/VP. The post argues role‑based accountability isn’t enough; you need end‑to‑end tr…

    Codeshipcloudbees.com4 min