<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Egor Kravchenko — Blog</title><description>Egor Kravchenko — senior full-stack &amp; mobile engineer building production systems for operationally complex, regulated workflows (fintech to healthcare), with practical AI woven in.</description><link>https://egorkravchenko.com</link><item><title>How I stopped re-explaining the project to every AI agent</title><link>https://egorkravchenko.com/blog/ai-agents-knowledge-base</link><guid isPermaLink="true">https://egorkravchenko.com/blog/ai-agents-knowledge-base</guid><description>Decisions lived in chats, then in two docs folders, then in one knowledge base that Claude Code searches by meaning. The episode that convinced me, and the rule that came with it: a found note is a claim, not a fact.</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><media:content medium="image" url="https://egorkravchenko.com/images/og/posts/ai-agents-knowledge-base.png"/><category>ai</category></item><item><title>Four AI reviewers, one schema, and a fix I reverted</title><link>https://egorkravchenko.com/blog/four-ai-reviewers-one-schema</link><guid isPermaLink="true">https://egorkravchenko.com/blog/four-ai-reviewers-one-schema</guid><description>I had four models audit the same Prisma schema twice each, verified every claim by script, and still implemented a critical finding the application had already solved. What eight AI reviews are good for, and what they are not.</description><pubDate>Sun, 26 Jul 2026 00:00:00 GMT</pubDate><media:content medium="image" url="https://egorkravchenko.com/images/og/posts/four-ai-reviewers-one-schema.png"/><category>engineering</category><category>ai</category></item><item><title>Mapping a legacy Prisma schema without reliable telemetry</title><link>https://egorkravchenko.com/blog/mapping-a-legacy-schema</link><guid isPermaLink="true">https://egorkravchenko.com/blog/mapping-a-legacy-schema</guid><description>More than 150 models, legacy pages still in production, and traffic data I could not trust. How I worked out which models a limited set of functions actually depends on, where the script needed a human, and what the result does not prove.</description><pubDate>Sun, 05 Jul 2026 00:00:00 GMT</pubDate><media:content medium="image" url="https://egorkravchenko.com/images/og/posts/mapping-a-legacy-schema.png"/><category>engineering</category></item><item><title>I built an AI agent that knows me</title><link>https://egorkravchenko.com/blog/ai-agent-that-knows-me</link><guid isPermaLink="true">https://egorkravchenko.com/blog/ai-agent-that-knows-me</guid><description>A self-hosted AI agent with local embeddings, hybrid retrieval, and persistent memory over my own knowledge base — and why the hard part wasn&apos;t the model.</description><pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate><media:content medium="image" url="https://egorkravchenko.com/images/og/posts/ai-agent-that-knows-me.png"/><category>ai</category></item><item><title>Cutting a React Native app from 1.2GB to 350MB</title><link>https://egorkravchenko.com/blog/react-native-memory-700mb-to-350mb</link><guid isPermaLink="true">https://egorkravchenko.com/blog/react-native-memory-700mb-to-350mb</guid><description>My first mobile app started at 700MB, climbed past 1.2GB, and got OOM-killed on real devices. The full teardown of how it reached a stable 350MB — and why the real leak was the shape of the app, not a setting.</description><pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate><media:content medium="image" url="https://egorkravchenko.com/images/og/posts/react-native-memory-700mb-to-350mb.png"/><category>engineering</category></item></channel></rss>