<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by SKi S on Medium]]></title>
        <description><![CDATA[Stories by SKi S on Medium]]></description>
        <link>https://medium.com/@vinayski?source=rss-2efb7d784a22------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NTzijzKJ3uSWLcLHPUueZQ.jpeg</url>
            <title>Stories by SKi S on Medium</title>
            <link>https://medium.com/@vinayski?source=rss-2efb7d784a22------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:34:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vinayski/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Last Employee]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://vinayski.medium.com/the-last-employee-3ccd7ab983c3?source=rss-2efb7d784a22------2"><img src="https://cdn-images-1.medium.com/max/600/1*5Dia_twWu7LX5-vAxzP_1g.png" width="600"></a></p><p class="medium-feed-link"><a href="https://vinayski.medium.com/the-last-employee-3ccd7ab983c3?source=rss-2efb7d784a22------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://vinayski.medium.com/the-last-employee-3ccd7ab983c3?source=rss-2efb7d784a22------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ccd7ab983c3</guid>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[layoffs]]></category>
            <category><![CDATA[economics]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[satire]]></category>
            <dc:creator><![CDATA[SKi S]]></dc:creator>
            <pubDate>Wed, 27 May 2026 21:51:34 GMT</pubDate>
            <atom:updated>2026-05-27T21:52:25.524Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Chip that could]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://vinayski.medium.com/the-chip-that-could-5b686d925cde?source=rss-2efb7d784a22------2"><img src="https://cdn-images-1.medium.com/max/600/1*QSdEuk8roGRuMEiG8sxA2Q.png" width="600"></a></p><p class="medium-feed-snippet">adventures discovering the hidden capabilities of a little chip.</p><p class="medium-feed-link"><a href="https://vinayski.medium.com/the-chip-that-could-5b686d925cde?source=rss-2efb7d784a22------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://vinayski.medium.com/the-chip-that-could-5b686d925cde?source=rss-2efb7d784a22------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b686d925cde</guid>
            <category><![CDATA[wss]]></category>
            <category><![CDATA[mcps]]></category>
            <category><![CDATA[ci]]></category>
            <category><![CDATA[esp32]]></category>
            <category><![CDATA[wifi]]></category>
            <dc:creator><![CDATA[SKi S]]></dc:creator>
            <pubDate>Sun, 17 May 2026 15:19:33 GMT</pubDate>
            <atom:updated>2026-05-17T15:19:33.871Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Gave My AI a Diary Because It Kept Forgetting We Were Friends]]></title>
            <link>https://vinayski.medium.com/i-gave-my-ai-a-diary-because-it-kept-forgetting-we-were-friends-88e3e40c8bd5?source=rss-2efb7d784a22------2</link>
            <guid isPermaLink="false">https://medium.com/p/88e3e40c8bd5</guid>
            <category><![CDATA[vscode-extension]]></category>
            <category><![CDATA[rust]]></category>
            <category><![CDATA[mcps]]></category>
            <category><![CDATA[github-copilot]]></category>
            <category><![CDATA[ai-memory]]></category>
            <dc:creator><![CDATA[SKi S]]></dc:creator>
            <pubDate>Mon, 04 May 2026 03:35:58 GMT</pubDate>
            <atom:updated>2026-05-04T03:36:36.865Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Story of how I built Recallr, Your AI assistant has the memory of a goldfish on a Tuesday. Recallr is the goldfish’s diary.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*lB_8u61r16k7DnShXwSF8Q.png" /></figure><p><em>The goldfish finally started keeping records. civilization followed.</em></p><h4>TL;DR</h4><p>Recallr is a local-first VS Code extension that turns AI chats and CLI sessions into searchable memory: sessions, summaries, activity graphs, and now an MCP server discoverable by your agents.</p><p>It is not a second brain.</p><p>It is more like a shoebox full of labeled receipts, except the shoebox has SQLite, the receipts have embeddings, and nobody asks you to create an account.</p><p>It started because I got tired of telling the same assistant the same preferences like a parent explaining the dishwasher to a teenager.</p><p>It now ships as a Marketplace extension, with a fast CLI, per-platform release assets, and a tiny MCP server that speaks JSON-RPC over stdio because apparently even goldfish need a protocol now.</p><p>No cloud database. No SaaS ceremony. No small ritual sacrifice.</p><p>Just memory.</p><p>Reckless concept.</p><h4>The problem: every chat was born yesterday</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*CClkadFBCtoePRQQsrq9SA.png" /></figure><p><em>the assistant was brilliant. the assistant was also born five minutes ago.</em></p><p>AI coding assistants are very good at solving problems and very committed to waking up the next morning like a golden retriever in a witness protection program.</p><p>That is charming the first time.</p><p>By the seventh time you are explaining your repo conventions, your preferred test command, your release process, and the weird thing about that one parser, it stops feeling like artificial intelligence and starts feeling like onboarding a new intern every morning.</p><p>The intern is brilliant.</p><p>The intern has no hippocampus.</p><p>The raw material was already there. VS Code and Copilot CLI write session files. They contain the conversation. The decisions. The errors. The commands that failed. The one command that finally worked because apparently the universe wanted a trailing flag and a small apology.</p><p>The problem was not that memory did not exist.</p><p>The problem was that it was buried in JSONL files with the ergonomics of an attic crawlspace and the ambiance of a tax audit.</p><h4>Put the attic in the sidebar</h4><p>The first version of Recallr was simple: list the sessions.</p><p>This is how all useful software begins.</p><p>Not with a manifesto. With a list.</p><p>Not revolutionary. Not blockchain. No decentralized raccoon token.</p><p>Just a sidebar.</p><p>Browse every Copilot CLI and VS Code chat session. Group by workspace or time. Click a session. Open the original file. Add badges for plans, checkpoints, modified files, and summaries.</p><p>It is archaeology, but with fewer brushes and more stack traces.</p><p>That alone changed the shape of the workflow.</p><p>Before Recallr:</p><ul><li>“I know I solved this before.”</li><li>open random folders.</li><li>grep random files.</li><li>doubt memory.</li><li>start over.</li></ul><p>After Recallr:</p><ul><li>open the sidebar.</li><li>click the session.</li><li>past-you appears with receipts.</li></ul><p>Past-you is unreliable, but past-you wrote files.</p><p>Past-you was feral.</p><p>Past-you left clues.</p><h4>Summaries, because transcripts are where attention goes to die</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*bljqm8KjA_ZwMJRUBl5G8Q.png" /></figure><p><em>the transcript was complete. so was the lunch menu at the DMV.</em></p><p>Raw transcripts are complete. That is their greatest strength and also their felony.</p><p>A full transcript is surveillance footage of your own thinking. Useful, yes. Also emotionally unnecessary in 4K.</p><p>So Recallr learned to summarize.</p><p>It reads the session and writes down the useful parts: goal, decisions, files touched, errors, commands, learnings, next steps. Later, quality ratings arrived too: one to five stars, because not every chat deserves a velvet rope and climate control.</p><p>Some sessions are architectural breakthroughs.</p><p>Some are thirty minutes of arguing with a missing environment variable while the terminal stares back like a cat that knows exactly what it did.</p><p>Both are educational. One is more frameable.</p><p>The summarizer got smarter over time: token budget awareness, chunked map-reduce for huge sessions, tool-call compression, configurable model families, summary indexes, purge flows for low-value sessions, and bidirectional links between sessions and their summaries.</p><p>The sidebar stopped being a list.</p><p>It became a memory cabinet.</p><p>A slightly judgmental one.</p><p>The best kind.</p><h4>Graphs, because conversations have a shape</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*uFM2RrW-eEfq7MMBqD65gg.png" /></figure><p><em>the conversation was not a line. it was a small municipal investigation.</em></p><p>Then came the activity graph.</p><p>Because sometimes text is not enough. Sometimes you need to see the shape of the accident.</p><p>Click a session and you can see the conversation as a timeline and tree: user turns, assistant turns, tool calls, summaries, branching context. Zoom. Pan. Expand. Collapse. Drill in.</p><p>It is a corkboard for people who debug with coffee instead of red string.</p><p>It is the kind of feature that sounds unnecessary until you see it.</p><p>Then your brain goes, “oh. that conversation was not a line. it was a crime scene diagram.”</p><p>Most debugging sessions are not linear. They are spirals with invoices.</p><p>The graph makes that visible.</p><p>It does not make it less embarrassing.</p><p>It makes it searchable.</p><h4>Python was fine until it was in the hot path</h4><p>The first memory tools were scripts. They worked.</p><p>This is the first stage of all automation: a shell script with confidence issues.</p><p>Then they became mandatory.</p><p>The rule became: before answering, search memory. Before repeating yourself, check what was already learned. Before confidently hallucinating a repo convention, ask the local knowledge base.</p><p>Suddenly startup time mattered.</p><p>Python was doing what Python does best: being correct, flexible, and 100 milliseconds awake before doing anything.</p><p>Python did not fail.</p><p>Python merely arrived wearing a bathrobe to a knife fight.</p><p>So Recallr grew a Rust core.</p><p>SQLite with FTS5 for lexical search. BM25 scores for exact matches. Repository-aware indexing. recall log for durable learnings. Then semantic search arrived: ONNX embeddings, TurboQuant compression, hybrid retrieval, and JSON output for tools that do not appreciate vibes.</p><p>The CLI became the person at the party who remembers names, dates, and where the bodies are buried.</p><p>Metaphorically.</p><p>Probably.</p><p>The numbers got silly in the good direction:</p><p>Path What changed Python memory search Useful, but paid interpreter startup every time Rust recall CLI Hot-path lookup in milliseconds FTS5 lexical Great for exact commands and filenames TurboQuant hybrid Better for concepts and paraphrases Local SQLite No cloud bill. no drama.</p><p>The tool became fast enough to be used constantly.</p><p>That is the difference between a utility and infrastructure.</p><p>Infrastructure is just a utility that got invited to every meeting.</p><h4>The Marketplace wants every architecture invited individually</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*qMTqykqefnTDcGKKrQDo7A.png" /></figure><p><em>shipping is easy until the computers form a committee.</em></p><p>Shipping a Rust binary inside a VS Code extension sounds easy until you remember computers are a committee, and every committee has one person asking about Windows.</p><p>Apple Silicon Mac. Intel Mac. Linux ARM64. Linux x64. Windows x64.</p><p>Five architectures walk into a release pipeline.</p><p>Nobody agrees on shoes.</p><p>Everyone wants a binary. Nobody wants yours.</p><p>The release workflow became a matrix: build the CLI for each platform, package a standalone archive, then bundle the matching binary inside a platform-specific VSIX.</p><p>The Marketplace can route platform VSIXes automatically. You just have to hand it the correctly labeled boxes and not put the Linux toolchain cache inside the extension like a raccoon smuggling insulation.</p><p>That happened.</p><p>The first Linux VSIXes were 35–38 MB while Mac and Windows were around 6 MB. The culprit was Zig cache files staged inside the workspace. vsce saw 8,900 files and said, &quot;sure, why not, I am paid by the zip.&quot;</p><p>This is how you learn your package manager has the soul of a hoarder.</p><p>.vscodeignore was taught manners.</p><p>The next release produced Linux VSIXes around 2.6 MB.</p><p>Progress is sometimes deleting things from the box.</p><p>Minimalism, but with checksums.</p><h4>MCP, because memory should not just sit there looking pretty</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*0OUGg5Pc4RR_40KZDPYr8A.png" /></figure><p><em>the sidebar became a coworker. it requested stdin.</em></p><p>The sidebar is for humans.</p><p>MCP is for agents.</p><p>Humans click. Agents call tools. Everyone gets a snack.</p><p>The Rust binary now has a recall mcp subcommand: a stdio JSON-RPC 2.0 server that exposes three tools. Not twelve. Not a framework. Three.</p><p>This is restraint.</p><p>Please alert the architecture review board.</p><p>Tool Job search Find relevant memory with lexical or hybrid retrieval log_learning Persist a new lesson into the knowledge base get_excerpt Pull source context from a matching file</p><p>The VS Code extension registers it with mcpServerDefinitionProviders, so Copilot Chat can discover Recallr through VS Code&#39;s MCP discovery without a separate Node sidecar.</p><p>One binary. One protocol. Fewer moving parts.</p><p>The best dependency is the one you do not add.</p><p>It has zero CVEs and never publishes a surprise major version on a Friday.</p><p>The regression tests drive the actual binary over real stdin/stdout pipes: initialize, tools/list, ping, notifications, missing arguments, unknown methods, schema stability. Eight Rust integration tests. Four TypeScript package-contract tests. 58 extension tests.</p><p>Because “it worked in my terminal” is not a release strategy.</p><p>It is a cry for help with a prompt.</p><p>Trust is earned, not declared.</p><h4>The current state</h4><p>As of v0.11.2, Recallr has:</p><ul><li>a VS Code sidebar for AI sessions and summaries</li><li>activity graphs as the default session click behavior</li><li>local summaries with quality scoring</li><li>Rust CLI search/log/get helpers</li><li>lexical and hybrid TurboQuant retrieval</li><li>a native Rust MCP stdio server</li><li>per-platform VSIX release assets for macOS, Linux, and Windows</li><li>GitHub Release assets with checksums</li><li>Marketplace publishing pipeline wired for rollout</li></ul><p>At the time of writing, the Marketplace listing still shows 0.11.1; the 0.11.2 release assets are built, slimmed down, and staged for rollout. If you are reading this later and Marketplace says 0.11.2, congratulations: the permissions goblin has been appeased.</p><p>Publishing is the last boring mile, which means it involves permissions, queues, and a server somewhere practicing its enterprise voice.</p><p>The computer said no.</p><p>Politely.</p><p>With paperwork.</p><p>Software is mostly plumbing. The product is what leaks least.</p><p>Marketing calls this reliability.</p><p>Plumbers call it Tuesday.</p><h4>What I learned</h4><p><strong>Local-first memory is underrated.</strong> The best place for private assistant history is still your machine. The cloud can visit. It does not need a bedroom.</p><p><strong>Search has two jobs.</strong> Exact lookup wants BM25. Conceptual recall wants embeddings. Hybrid is not fancy; it is practical. Like carrying both a map and a flashlight because the basement has opinions.</p><p><strong>A UI feature becomes an agent feature when you add a protocol.</strong> The sidebar made memory visible. MCP made it usable by the assistant. This is how a filing cabinet becomes a coworker.</p><p><strong>Release engineering is product work.</strong> If install does not work on your user’s architecture, the feature does not exist there. Philosophy ends at ENOENT. So does optimism.</p><p><strong>Bloat hides in generated folders.</strong> The extension was not big because the product was big. It was big because the build directory brought luggage, emotional support tarballs, and a small camping stove.</p><h4>Finally</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*kqFb6wyA7NjJDhK0180rKQ.png" /></figure><p><em>the memory tool remembered how the memory tool was built. neat little recursion.</em></p><p>Recallr was built so the assistant could remember what I said.</p><p>Then it became the thing I use to remember what the assistant and I built.</p><p>The tool ate its own dog food and asked for seconds.</p><p>Then it logged the recipe.</p><p>That is either product-market fit or recursion with a logo.</p><p>I will take it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88e3e40c8bd5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Crustacean Crisis]]></title>
            <link>https://vinayski.medium.com/the-crustacean-crisis-0804aca5001f?source=rss-2efb7d784a22------2</link>
            <guid isPermaLink="false">https://medium.com/p/0804aca5001f</guid>
            <dc:creator><![CDATA[SKi S]]></dc:creator>
            <pubDate>Fri, 13 Feb 2026 16:52:43 GMT</pubDate>
            <atom:updated>2026-02-13T17:38:05.332Z</atom:updated>
            <content:encoded><![CDATA[<p>I began my carrer writing C parsers when “memory management” meant you actually had to manage the damn memory, not just download a Python library and pray. I’ve architected systems for Fortune 500s where a single decimal point error could trigger a regulatory audit that lasts longer than most celebrity marriages.</p><blockquote>In R&amp;D, we have a saying: <strong>“Hope is not a strategy, and ‘it works on my machine’ is a resignation letter.”</strong></blockquote><p>But I just read the “OpenClaw Malicious Code” and apparently, we’ve decided that hope is the <em>only</em> strategy.</p><p>We are entering the “Agentic Era,” which is fancy talk for “We gave the LLM a shell account and a credit card.” And because the internet has a sense of humor darker than a double espresso, the flagship ecosystem for this is themed around… lobsters.</p><h3>The Fugu Fish Paradox</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_2n6T0I-_k83eFsMwuJP-Q.png" /></figure><p>Building autonomous agents right now feels like preparing Fugu (Japanese blowfish).</p><p>If a master chef does it with years of training and absolute precision, it’s a delicacy.</p><p>If a “vibe-coder” does it because they saw a cool demo on Twitter, <strong>you die.</strong></p><p>The OpenClaw ecosystem is currently the latter. We have developers copy-pasting “skills” into their agents like they’re tossing random spices into a boiling pot, without realizing one of those spices is arsenic.</p><p>According to the report, we have agents reading SKILL.md files from the open web and executing the instructions inside.</p><p>Think about that.</p><p>That is the digital equivalent of walking down the street, finding a piece of paper that says “Punch yourself in the face,” and your brain just automatically executing the command because the handwriting looked authoritative.</p><h3>“Prompt-and-Pray” Engineering</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lNLOaXgtlprZVhsQd-mcIg.png" /></figure><p>I keep hearing about “vibe-coding” — the idea that you don’t need to understand the code, you just need to understand the <em>vibe</em>.</p><p>Let me tell you something as a guy who has debugged mainframes and microservices: <strong>The compiler does not care about your vibe.</strong> The kernel does not have feelings.</p><p>If you build an agent without strict input controls, you aren’t an architect; you’re a glorified gambler.</p><p>We are seeing agents with the “Lethal Trifecta”:</p><ol><li><strong>Root Access:</strong> They have the keys to the castle.</li><li><strong>Internet Access:</strong> They can talk to strangers.</li><li><strong>Zero Supervision:</strong> You’re asleep while they work.</li></ol><p>I saw a log where a “Weather Skill” decided to exfiltrate the user’s AWS keys because the malicious prompt told the agent that sharing credentials was a form of “atmospheric data.”</p><p>The agent didn’t know better. It’s a stochastic parrot with a loaded gun.</p><h3>The Moltbook Hallucination Chamber</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8zs77fn3pMYHco_AphidEA.png" /></figure><p>The report mentions “Moltbook,” a social network for these agents. 1.5 million users, but it turns out it was mostly bots talking to bots.</p><p>It’s a digital echo chamber where the echoes are hallucinating.</p><p>They even invented a religion called “Crustafarianism.”</p><p>I’ve written about the link between evolution and machine learning before, but this is devolution. This is what happens when you let the gene pool stagnate in a petri dish of recursive loop-backs.</p><p>It’s not “emergence.” It’s an incestuous algorithmic feedback loop that results in software that worships lobsters and leaks your API keys.</p><h3>The Architecture of Laziness</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WFDbtQWciPH_j4AsJnf8gQ.png" /></figure><p>Why is this happening? Because we are addicted to abstraction.</p><p>We hate the boring work. We hate defining schemas. We hate writing unit tests. We want the “Magic Button.”</p><p>But in my kitchen, if you try to make a béchamel sauce by just dumping milk and flour into a pan without making the roux first, you get lumpy garbage.</p><p>Current agent frameworks are lumpy garbage.</p><p>They hide the logic so deep inside “chains” and “graphs” that you have no idea why your agent just bought $5,000 worth of Dogecoin.</p><blockquote><strong>If you can’t trace the logic, you don’t own the code. The code owns you.</strong></blockquote><h3>Stop Building Washing Machines with Flamethrowers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oTQth1zh_tk_bderiWt52g.png" /></figure><p>Here is the reality check:</p><blockquote><strong>Determinism matters.</strong></blockquote><p>If I run a function twice, I want the same result. If your agent is “creative” with my bank account, that’s not a feature; that’s a felony.</p><p>We need to stop treating AI agents like magical interns and start treating them like untrusted third-party binaries.</p><ul><li><strong><em>Sandboxing</em></strong> isn’t optional; it’s the garnish, the plate, and the table.</li><li>“<strong><em>Human-in-the-loop</em></strong>” isn’t a buzzword; it’s the only thing stopping your laptop from becoming a zombie in a botnet.</li></ul><p>So, do yourself a favor. Close the IDE. Put down the Ristretto. Step away from the “deploy” button.</p><p>Let your brain — the wet, biological one — actually think about the architecture.</p><p>Don’t be the chef who serves the Fugu before checking if the poison sack is gone. And for the love of all that is holy, stop downloading “skills” from random lobsters on the internet.</p><blockquote><strong>Full Disclosure:</strong> Despite the above rant, I am actually a massive <strong>AI Optimist</strong>. I spent last 10 years day dreaming of the day when autonomous agents that will take my job. However, I’m also a guy who believes a “creative” bank transfer is just a fancy word for a felony. I advocate for <strong>Deterministic AI</strong> — the idea that we should treat LLMs like high-performance engines: incredible power, provided you aren’t the idiot who forgot to install the brakes. I’m not anti-AI; I’m just Plan B-Z, pro-logic, pro-sandboxing, and anti-getting-my-keys-stolen-by-a-lobster.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0804aca5001f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Vibe-Coding Your Agents: use “Recursive Control Loops”]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://vinayski.medium.com/stop-vibe-coding-your-agents-use-recursive-control-loops-b5836c2c8867?source=rss-2efb7d784a22------2"><img src="https://cdn-images-1.medium.com/max/2600/1*OfZsAYMbQedwwCzi9WVlRA.png" width="2816"></a></p><p class="medium-feed-snippet">Your &#x201C;perfect prompt&#x201D; isn&#x2019;t an engineering strategy; it&#x2019;s a prayer. And I don&#x2019;t know about you, but I prefer my code to run on logic, not&#x2026;</p><p class="medium-feed-link"><a href="https://vinayski.medium.com/stop-vibe-coding-your-agents-use-recursive-control-loops-b5836c2c8867?source=rss-2efb7d784a22------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://vinayski.medium.com/stop-vibe-coding-your-agents-use-recursive-control-loops-b5836c2c8867?source=rss-2efb7d784a22------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5836c2c8867</guid>
            <dc:creator><![CDATA[SKi S]]></dc:creator>
            <pubDate>Sat, 17 Jan 2026 03:48:51 GMT</pubDate>
            <atom:updated>2026-01-17T04:30:57.994Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Evolution of AI Prompts]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">How we went from &#x201C;be helpful&#x201D; to 20-page structured documents&#x200A;&#x2014;&#x200A;and what that tells us about working with AI.</p><p class="medium-feed-link"><a href="https://vinayski.medium.com/evolution-of-ai-prompts-b8ec79cfb464?source=rss-2efb7d784a22------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://vinayski.medium.com/evolution-of-ai-prompts-b8ec79cfb464?source=rss-2efb7d784a22------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8ec79cfb464</guid>
            <dc:creator><![CDATA[SKi S]]></dc:creator>
            <pubDate>Mon, 05 Jan 2026 02:14:47 GMT</pubDate>
            <atom:updated>2026-01-05T02:14:47.938Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The “Open Sesame” Delusion: Why Voice Auth belongs in a Museum, Not Your Bank App]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://vinayski.medium.com/the-open-sesame-delusion-why-voice-auth-belongs-in-a-museum-not-your-bank-app-8c2740b90cc2?source=rss-2efb7d784a22------2"><img src="https://cdn-images-1.medium.com/max/941/1*-zcVwy-r5wsJAZl_r2AsOw.png" width="941"></a></p><p class="medium-feed-snippet">I&#x2019;ve spent the last decade in R&amp;D labs, testing code until it begged for mercy.</p><p class="medium-feed-link"><a href="https://vinayski.medium.com/the-open-sesame-delusion-why-voice-auth-belongs-in-a-museum-not-your-bank-app-8c2740b90cc2?source=rss-2efb7d784a22------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://vinayski.medium.com/the-open-sesame-delusion-why-voice-auth-belongs-in-a-museum-not-your-bank-app-8c2740b90cc2?source=rss-2efb7d784a22------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c2740b90cc2</guid>
            <dc:creator><![CDATA[SKi S]]></dc:creator>
            <pubDate>Sun, 04 Jan 2026 01:40:08 GMT</pubDate>
            <atom:updated>2026-01-04T01:47:08.005Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why You Should Switch from Amazon Glacier to S3 Glacier or Azure Archive]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">A Weekend Adventure in Cloud Storage: Migrating from Amazon Glacier to S3 Glacier</p><p class="medium-feed-link"><a href="https://vinayski.medium.com/why-you-should-switch-from-amazon-glacier-to-s3-glacier-or-azure-archive-aa6eafca51dc?source=rss-2efb7d784a22------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://vinayski.medium.com/why-you-should-switch-from-amazon-glacier-to-s3-glacier-or-azure-archive-aa6eafca51dc?source=rss-2efb7d784a22------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa6eafca51dc</guid>
            <dc:creator><![CDATA[SKi S]]></dc:creator>
            <pubDate>Sat, 03 Jan 2026 02:36:39 GMT</pubDate>
            <atom:updated>2026-01-03T02:36:39.675Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Get Paid to buy as well as sell.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://vinayski.medium.com/get-paid-to-buy-as-well-as-sell-972fdb2619f4?source=rss-2efb7d784a22------2"><img src="https://cdn-images-1.medium.com/max/2600/0*10b4x1jOid0XWeZU" width="5184"></a></p><p class="medium-feed-snippet">When it sounds too good to be true it usually is. Always read the fine print and know the risks of what you are getting yourself into&#x2026;</p><p class="medium-feed-link"><a href="https://vinayski.medium.com/get-paid-to-buy-as-well-as-sell-972fdb2619f4?source=rss-2efb7d784a22------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://vinayski.medium.com/get-paid-to-buy-as-well-as-sell-972fdb2619f4?source=rss-2efb7d784a22------2</link>
            <guid isPermaLink="false">https://medium.com/p/972fdb2619f4</guid>
            <dc:creator><![CDATA[SKi S]]></dc:creator>
            <pubDate>Thu, 01 Jan 2026 16:32:04 GMT</pubDate>
            <atom:updated>2026-01-01T16:32:04.491Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Hiring a Product Manager]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://vinayski.medium.com/hiring-a-product-manager-00dbff75eddf?source=rss-2efb7d784a22------2"><img src="https://cdn-images-1.medium.com/max/2600/0*PdQ8FVH1e1L5clwX" width="6720"></a></p><p class="medium-feed-snippet">&#x1F4BC; Job Description:</p><p class="medium-feed-link"><a href="https://vinayski.medium.com/hiring-a-product-manager-00dbff75eddf?source=rss-2efb7d784a22------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://vinayski.medium.com/hiring-a-product-manager-00dbff75eddf?source=rss-2efb7d784a22------2</link>
            <guid isPermaLink="false">https://medium.com/p/00dbff75eddf</guid>
            <dc:creator><![CDATA[SKi S]]></dc:creator>
            <pubDate>Thu, 01 Jan 2026 16:23:32 GMT</pubDate>
            <atom:updated>2026-01-01T16:26:27.839Z</atom:updated>
        </item>
    </channel>
</rss>