- PLAYER
- Milos Cvetkovic
- CLASS
- Full Stack Engineer & Architect
- SPEC
- AI-Native Development
- XP
- 13 years · 6 domains · 3 clouds
- STATUS
- Building at Obsidian 22
This happened at 3am.
Nobody woke up.
Milos Cvetkovic, Senior Full Stack Engineer specializing in AI-native development, TypeScript, React, and cloud architecture.
I build systems that inherit chaos and ship clarity.
Scroll to see how.
- TypeScript
- React
- NestJS
- Azure
- Terraform
- Claude Code
- DDD
- Kubernetes
PHASE 1 DISCOVERY
"I'm tired of 3am pages. Build something that fixes itself."
Interesting. What does "fix itself" mean to you?
Detect the error. Understand it. Open a PR with a fix.
Autonomous code changes need guardrails. What's the blast radius?
I'm thinking: budget caps, confidence thresholds, human approval...
Most bugs live in the gap between what you asked for and what you meant.
I close that gap before writing a single line of code.
PHASE 2 STRATEGY
TECH TREE
Cold starts matter when errors are on fire
Type errors caught at compile time, not 3am
The part that actually thinks
See everything. Miss nothing.
SYNERGIES DETECTED
Hype fades. The right tool for the job doesn't.
I pick technologies that solve the problem, not pad my resume.
PHASE 3 EXECUTION
export class ErrorAnalyzer {
async analyze(error: Error) {
const context = await this.getCodeContext();
return this.claude.diagnose(error, context);
}
}The bottleneck was never my typing speed.
AI writes the syntax. I make the decisions that matter.
PHASE 4 THE GAUNTLET
"It worked on my machine" doesn't fly here.
Six gates. Zero shortcuts. Every commit proves itself or dies trying.
PHASE 5 THE LOOP
This happened at 3:14am. Nobody got paged.
The system diagnosed itself, wrote a fix, and waited for a human to approve. That's the future I build.
SESSION COMPLETE
This is how I work. Every time.
Follow along for more engineering deep dives.
Or scroll down to see more of my work
Featured Work
- PRODUCTION
- PRODUCTION