Notes that come out of my own products.
Short pieces on infrastructure decisions, store releases, AI-assisted development and product scope. All of it comes from work I actually ran — not generic summaries.
From reading to application.
The writing is first-hand technical evidence; these pages show the service, capability and working-system layer behind the same topics.
Read a topic in order.
No part-list clutter inside the card. The series page owns reading order and every part.
Building Products with AI
From vibe coding and agent orchestration to production Lovable workflows and real AI integration: keeping product and architecture control while moving faster.
From Prototype to Production
Turning a working MVP into a dependable product: production checks, modular refactoring, data migration, audits, rewrite decisions and release gates.
SaaS Systems: Architecture, Cost and Simplicity
Field notes and decision frameworks connecting backend cost, cloud choices and product complexity as one systems problem.
FX and Cloud: Running SaaS from Turkey
Managing TRY revenue against USD/EUR infrastructure costs, global payments, cloud bills and pricing as one unit-economics system.
The Turkish Interface Problem
Where English-first product patterns break in Turkish: microcopy, suffixes, locale behavior, tone, KVKK and AI-assisted development.
Infrastructure Realities from Turkey
Field decisions for Turkey-focused SaaS: self-hosting vs cloud, local/global payments, CDN, DNS and real latency.
Problem Before Product
Diagnosing the real constraint, decision point and build contract before a feature request turns directly into implementation.
Architecture in the Wild
Field architecture through live state, information, interaction and product-boundary decisions rather than abstract diagrams.
Rescue & Ownership
Production rescue through root-cause diagnosis, release reality and operational ownership instead of repeated symptom patches.
Evidence Engineering
Connecting claims to working products, sourceable scope, architecture decisions, release traces and verifiable outcomes.
Notes that stand on their own.
Direct notes on products, information architecture, infrastructure and ways of working.
- ENTRY-009Product decisionsWhat is Rail? Capturing notes, tasks and decisions without leaving your Windows workflowRail is a Windows edge workspace for capturing notes, tasks and decisions without switching away from the application you are already using.
- ENTRY-042Release & operationsReader question: can you sell SaaS from Turkey without Stripe?Yes. Separate seller role, payment collection, tax handling, payouts and entitlements instead of looking for a simple Stripe clone.
- ENTRY-041InfrastructureShort note: five SaaS metrics I check after an FX moveSeparate exchange-rate impact from usage and architecture changes before repricing.
- ENTRY-040Release & operationsInternational SaaS launch checklist from TurkeyA global landing page is not a global operating system. Payments, accounting, entitlements, support and compliance must work together.
- ENTRY-039Release & operationsKVKK checklist before launching a SaaS in TurkeyA privacy-policy page is not enough; real data flows, disclosure, consent, deletion and security processes must match.
- ENTRY-038Product decisionsNext.js or TanStack? A decision tree based on product needsChoose from rendering, backend boundaries and deployment requirements instead of popularity.
- ENTRY-037InfrastructureA one-day build log: moving CI/CD from GitHub Actions to CloudflareChanging deployment providers is not just editing YAML; source of truth, build contracts and environment boundaries must stay explicit.
- ENTRY-036InfrastructureWhy I did not deploy Kubernetes for a solo SaaSA powerful technology can still be the wrong answer when its operational surface is larger than the problem it solves.
- ENTRY-035AI workflowLovable vs v0 vs Bolt: a Turkish-prompt benchmark protocolUse the same Turkish brief and repeatable scoring criteria instead of declaring a winner from demo impressions.
- IA-001Information architectureHow do you manage a category network covering 300,000 books?At scale, information architecture is not a naming exercise. It is a system for keeping classification decisions consistent across people, review and quality control.
- REVERSE-001Product decisionsWhy does Linear feel fast?A proof-led decomposition of Linear's creation, context preservation, keyboard, search and editing behavior without copying screens.
- ENTRY-024AI workflowFrom Notion and Obsidian to Agents: Building Context Architecture for AIDesigning a context system that keeps product truth, code reality, decisions and operating rules authoritative and fresh for AI agents.
- ENTRY-023Release & operationsFrom PWA and Web to Mobile Stores: Managing Multiple Platforms from One CodebaseA practical architecture for sharing a product core across web, PWA and native stores while containing platform-specific behavior and release risk.
- ENTRY-022Product decisionsGame Mechanics in SaaS Product Design: XP, Quests and Systemic HabitsDesigning gamification as a behavioral system rather than a layer of points, badges and confetti.
- ENTRY-008Product decisionsHow I make product decisions from idea to working SaaSA good MVP is not a product with few features. It is the smallest reliable system that tests the most important assumption.
- ENTRY-006Product decisionsHow I keep the system simple while building several products aloneRunning multiple products needs fewer exceptions, clearer priorities and one source of truth — not more tools.
- ENTRY-005Release & operationsWhat it actually takes to ship a product on Google PlayProducing an Android bundle is the easy part. A real release is identity, policy, testing, store data, version discipline and production acceptance.
- ENTRY-004Product decisionsWhy dashboard freedom is not always good UXGiving users the right to change everything does not always make them freer. Sometimes it simply gives them another system to manage.