What is "Vibe Coding"?
The term was coined by Andrej Karpathy (ex-Tesla, ex-OpenAI) and describes a new way of software development:
"There's a new kind of coding I call 'vibe coding', where you fully give in to the vibes, embrace exponentials, and forget that the code even exists." — Andrej Karpathy, February 2025
With vibe coding, you describe in natural language what you want to build, and an AI generates the code. You "vibe" with the AI, iterate through descriptions, and end up with working code – without having written every line yourself.
Typical Tools: Cursor, Claude (Anthropic), GitHub Copilot, Windsurf, Bolt.new
What is Low-Code?
Low-code is the established approach of building applications with visual drag-and-drop interfaces. Instead of writing code, you connect pre-built components.
Typical Tools: Microsoft Power Platform (Power Apps, Power Automate), Mendix, OutSystems, Retool
The Big Comparison
| Criterion | Low-Code (e.g., Power Platform) | Vibe Coding (e.g., Cursor + Claude) |
|---|---|---|
| Learning Curve | Gentle – visual, intuitive UI | Medium – must know how to formulate prompts |
| Target Audience | Citizen developers, business users | Developers, tech-savvy professionals |
| Flexibility | Limited to platform capabilities | Unlimited – any code possible |
| Maintenance | Easy, visually traceable | Requires code understanding |
| Costs | License fees (CHF 5–40/user/month) | Tool costs (CHF 20–50/month) + API costs |
| Vendor Lock-in | High (platform-dependent) | Low (standard code) |
| Enterprise-Ready | Yes, with governance tools | Depends – requires discipline |
When to Choose Low-Code?
Internal Tools
Forms, approval workflows, simple dashboards for internal processes.
Microsoft Ecosystem
If you already use Microsoft 365, SharePoint, Dynamics – seamless integration.
Non-Technical Teams
Business analysts and departments can build solutions themselves.
Quick Prototypes
Demonstrate a working app within hours.
Low-Code Example: Power Apps
// No traditional programming needed
// Visual formula in Power Apps:
Filter(
Employees,
Department = "Sales" && Status = "Active"
)
This formula creates a filtered view – without backend code, database queries, or API endpoints.
When to Choose Vibe Coding?
Customer-Facing Apps
Custom UX, branding, specific features for end users.
Complex Logic
When the low-code platform hits its limits.
Full Control
No vendor lock-in, own infrastructure, open standards.
Modern Stacks
React, Next.js, Supabase – use the latest technologies.
Vibe Coding Example: Cursor + Claude
// Prompt to Claude in Cursor:
"Create a React component for an employee
list with filter by department.
Use Tailwind CSS and display status as
colored badges."
// Claude generates complete code:
// - React component
// - State management
// - Filter logic
// - Tailwind styling
// - TypeScript types
In minutes you get production-ready code that you fully control and can customize.
The Risks: Where Things Can Go Wrong
Low-Code Risks
Potential Problems
- Shadow IT: Uncontrolled app proliferation
- Performance: With complex data volumes
- Limits: Eventually you hit boundaries
- Migration: Moving to another system is difficult
Vibe Coding Risks
Potential Problems
- Code Quality: AI doesn't always generate optimal code
- Security: Vulnerabilities get overlooked
- Maintainability: "Vibe code" can become chaotic
- Hallucinations: AI sometimes invents APIs
The Ralph Wiggum Loop
A common problem in vibe coding: The AI "fixes" a bug by introducing three new ones. You end up in an endless loop that Karpathy calls the "Ralph Wiggum Loop" – like the Simpsons character running in circles.
Hybrid Approach: The Best of Both Worlds
In practice, it often makes sense to combine both approaches:
- Internal processes: Low-Code (Power Platform)
- Customer portals: Vibe Coding (Custom Code)
- Prototypes: Low-Code for quick validation
- Production: Custom Code for scaling
Practical Example
Scenario: You want to build a customer portal with an internal admin backend.
| Component | Approach | Why? |
|---|---|---|
| Admin Dashboard | Power Apps | Quick to build, internal use, Microsoft integration |
| Customer Portal | Vibe Coding (Next.js) | Custom design, optimal UX, SEO |
| Automations | Power Automate | Email notifications, approvals |
| Complex Calculations | Azure Functions | Custom code for special cases |
Cost Comparison: Realistic Numbers
| Cost Item | Low-Code | Vibe Coding |
|---|---|---|
| Development time (simple app) | 1–2 days | 2–4 days |
| Development time (complex app) | 2–4 weeks | 4–8 weeks |
| Monthly costs (5 users) | CHF 100–200 | CHF 20–50 (hosting) |
| Monthly costs (50 users) | CHF 500–2000 | CHF 50–200 (hosting) |
| Maintenance/year | Minimal (platform updates) | Variable (code maintenance) |
Bottom line: Low-code has higher ongoing costs but lower development costs. Vibe coding is cheaper at scale but requires more initial effort.
Decision Guide: What Fits You?
Choose Low-Code if:
- Your app is primarily used internally
- You already use Microsoft 365
- Non-technical staff should build apps
- You need quick results (weeks, not months)
- Standard processes are being mapped
Choose Vibe Coding if:
- You're building a customer-facing application
- Custom design and UX are important
- You want full control over the code
- The app needs to scale (thousands of users)
- You have developer resources
The Future: Convergence?
Interestingly, both approaches are increasingly merging:
- Low-code gets smarter: Power Platform integrates Copilot for natural language app creation
- Vibe coding gets easier: Tools like Bolt.new generate complete apps from descriptions
- Both use AI: The boundary is blurring
In 2–3 years, we may no longer distinguish between "low-code" and "vibe coding" – but simply describe what we want, and the AI chooses the best approach.
Which Approach Fits Your Project?
I help you choose the right strategy – whether low-code, vibe coding, or both.
Request Consultation