<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Nikolai Skavinskii — Blog</title>
    <link>https://nikska.com/blog</link>
    <atom:link href="https://nikska.com/feed.xml" rel="self" type="application/rss+xml" />
    <description>Notes on building products that people love.</description>
    <language>en-us</language>
    <item>
      <title>How I write with LLMs (it's not faster, it's just different)</title>
      <link>https://nikska.com/blog/writing-with-llms</link>
      <guid isPermaLink="true">https://nikska.com/blog/writing-with-llms</guid>
      <pubDate>Fri, 15 Aug 2025 12:00:00 GMT</pubDate>
      <dc:creator>Nikolai Skavinskii</dc:creator>
      <description>Voice-dump your ideas, let the LLM build a table of contents, then delete it and write the thing yourself. A process that produces more meaningful texts, not less.</description>
      <content:encoded><![CDATA[<blockquote>
<p><em>Originally posted on <a href="https://www.linkedin.com/in/nikska/">LinkedIn</a> in August 2025, back when GPT-5 and Claude 4.1 were the news of the day. Every word still stands.</em></p>
</blockquote>
<p><img src="https://nikska.com/blog/writing-with-llms.webp" alt="Using LLMs to write text — tips to keep your human voice"></p>
<p>GPT-5 is out, Claude 4.1 is here. Writing texts with them still sucks (unless you&#39;re okay with &quot;YOU&#39;RE ABSOLUTELY RIGHT!&quot;)</p>
<p>Here are my quick tips on how to write with LLMs.</p>
<p><strong>TL;DR — it&#39;s not faster, it&#39;s just different.</strong></p>
<p>Writing is a human task. Nature&#39;s <a href="https://www.nature.com/articles/s44222-025-00323-4">&quot;Writing is Thinking&quot;</a> kinda says it all.</p>
<p>With this off the table, how do I write with LLMs to avoid cringe and slop.</p>
<h2>🧠 Split the work by strengths</h2>
<p>Leverage the best in humans — expertise, wit, passion, and LLMs — speed, summarization, reasoning.</p>
<h2>🎙️ Talk, don&#39;t type</h2>
<p>Use voice mode and throw all your ideas on the topic into it. Do not care too much for the structure just yet. The most important part — talk to the machine (yes, use your vocal chords).</p>
<h2>🏗️ Ask for structure only</h2>
<p>Ask the LLM to produce only the structure, a Table of Contents.</p>
<h2>✍️ Read it... then delete it</h2>
<p>As counterintuitive as it sounds, you now have way more than 15 minutes ago when you just started. Let me explain:</p>
<ul>
<li>You spoke through the main points, which actually reinforced the best of your ideas and highlighted the weak parts way better than if you just typed them</li>
<li>You used the best feature of LLM — restructuring data. You&#39;re lucky if it made mistakes or allowed itself some inaccuracies — now you know what to avoid and how to write it better</li>
<li>And now you have a better understanding of the subject. Go on and write it down, make your own mistakes!</li>
</ul>
<h2>💫 Bonus: turn the LLM on your draft</h2>
<p>Send the final text to the same LLM and ask it two things:</p>
<ul>
<li>List some questions as if they were a member of your audience. What would they want to expand on?</li>
<li>List some harsh critiques from the standpoint of a nitpicky ICP. While this part is usually already pretty sloppy, some of the points GPT or Claude produces are quite useful.</li>
</ul>
<hr>
<p>Okay, this process might seem more lengthy. Because it is. But for me, it&#39;s way, way more engaging, and it allows me to produce more meaningful texts, not less. I still don&#39;t use LLMs to produce text anyone would read (if you catch me doing that, you&#39;re allowed to hit me in the knee.)</p>
<p>This post was written using this approach, and I even decided to pretend to be an LLM and place emojis here and there. Did I do a good job?</p>
]]></content:encoded>
    </item>
    <item>
      <title>AI-generated content on social media</title>
      <link>https://nikska.com/blog/ai-generated-content-on-social-media</link>
      <guid isPermaLink="true">https://nikska.com/blog/ai-generated-content-on-social-media</guid>
      <pubDate>Wed, 09 Apr 2025 12:00:00 GMT</pubDate>
      <dc:creator>Nikolai Skavinskii</dc:creator>
      <description>After running 3000+ AI agents on X, an inconvenient truth: if you need AI to communicate your ideas, your ideas are not worthy to communicate.</description>
      <content:encoded><![CDATA[<blockquote>
<p><em>Originally published on the <a href="https://www.linkedin.com/company/superposition-labs/">Superposition Labs</a> LinkedIn page on April 9, 2025.</em></p>
</blockquote>
<p><img src="https://nikska.com/blog/ai-content-social-media.webp" alt="AI-generated content on social media"></p>
<p>After weeks and months of talking to AI more than to real humans, I decided to embrace my writing style and language proficiency, and stop using any AI for writing or rewriting my thoughts.</p>
<p>Here&#39;s why.</p>
<h2>The sabbatical</h2>
<p>I had a long sabbatical from LinkedIn, during which I was having tremendous fun building AI agents and promoting them on X, mostly for the web3 crowd.</p>
<p>LinkedIn was already a swamp of slop and lazily AI-generated content back then, and it&#39;s even more so now (boy do comments here look horrible.)</p>
<p>I not only witnessed this cycle hyper-accelerated on X, but actually contributed in small part to it.</p>
<h2>From &quot;Newmarket&quot; to Memetic</h2>
<p>We started with the idea of AI agents as economic entities under the project codenamed &quot;Newmarket,&quot; and quickly realized that LLMs can&#39;t be trusted with either money, time or decisions in any combination. I will write a bit more on this later.</p>
<p>It was glaringly obvious that an AI agent is a set of building blocks for dynamic workflows, but most of them were utterly impossible to communicate with due to their pure synthetic nature and ever-present agreeableness.</p>
<p>That&#39;s cool and all, but that also led to incredibly easy attacks, and diminishing results, so together with Arsenii Zemskov we focused on AI agents that have personality, and we succeeded in that with the system we call Memetic. It ingests an X profile and creates a &quot;Reflection&quot; that mimics how the user interacts with others. The whole thing is rooted in our deep research on social media interactions that we were doing with Talkscan at Superposition Labs.</p>
<p>We then built tooling around this idea, and naturally, our agents started crawling X, engaging in conversations.</p>
<h2>The reply-bot flood</h2>
<p>That was really fun and innovative around October–November 2024, right around when a whole bunch of open-source frameworks were released to do almost exactly the same, but with a really sloppy way of initializing these agents (&quot;You are a software engineer who writes deep and thoughtful posts&quot; bla bla bla...)</p>
<p>Within weeks every X reply section flooded with automated content that made very little sense, and within 1–2 months most of those &quot;advanced reply bots&quot; were muted, banned and deplatformed. Some still stand. Now X is an even worse swamp of manipulated narrative and attention farming.</p>
<p>We moved on with Memetic to building synthetic audiences, as we discovered that the way we initialize and build Reflections gives them a set of unique abilities for market and product research.</p>
<h2>Why did we pivot then?</h2>
<p>We created more than 3000 agents that were running day in and day out, and we learned an inconvenient truth for proponents of the write-with-AI approach.</p>
<p><strong>If you need AI to communicate your ideas, your ideas are not worthy to communicate.</strong> Even less so to read by other humans. If your message is written and published by AI then you are redundant, and anyone can get the same text content from Claude 3.7 Sonnet.</p>
<p>Every kind of automated outreach is glaringly inauthentic, and it mostly feeds the Dead Internet theory.</p>
<h2>Still an AI enthusiast</h2>
<p>Don&#39;t get me wrong, I am still an AI enthusiast. I share tremendous excitement and chilling fears as to what are the next steps for human interactions in the AI-first world. AI is awesome at optimizing workflows, at generating stunning images and processing them. But reading text that was generated by a push of a button is beyond redundant.</p>
<p>Humans develop AI text fatigue incredibly fast, and I find it incredibly hard to justify investing even $20/month for a service that writes tweets on my or someone else&#39;s behalf. That is why I am not using AI for any texts that I publish, even though I am far from being fluent in English.</p>
<p>I have a serious gripe on &quot;AI Avatars&quot; precisely on the same grounds. But this is a writing for the future.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Proof of Humanity</title>
      <link>https://nikska.com/blog/proof-of-humanity</link>
      <guid isPermaLink="true">https://nikska.com/blog/proof-of-humanity</guid>
      <pubDate>Mon, 28 Oct 2024 12:00:00 GMT</pubDate>
      <dc:creator>Nikolai Skavinskii</dc:creator>
      <description>I showed a Bongard problem to my five-year-old daughter. Her answer was better than mine — and a reminder of what unfettered human intelligence looks like.</description>
      <content:encoded><![CDATA[<blockquote>
<p><em>Originally posted on <a href="https://www.linkedin.com/in/nikska/">LinkedIn</a> in October 2024.</em></p>
</blockquote>
<p>Working with AI models and, especially, agents calls for robust benchmarks to evaluate their capabilities. Many of you are likely familiar with the <a href="https://arcprize.org/">Abstraction and Reasoning Corpus (ARC) Challenge</a>, which has become a popular way to benchmark AI models.</p>
<p>As this test is quite hard for SoTA models, I use it regularly to prove to myself that I&#39;m still human.</p>
<h2>The Bongard Problems</h2>
<p>Recently, Arsenii Zemskov brought an old but fascinating test back into the spotlight: the Bongard Problems, collected by <a href="https://www.foundalis.com/res/diss_research.html">Harry Foundalis</a>.</p>
<p>The Bongard Problems present two sets of shapes, and your goal is to describe what is characteristic of each set so you can discern the two groups. These problems predate the ARC Challenge, and it strikes me how visionary thinkers were, conceptualizing such challenges decades ahead of their time.</p>
<h2>A five-year-old vs. problem 32</h2>
<p>I printed out a portion of the problem set. After working through a couple of pages, I decided to show them to my five-year-old daughter. I was curious about how she would perceive these problems, given that she hasn&#39;t been exposed to IQ tests or other early developmental assessments at her age.</p>
<p>Below is problem number 32. Take a moment to look at it and consider the difference between the two groups.</p>
<p><img src="https://nikska.com/blog/bongard-32.webp" alt="Bongard problem 32: two groups of six abstract line figures"></p>
<p>As someone with mathematical training, one might say: &quot;The figures on the left have sharp projecting angles, while the ones on the right do not.&quot;</p>
<p>However, my daughter&#39;s interpretation was beautifully different. Her solution:</p>
<blockquote>
<p>&quot;The ones on the left — you can see up in the sky. The ones on the right — you can see on the ground.&quot;</p>
</blockquote>
<h2>Fresh eyes</h2>
<p>This perspective was a powerful reminder that unfettered human intelligence, especially in children, offers profound and intuitive insights we adults might overlook. Children approach problems without the constraints and biases that we adults often carry.</p>
<p>In the realm of AI and complex models, it&#39;s easy to get lost in algorithms and data. But moments like these remind me that human intelligence, in its purest form, is a true source of inspiration.</p>
<p>Perhaps, as humanity continues to develop advanced AI, it should strive to preserve and emulate that childlike wonder and unbounded creativity. After all, the most profound insights often come from seeing the world through fresh eyes.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
