Readit NewsLocation: Munich, Germany
Remote: Yes
Willing to relocate: No
Technologies: Laravel, Vue.js, PHP, Inertia.js, Livewire, Alpine.js | React, Next.js, Python (Django, FastAPI), Node.js (Express, NestJS) | MySQL, PostgreSQL, Redis | TypeScript, Tailwind CSS | DevOps
Specialty: Laravel & Vue.js full-stack development. This is my bread and butter, but I take on projects across the modern web stack.
AI Expertise: OpenAI, Anthropic, Google AI API integration, agent orchestration, AI-powered tools, web scraping & anti-bot techniques
Services: Custom development, SaaS architecture, performance optimization, API development, legacy app modernization, project rescue, fractional CTO, technical team leadership
Résumé/CV: https://t1p.de/aofx0
Email: see profile
15+ years building web applications. Former founder of SaaS startup, ecommerce marketplace, and high-traffic blog network. I ship working software and understand what makes a product viable.
vincent_s commented on AI Exponentializes Your Tech Debt vincentschmalbach.com/ai-... · Posted by u/vincent_s
This is so not a problem.
After a long stretch of I just ask codex to: Audit the code base and event changes and describe the data model and all related and possibly overlapping functions.
Plan a new redesign that is simpler, has less code, more reuse and cleaner design,
Execute the refactor Review the code and asses new code and reaudit
… repeat
You can queue these up in codex and it will just go about its way reducing your tech debt way faster than an engineer could.
I think this might work for smaller codebases, but the main point of my article isn't really about vibe coding. Vibe coded apps are typically smaller anyway, so refactoring isn't that big of an issue there.
When we're talking about actual software that has been around for a while and has accumulated serious tech debt, it's not so easy. I've definitely worked on apps where your described approach doesn't lead to anything viable. It's just too much for an AI to grasp when you have years of accumulated complexity, dependencies, and business logic spread across a large codebase.
Regarding vibe coders specifically: I think people who can't code themselves often don't really know what "cleaner design" or "more reuse" actually means in practice. They can certainly learn, but once they do, they're probably not vibe coders anymore.
Full Stack Developer & AI Engineer with 15+ YoE. Laravel/Vue.js specialist who also builds with React, Next.js, Python (Django/FastAPI), and Node.js.
I develop SaaS applications, integrate AI (OpenAI/Anthropic/Google APIs, agent orchestration), and rescue struggling projects. Background as a founder (SaaS, ecommerce, high-traffic blogs) means I understand business, not just code.
Available for long-term contracts (20+ hours/week), project-based work, fractional CTO roles, and technical consulting.
Core Stack: Laravel, Vue.js, PHP, Inertia.js, Tailwind | Also: React, Next.js, Python, Node.js, TypeScript | DevOps
AI: OpenAI, Anthropic, Google AI APIs, agent orchestration, web scraping
Website: https://t1p.de/rqox2
Email: see profile