<?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/">
  <channel>
    <title>Forem: Artem</title>
    <description>The latest articles on Forem by Artem (@artemdev_).</description>
    <link>https://forem.com/artemdev_</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3399299%2F65e69b97-ee12-4158-a5ed-a1bd6dcb7050.webp</url>
      <title>Forem: Artem</title>
      <link>https://forem.com/artemdev_</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/artemdev_"/>
    <language>en</language>
    <item>
      <title>There’s a strange gap in web development.</title>
      <dc:creator>Artem</dc:creator>
      <pubDate>Tue, 25 Nov 2025 17:42:12 +0000</pubDate>
      <link>https://forem.com/artemdev_/theres-a-strange-gap-in-web-development-57g7</link>
      <guid>https://forem.com/artemdev_/theres-a-strange-gap-in-web-development-57g7</guid>
      <description>&lt;p&gt;On one side, you’ve got the enterprise-grade developer depression kit: Next.js apps, AWS pipelines, API layers, auth flows, rate-limiting, deployments, and a dozen microservices no small business asked for.&lt;/p&gt;

&lt;p&gt;On the other side, you’ve got “we just need a landing page” landing pages — the tiny brochure sites that somehow still manage to generate 40 rounds of feedback and three different opinions on button size.&lt;/p&gt;

&lt;p&gt;Developers don’t want to touch these small sites because they turn into endless tweaks. Small businesses can’t justify paying thousands for something that should take minutes, not months. And freelancers get stuck between scope creep and clients who think a $200 budget includes a full rebrand and psychic guidance.&lt;/p&gt;

&lt;p&gt;So I built &lt;a href="//swiftlysite.com"&gt;swiftlysite.com&lt;/a&gt; to bridge the gap.&lt;/p&gt;

&lt;p&gt;It lets anyone generate a production-ready website just by writing a short description. No freelancers drowning in revisions. No devs resizing logos at midnight. No small business owners comparing twenty nearly identical proposals.&lt;/p&gt;

&lt;p&gt;Just text in, website out.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
      <category>programming</category>
    </item>
    <item>
      <title>Build an Interactive Dijkstra Pathfinding Tool with TypeScript + Canvas</title>
      <dc:creator>Artem</dc:creator>
      <pubDate>Thu, 31 Jul 2025 07:45:12 +0000</pubDate>
      <link>https://forem.com/artemdev_/build-an-interactive-dijkstra-pathfinding-tool-with-typescript-canvas-4c39</link>
      <guid>https://forem.com/artemdev_/build-an-interactive-dijkstra-pathfinding-tool-with-typescript-canvas-4c39</guid>
      <description>&lt;p&gt;&lt;a href="https://orthogonal-pathfinder-canvas-ts.vercel.app" rel="noopener noreferrer"&gt;Live Demo&lt;/a&gt;&lt;br&gt;
&lt;a href="https://github.com/artemdev9/orthogonal-pathfinder-canvas-ts" rel="noopener noreferrer"&gt;Github Repo&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Recently, I was approached by a company looking for a fast, visual way to calculate the shortest path between connected nodes — something they could eventually use to improve flowchart and diagram tooling.&lt;/p&gt;

&lt;p&gt;To explore this idea, I built an interactive Dijkstra pathfinding tool in the browser using TypeScript and the Canvas API. It lets you drag around two points, and it dynamically calculates the shortest orthogonal path in real-time using Dijkstra’s algorithm.&lt;/p&gt;

&lt;p&gt;This project helped me deeply understand the algorithm’s mechanics and also prototype how a visual, grid-based layout engine might work in production tools.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>algorithms</category>
      <category>typescript</category>
    </item>
  </channel>
</rss>
