AI · every day

I build with AI every day.

Not hype, not a demo reel — a power tool I reach for every day. It writes code beside me, and it ships as real features inside the products I build. Here is exactly how, where, and the rules I keep it on.

  1. 1Framea sharp prompt
  2. 2DraftAI proposes
  3. 3VerifyI review every line
  4. 4Shipto production
  5. 5Measurekeep or cut
My AI loop AI does the typing — I own every decision
How I use it

Four ways AI earns its place

Same tool, four very different jobs — from writing code beside me to features your users actually touch.

As a pair engineer

Claude Code sits in my terminal as a second senior engineer — it reads the whole repo, writes to my conventions, and never tires of the boring parts.

What it does
  • Scaffolds features, refactors, and framework migrations
  • Writes tests and reproduces bugs from a stack trace
  • Reviews diffs and explains unfamiliar code
  • Automates the repetitive — codemods, config, glue
What I get
  • Days instead of weeks on mechanical work
  • More time on architecture and the hard calls
Claude CodeRefactorsTestsReviews

AI inside the product

The AI users actually touch — search that understands meaning, assistants that answer from your data, calls turned into text and scored.

What I build
  • RAG & semantic search over your content
  • LLM features: assistants, scoring, parsing, extraction
  • Speech-to-text with speaker separation
  • Grounding checks so answers stay backed by sources
What you get
  • Features that feel smart, not gimmicky
  • AI that does a job — measurable, not a demo
RAGEmbeddingspgvectorLLM

Content & media, faster

AI clears the blank page. Copy in three languages, social images, video — all produced inside the same visual system, not off-brand slop.

What it does
  • Multilingual copy & SEO (EN / ES / UK)
  • OG images and brand visuals generated to spec
  • Showreels and short video from a script
  • This very page — drafted, then hand-finished
What I get
  • A blank page is never the bottleneck
  • On-brand output, produced in hours
CopyOG imagesVideoi18n

Automation of the boring

The repetitive back-office work that used to eat hours — handed to small, reliable AI jobs that run themselves.

What I automate
  • Ad-copy generation and bid rules (Google Ads)
  • Lead routing to Telegram / WhatsApp / email
  • Internal tooling and one-off data jobs
  • A team AI Hub so wins get reused, not rebuilt
What you get
  • Hours back every week
  • Fewer manual, error-prone steps
AutomationGoogle AdsTooling
In production

AI I have actually shipped

Not slideware — real AI features running in production today. Follow any of them to the code or the live build.

1
Speech + scoring
CallLens

Sales calls turned into coaching — speaker-diarized transcription, an LLM scorecard with quoted evidence, and every call semantically searchable.

  • Deepgram speech-to-text with speaker separation
  • LLM scores each rep against a configurable scorecard
  • pgvector embeddings for meaning-based search
SymfonyDeepgramOpenAIpgvectorRepo + live
2
Hybrid RAG
Polylog

A multi-agent chatbot SaaS with hybrid RAG (BM25 + dense + RRF) and a grounding verifier that blocks ungrounded answers.

  • bge-m3 embeddings on Elasticsearch
  • FastAPI backend, Next.js dashboard
  • A grounding verifier gates every answer
FastAPIRAGElasticsearchLive
3
AI planner
TripsQuick

A multilingual travel platform with an AI trip planner and semantic search over destinations.

  • Elasticsearch semantic search
  • AI itinerary + GraphHopper route optimization
  • Next.js web + React Native app
Next.jsAIElasticsearchLive
4
AI assistant
Rybalka Club

A fishing community with an AI assistant that answers any fishing question, grounded in the handbook.

  • e5-large embeddings for semantic search + RAG
  • Elasticsearch as the only datastore
  • Next.js + Symfony
Next.jsEmbeddingsRAGLive
Guardrails

How I keep it honest

AI is powerful and confidently wrong in equal measure. These are the rules that keep it useful in production.

Human in the loop

AI writes the draft; I read every line before it ships. I own the decision, always.

Outcomes, not demos

If it doesn’t remove a real bottleneck or move a number, it doesn’t ship. Cool is not a reason.

Ground everything

Answers stay tied to sources. A grounding check beats a confident hallucination every time.

The win is often deleting AI

Sometimes a static page or a simple rule beats a model. Killing a feature is a valid result.

Own the data, pin the models

Self-hosted where it matters, exact model versions pinned — no silent drift in production.

Fast to try, ruthless to cut

Prototype in a day, measure honestly, keep only what earns its place.

The stack

What I reach for

The models, retrieval, and plumbing behind the work above — chosen for production, not for a demo.

Models & agents
ClaudeGPT (OpenAI)GeminiClaude Code
Speech
Deepgramdiarization
Retrieval
bge-m3e5-largepgvectorElasticsearch kNNRRF hybrid
Orchestration
Symfony MessengerFastAPISymfony WorkflowRedis queues

Let’s put AI to work.

An AI feature, a RAG system, or a workflow you want automated — tell me the problem and I’ll tell you honestly whether AI is the right tool.

© 2026 Vitalii KindrakevychBuilt in Cartagena · Available worldwideBack to home