Software Engineering

AI-generated infra, docs, and glue code

Use AI assistants to draft infrastructure bits (manifests, CI, scripts) plus β€œboring but important” work like docs, migrations, cleanup, and platform glue code.

Why the human is still essential here

Engineers validate security, correctness, and operational behavior (tests, edge cases, deployment sanity); AI speeds up drafting and routine work but humans are responsible for production readiness.

How people use this

Kubernetes manifests and Helm drafts

The assistant generates initial Kubernetes YAML/Helm templates from deployment requirements, which the engineer then hardens and validates in staging.

ChatGPT / Claude

CI workflow generation

The assistant drafts GitHub Actions pipelines (build, test, lint, deploy) tailored to the repo conventions, with the engineer verifying secrets and permissions.

GitHub Copilot

Docs and migration script drafts

The assistant produces first-pass API docs, migration steps, and one-off scripts, with the engineer reviewing for correctness and operational safety.

ChatGPT / GitHub Copilot

Related Prompts (4)

Community stories (1)

Medium
9 min read

AI Coding Assistants: Value, Workflow, and Tradeoffs (March 2026)

AI coding tools change fast. Anything I write today might be outdated next week. Its fine as this post is just a snapshot of has been useful to me, what feels like good value, and what I would pick depending on your constraints (privacy, budget, and how much you actually ship).

This blog is not a benchmark roundup, and I’m not trying to identify the best tool. It is a workflow-first take from someone who spends most days shipping production code, hacking prototypes, and then dealing with the maintenance.


Here is the kind of work I usually do:

- Frontend: React (TypeScript)

- Backend: Go / Python services

- Infra: Kubernetes, cloud-native deployments, networking

- Typical tasks: Web apps, production APIs, dashboards, platform glue, infrastructure


When I test a coding assistant, I do not throw toy examples at it. I give it things that actually happen:

- turning UI into code (screenshots, design-to-code, MCP-style workflows)

- adding a feature across frontend + backend (sometimes infra)

- refactoring while keeping API compatibility

- writing infra bits (manifests, CI, scripts)

- boring stuff that still matters: docs, migrations, cleanup, glue code


...

TF
Teng FoneData Engineer
Mar 5, 2026