Technical toolkit · Milos Cvetkovic, Senior Full-Stack Engineer
Tools are just tools.
What matters is knowing when to use them and why. Here's what I reach for—and the experience behind each choice.
Primary weapons
Self-assessed depth, not a measurement. The years count from my first production work in each.
TypeScript
8+ yearsMy language of choice. Type safety isn't optional when you're building systems that handle real money.
React / Next.js
7+ yearsFrom SPAs to server components. I've shipped React at every scale.
Node.js
8+ yearsAPIs, microservices, CLI tools. If it runs JavaScript, I've probably built it.
AI/LLM Integration
2+ yearsNot just prompts—production AI with guardrails, cost controls, and real observability.
What makes the difference
Full-Stack Ownership
I don't throw code over the wall. From database schema to deploy button—I own the whole thing.
Legacy Fluency
I can read your 2015 jQuery spaghetti, understand why it works, and migrate it without breaking production.
AI-Native Workflow
I ship 3-5x faster using AI tools—not as a crutch, but as a force multiplier for experienced judgment.
The full toolkit
AI & Agents
Building AI that actually works in production
Frontend
Modern interfaces that users love
Backend
APIs and services that scale
Cloud & DevOps
Infrastructure that doesn't page you at 3am
Architecture
Patterns that survive contact with reality
Testing & Quality
Confidence to deploy on Friday
How I stay sharp
I don't believe in "knowing everything." I believe in learning fast and building constantly.
Every week, I ship something—even if it's small. This portfolio? Built with Next.js features I learned while building it. My self-healing agent? Started as a weekend experiment.
The best engineers I know aren't the ones who memorized every API. They're the ones who can pick up any tool and be productive by lunch.
Want to see these skills in action?