As a single developer, I'm now able to own the entire lifecycle of a web application — cloud infrastructure, version control, CI/CD, and full-stack development — all using AI as a co-pilot. It's quite impressive how far we've come.
I signed up for Claude Code Pro ($200/year at ~$17/month) and paired it with an Azure Web App to stand up an ASP.Net MVC web app with auto-deployment from GitHub. Running Claude Code directly inside VS Code keeps everything in one place — no context switching, the AI is right where the code lives.
// section 01
What I'm Practicing
- → Cloud infrastructure — Azure Web App (serverless / PaaS)
- → Version control — GitHub
- → CI/CD pipeline — Auto-deploy on every push
- → Full-stack .Net web development — ASP.Net MVC
// section 02
The Stack
| Category | Tool | Cost |
|---|---|---|
| AI / Coding | Claude Code Pro | $17/mo (annual) |
| Editor | VS Code | free |
| Cloud | Azure Web App | — |
| Framework | ASP.Net MVC | free |
| VCS | GitHub | free |
| CI/CD | Azure auto-deploy from GitHub | — |
// section 03
Why It Works
Azure Web Apps need no VM management — point it at a GitHub repo and every push triggers an automatic build and deploy. Claude Code handles the heavy lifting on scaffolding, controllers, and config troubleshooting. A solo developer can now realistically own what used to require an entire team.
// note Running Claude Code directly inside VS Code keeps everything in one place — no context switching, the AI is right where the code lives.
// section 04
Concerns
While it seems effortless on the surface, I'm not ready to trust AI-generated code for anything external facing. Reading through the code carefully, I do catch mistakes — logic errors, incorrect assumptions, things that would slip through if I weren't paying attention. It's a co-pilot, not an autopilot.
// warning For now I'd feel comfortable shipping an AI-assisted app on a closed intranet or private network. Anything public-facing on the open web is a different story.
Security, edge cases, and production-grade reliability still require a developer who actually understands what the code is doing. The tooling is impressive — but it doesn't replace the need to read, understand, and own every line.

Comments
Post a Comment