<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mathias Nyola — Insights</title>
    <link>https://smosz.tselev.net/insights</link>
    <description>Original essays on product thinking, software engineering, AI, local reality, and practical digital systems by Mathias Nyola.</description>
    <language>en</language>
    <lastBuildDate>Sat, 24 Oct 2026 15:30:27 GMT</lastBuildDate>
    <atom:link href="https://smosz.tselev.net/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The problem must come before the technology</title>
      <link>https://smosz.tselev.net/insights/problem-before-technology</link>
      <guid isPermaLink="true">https://smosz.tselev.net/insights/problem-before-technology</guid>
      <pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate>
      <category>Product Thinking</category>
      <description>Why I start product work by understanding people, workflows and constraints before choosing the stack or designing the interface.</description>
    </item>
    <item>
      <title>Build systems people can actually use</title>
      <link>https://smosz.tselev.net/insights/build-systems-people-can-actually-use</link>
      <guid isPermaLink="true">https://smosz.tselev.net/insights/build-systems-people-can-actually-use</guid>
      <pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate>
      <category>Software Engineering</category>
      <description>A reflection on why useful software depends on usability, trust, maintenance and the realities of the people who use it every day.</description>
    </item>
    <item>
      <title>Local constraints are product requirements</title>
      <link>https://smosz.tselev.net/insights/local-constraints-are-product-requirements</link>
      <guid isPermaLink="true">https://smosz.tselev.net/insights/local-constraints-are-product-requirements</guid>
      <pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate>
      <category>Local Technology</category>
      <description>Connectivity, devices, cost, language and support capacity are not side issues. They are part of the product brief.</description>
    </item>
    <item>
      <title>A software engineer must learn to listen</title>
      <link>https://smosz.tselev.net/insights/software-engineer-must-learn-to-listen</link>
      <guid isPermaLink="true">https://smosz.tselev.net/insights/software-engineer-must-learn-to-listen</guid>
      <pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate>
      <category>Engineering Practice</category>
      <description>Technical skill matters, but listening is what helps an engineer understand what the code is really supposed to serve.</description>
    </item>
    <item>
      <title>An MVP is a promise, not a shortcut</title>
      <link>https://smosz.tselev.net/insights/mvp-is-promise-not-shortcut</link>
      <guid isPermaLink="true">https://smosz.tselev.net/insights/mvp-is-promise-not-shortcut</guid>
      <pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate>
      <category>Product Building</category>
      <description>Minimum viable products should reduce scope, not responsibility. Small products still need trust, clarity and care.</description>
    </item>
    <item>
      <title>AI should serve local reality</title>
      <link>https://smosz.tselev.net/insights/ai-should-serve-local-reality</link>
      <guid isPermaLink="true">https://smosz.tselev.net/insights/ai-should-serve-local-reality</guid>
      <pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate>
      <category>AI</category>
      <description>AI becomes more meaningful when it is shaped around real people, local languages, practical workflows and responsible product decisions.</description>
    </item>
  </channel>
</rss>