The Hidden Cost of Developer Waiting

▶ Watch (00:08)

The 2025 Stack Overflow survey found developers blocked by delays in provisioning and approval waits, not by skill gaps. At an 800-person org, two idle hours per developer per week erases thousands of engineering hours. Add the platform and security engineers servicing those tickets and you lose the output of two or three full-capacity teams.

Ramanathan named the cause: the producer-consumer-approver triad. Platform engineers drown in tickets, developers wait on environments, compliance teams rubber-stamp requests and absorb blame for every delay. HashiCorp’s Cloud Complexity Report found 73% of respondents say those three groups do not work in unison.

Terraform as the Self-Service Foundation

▶ Watch (06:49)

Terraform gives you codified, repeatable infrastructure. Three layers on top turn it into a self-service platform: guardrails (policy as code, compliance baked in), governance (approvals, audit trails, cost controls), and workflows (the interfaces developers use, from Backstage to ServiceNow to GitHub Actions).

The fix does not replace existing tools. Developer portals, ticketing systems, and the Terraform construct itself all work. Backstage is a popular portal choice, though customers note the assembly time:

“backstage is like shopping at IKEA” — Bharath Ram Ramanathan

Developer Portal Path: Red Hat Developer Hub Demo

▶ Watch (12:12)

Raju walked through the Red Hat Developer Hub machine pool provisioning (12:50) live. A developer selects a cluster automation template in Red Hat Developer Hub, fills in a cluster name, instance type (ARM), and autoscaling min/max, then clicks create. Developer Hub triggers an HCP Terraform run behind the scenes, provisions the machine pool on ROSA (Red Hat OpenShift on AWS), and notifies the developer on completion.

Developers got speed without learning HCL. Platform teams kept governance intact. Developer Hub also connects Jira, VCS, and other tools into one portal.

ITSM Path: ServiceNow + Terraform Demo

▶ Watch (17:04)

Highly regulated organizations cannot remove approvals. ServiceNow already owns governance and audit trails for those teams. What it lacks is a backend automation layer. Terraform fills that gap.

Raju demonstrated the ServiceNow RDS workspace and day-two load balancer update (17:41) end to end. A platform engineer picks a catalog item, sets a workspace name, and provisions an RDS resource. Terraform runs behind ServiceNow. Later, the engineer adds a load balancer by committing a module change, cutting a new release, pinning the version in the registry, and updating the workspace. ServiceNow surfaces the change. Developers never touch the infrastructure layer directly.

Terraform-Native Path: HCP Waypoint Demo

▶ Watch (21:24)

Teams already deep in Terraform often do not want a new portal or ITSM integration. HCP Waypoint is built for them. Platform engineers create no-code module templates and attach one-click actions. Developers get a GUI and never see HCL.

The HCP Waypoint ECS deploy via one-click action (21:59) shows the full flow. A platform engineer builds an ECS template from a no-code module, attaches a deploy-to-ECR action, and publishes. A developer triggers the action and a to-do app appears live. Provisioning drops from days to minutes without the developer touching HCL or learning a new tool.

Notable Quotes

backstage is like shopping at IKEA Bharath Ram Ramanathan · ▶ 11:17

Terraform is consistent. Bharath Ram Ramanathan · ▶ 6:53

developers instead of days Tejitha Raju · ▶ 26:59

Key Takeaways

  • 800 developers losing 2 hours each per week equals thousands of wasted engineering hours per year.
  • Terraform acts as the orchestration layer across developer portals, ITSM tools, and native waypoint interfaces.
  • Self-service does not require replacing existing tools. Portals, ServiceNow, and Waypoint all work via Terraform APIs.