<?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>DEV Community: Dejan Stajic</title>
    <description>The latest articles on DEV Community by Dejan Stajic (@dejan_stajic_28050c35cb79).</description>
    <link>https://dev.to/dejan_stajic_28050c35cb79</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4099764%2F90baa754-4a43-42da-af4d-4662bcb81ec0.jpg</url>
      <title>DEV Community: Dejan Stajic</title>
      <link>https://dev.to/dejan_stajic_28050c35cb79</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dejan_stajic_28050c35cb79"/>
    <language>en</language>
    <item>
      <title>I built a free seating chart maker that never uploads your guest list</title>
      <dc:creator>Dejan Stajic</dc:creator>
      <pubDate>Sun, 22 Nov 2026 19:08:29 +0000</pubDate>
      <link>https://dev.to/dejan_stajic_28050c35cb79/i-built-a-free-seating-chart-maker-that-never-uploads-your-guest-list-5gee</link>
      <guid>https://dev.to/dejan_stajic_28050c35cb79/i-built-a-free-seating-chart-maker-that-never-uploads-your-guest-list-5gee</guid>
      <description>&lt;p&gt;I'm Dejan. I built a free seating chart maker and I want to be upfront about that. This post is about why I kept the guest list in the browser, and how the tool actually works.&lt;/p&gt;

&lt;p&gt;Wedding and event seating is a messy puzzle: couples who should stay together, relatives who should not sit at the same table, meal counts for the caterer, and a floor plan you can print. Most tools I looked at want an account, or they upload the list to a server. I didn't want a guest list leaving the device at all.&lt;/p&gt;

&lt;p&gt;The tool is here: &lt;a href="https://dejoski.github.io/seating-chart-maker/" rel="noopener noreferrer"&gt;https://dejoski.github.io/seating-chart-maker/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It runs in the browser. There is no sign-up, no ads, and no guest limit. The list is stored only in the browser's local storage on that device and is never uploaded. If you need the chart on another device, use Backup (.json) and Restore.&lt;/p&gt;

&lt;p&gt;How I use it:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Paste people in, one name per line, or paste columns from a spreadsheet (Name, Group, Meal, Notes). Write couples as "Alex &amp;amp; Sam Lee" and plus-ones as "Jordan Park +1" so they stay linked.&lt;/li&gt;
&lt;li&gt;Set up tables. There are quick layouts (rounds of 8 or 10, long tables, a head table, classroom rows, pairs, pods, and U-shape), or you can add tables one at a time with 1–20 seats. Drag a table by its name bar to move it around the room.&lt;/li&gt;
&lt;li&gt;Add rules. Keep two people together or apart, and lock anyone whose seat is already decided.&lt;/li&gt;
&lt;li&gt;Auto-arrange, then fine-tune. Auto-arrange fills tables while respecting every rule it can, keeps couples together, and puts people from the same group near each other. Drag names to adjust. On a phone, tap a name, then tap a table.&lt;/li&gt;
&lt;li&gt;Export a PDF (floor plan, a by-table list, and an A–Z "find your seat" list), a PNG, or a caterer CSV with meals by table.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If the rules can't all be met, the tool keeps the arrangement with the fewest broken rules and lists each conflict in red, so you can add a table, change seat counts, or loosen a rule.&lt;/p&gt;

&lt;p&gt;Wedding, classroom, and event modes each keep their own chart, so switching modes doesn't overwrite anything. For more charts in the same mode, save a backup file for each one.&lt;/p&gt;

&lt;p&gt;That's the whole product: a free, no-account chart you can paste, arrange, and print, with the list staying on your machine. If you try it and something is awkward, I'd like to hear it in the comments.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>showdev</category>
      <category>javascript</category>
      <category>privacy</category>
    </item>
    <item>
      <title>I built a daily debugging puzzle to stop getting rusty</title>
      <dc:creator>Dejan Stajic</dc:creator>
      <pubDate>Sat, 29 Aug 2026 05:18:05 +0000</pubDate>
      <link>https://dev.to/dejan_stajic_28050c35cb79/i-built-a-daily-debugging-puzzle-to-stop-getting-rusty-j7h</link>
      <guid>https://dev.to/dejan_stajic_28050c35cb79/i-built-a-daily-debugging-puzzle-to-stop-getting-rusty-j7h</guid>
      <description>&lt;p&gt;I kept noticing I was faster at writing new code than at finding bugs in code I already had. That skill atrophies if you only ship features.&lt;/p&gt;

&lt;p&gt;So I built a small daily practice: a broken snippet, one bug, fix it. New challenge every day. Python, JavaScript, and TypeScript, beginner through advanced.&lt;/p&gt;

&lt;p&gt;The loop is simple. Open the challenge, read the code, reproduce the failure, patch it. No leaderboard pressure. Just reps.&lt;/p&gt;

&lt;p&gt;Today's is a Python greeting function. Other days are string concat, off-by-one, the usual stuff that actually shows up in review.&lt;/p&gt;

&lt;p&gt;Site: &lt;a href="https://debugger-zeta.vercel.app" rel="noopener noreferrer"&gt;https://debugger-zeta.vercel.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Stack is Next.js on Vercel. I want feedback on whether the bugs feel like real mistakes or too toy. If you try one, tell me which language and whether the difficulty labels are honest.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>python</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
