The awkward middle ground between full-stack and cloud infrastructure

Jay Patel — Sat, 13 Jun 2026 13:00:06 +0000

Hey guys,

Lately, I’ve been trying to bridge the gap between my day-to-day work as a full-stack MERN dev and the infrastructure side of things as an associate cloud engineer.

Honestly, the deeper I go down this rabbit hole, the more I realize how weirdly blurred the lines have gotten.

It feels like full-stack devs are now expected to be mini-DevOps engineers who just casually containerize everything with Docker, write GitHub Actions CI/CD YAML files from scratch, and debug K8s cluster networking on a Tuesday afternoon. Meanwhile, cloud teams are playing a never-ending game of whack-a-mole, trying to figure out how to handle application secrets without losing their minds when a dev accidentally hardcodes an .env variable.

I’m really curious to see how other teams are splitting the bill on this in the real world.

If you’re a full-stack dev: How much of the cloud config do you actually touch before handing it off? Are you just writing the Dockerfile and throwing the image over the wall? Or are you actively configuring API Gateways, provisioning databases, and tweaking AWS IAM policies? Where do you think the boundary should be?

And for the DevSecOps / Cloud Architecture folks here: What is the absolute biggest "please, for the love of clean architecture, don’t do this" mistake you see web devs make when they try to ship a Node/Express app to production?

Is it running containers as root? Is it using latest tags for base images in Docker? Or maybe passing production DB credentials as plain text in the CI pipeline?

I’d love to hear some perspectives, hot takes, or absolute horror stories in the comments. How is your team handling the dev-to-cloud handoff right now? 👇

DEV Community: Jay Patel

The awkward middle ground between full-stack and cloud infrastructure