A blog.
Stop Using AI Like Autocomplete: 8 Hours to 45 Minutes
Stop using AI like autocomplete. The mindset shift that turns 8 hours of coding into 45 minutes of reviewing — and the AI modes most builders never touch.
OLVASD EL ▸CLAUDE.md Explained: The File That Prevents AI Mistakes
CLAUDE.md explained: the one file that prevents 90% of AI coding mistakes. What it is, exactly what goes in it, and how to start yours with just 5 rules.
OLVASD EL ▸Row-Level Security Explained for Non-Technical Founders
Row-level security explained for non-technical founders: the database feature that makes customer data leaks nearly impossible. The reason I sleep at night.
OLVASD EL ▸Multi-Tenancy Explained: One Database, 1,000 Customers
Multi-tenancy explained for non-technical founders: how one database serves 1,000 customers safely — and the one column every table needs from day one.
OLVASD EL ▸Database-First Case Study: Tables Before One Screen
A database-first case study: the whole database designed before one screen was built, no rebuilds since, and five UI overhauls with zero database changes.
OLVASD EL ▸Solopreneur Tech Stack: €3,250 Built €2M of Software
The exact solopreneur tech stack that built 11 products for €3,250 a year — Claude, Cursor, Supabase, Vercel. Full cost breakdown plus the honest catch.
OLVASD EL ▸Signs AI Is Confidently Wrong: 11 Red Flags in Your Code
The 11 signs AI is confidently wrong about your architecture: it sounds just as sure when it is wrong. Spot the red flags, then push back with a 4-step script.
OLVASD EL ▸You Are the Architect, AI Is the Builder
You are the architect, AI is the builder. The exact division of decisions — which calls are yours, which are AI's — and five moments you must push back.
OLVASD EL ▸Tech Terms for Founders: 25 You Need, in Plain English
The 25 tech terms for founders that cover most AI-building conversations — API, backend, migration, RLS — each in plain English with a real-world analogy.
OLVASD EL ▸Databases Explained for Non-Technical Founders
Databases explained for non-technical founders: if you can read a spreadsheet, you already understand tables — plus the one design rule that decides your SaaS.
OLVASD EL ▸How SaaS Works: A Simple Explanation for Founders
How SaaS works, explained simply with a restaurant analogy: frontend, backend, database, and API in plain English — so you can direct AI to build yours.
OLVASD EL ▸Do I Need to Learn to Code to Build a SaaS? No — Do This
Do I need to learn to code to build a SaaS? No. A login feature that cost €2,000-5,000 and 3 days now takes AI just 5 minutes. Learn to direct AI instead.
OLVASD EL ▸