<?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: Muneer Alam</title>
    <description>The latest articles on DEV Community by Muneer Alam (@muneer320).</description>
    <link>https://dev.to/muneer320</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%2F3962059%2F932cd874-246e-41b1-afa0-4f4d8e7578d1.png</url>
      <title>DEV Community: Muneer Alam</title>
      <link>https://dev.to/muneer320</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/muneer320"/>
    <language>en</language>
    <item>
      <title>Every keyboard is a mechanical keyboard with Klicky</title>
      <dc:creator>Muneer Alam</dc:creator>
      <pubDate>Fri, 06 Nov 2026 03:41:17 +0000</pubDate>
      <link>https://dev.to/muneer320/i-wanted-keyboard-sounds-on-linux-then-i-fell-down-the-audio-stack-3b1d</link>
      <guid>https://dev.to/muneer320/i-wanted-keyboard-sounds-on-linux-then-i-fell-down-the-audio-stack-3b1d</guid>
      <description>&lt;p&gt;Somewhere under your keycaps lives Klicky. It is curious, a little mischievous, and very pleased that keyboards make sounds. One click catches its attention. A steady run of typing gives it a rhythm to follow. When you take a break, it curls up and enjoys the quiet too.&lt;/p&gt;

&lt;p&gt;The software behind that little creature is a Rust utility that gives ordinary typing a mechanical-keyboard voice on &lt;strong&gt;Linux, macOS and Windows&lt;/strong&gt;. Ten sound packs, a volume control, and native controls that fit your desktop. Most of the time, that is all you need to think about.&lt;/p&gt;

&lt;p&gt;Want to hear it before getting into the audio stack? &lt;a href="https://klicky.muneer320.tech/#demo" rel="noopener noreferrer"&gt;Watch the 45-second Klicky demo&lt;/a&gt;: three sound packs, from steady clicks to a quicker burst.&lt;/p&gt;

&lt;p&gt;Building it sent me considerably further down the stack.&lt;/p&gt;

&lt;h2&gt;
  
  
  I just wanted it on my own machine
&lt;/h2&gt;

&lt;p&gt;I first saw somebody using &lt;a href="https://github.com/Sauhard74/klicky" rel="noopener noreferrer"&gt;Sauhard Gupta&lt;/a&gt;’s original Klicky project on their Mac. I liked it and wanted to use it myself. There was one small problem: I was running Omarchy on Arch Linux.&lt;/p&gt;

&lt;p&gt;So I did what an engineer with some time on their hands does. I took the repo and started moulding it to work on my setup.&lt;/p&gt;

&lt;p&gt;First Omarchy. Then Linux more broadly. Then Windows. I kept adding to it, and it kept growing.&lt;/p&gt;

&lt;p&gt;The original macOS project already had good foundations: a Rust daemon, decoded sound caching, local socket commands and KeyEcho-compatible packs. Those are Sauhard’s contributions. My work grew around Linux input, audio buffering, normalization, desktop integration and packaging, followed by the Windows implementation and further macOS lifecycle work.&lt;/p&gt;

&lt;p&gt;I had found something I enjoyed and wanted it to fit the machine I actually used.&lt;/p&gt;

&lt;h2&gt;
  
  
  A voice ready before you press a key
&lt;/h2&gt;

&lt;p&gt;The obvious version of a keyboard-sound app is easy to describe: receive a keypress, find a sound, play it.&lt;/p&gt;

&lt;p&gt;The important detail is when each piece of work happens.&lt;/p&gt;

&lt;p&gt;Opening a file, decoding OGG audio and creating an output stream are things I don’t want between a keypress and its click. Klicky prepares the sounds when a pack loads. Each pack has one &lt;code&gt;sound.ogg&lt;/code&gt; recording and a &lt;code&gt;config.json&lt;/code&gt; map that identifies the slices for individual keys.&lt;/p&gt;

&lt;p&gt;Loading decodes the recording into PCM samples, prepares the slices, normalizes quiet ones and keeps them in shared buffers. A keypress then selects prepared audio for the already-running mixer. Several key sounds can overlap, so a new click does not have to wait for the previous one to finish.&lt;/p&gt;

&lt;p&gt;A small part of that preparation solved another very audible problem: some packs were much quieter than others. The normalization uses an 85% peak target and caps amplification at 6×. Here is the gain decision from &lt;a href="https://github.com/Muneer320/klicky/blob/edc6567e633ec83ec53848934bbb4741281e9596/src/soundpack.rs#L66" rel="noopener noreferrer"&gt;the sound loader&lt;/a&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight rust"&gt;&lt;code&gt;&lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;gain&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="no"&gt;TARGET_PEAK&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="n"&gt;peak&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;clamp&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mf"&gt;1.0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="no"&gt;MAX_NORMALIZATION_GAIN&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;gain&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="mf"&gt;1.0&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The function handles silent slices before this step. The lower bound leaves already-loud samples alone; the upper bound prevents an extremely quiet recording from getting an enormous boost. The useful architectural choice is that this work happens during preparation, rather than on every keypress.&lt;/p&gt;

&lt;h2&gt;
  
  
  The code was fast. The sound still felt late.
&lt;/h2&gt;

&lt;p&gt;An early Linux run recorded an average callback-to-mixer dispatch of &lt;strong&gt;0.241 ms&lt;/strong&gt; across 55 keypresses, with a p95 of &lt;strong&gt;0.56 ms&lt;/strong&gt;. That was a useful clue: the input handler was already handing sounds over quickly.&lt;/p&gt;

&lt;p&gt;Further along the path, the audio device had negotiated a buffer of &lt;strong&gt;1,102 frames at 44.1 kHz&lt;/strong&gt;. That works out to roughly &lt;strong&gt;25 ms&lt;/strong&gt;. A fast hand-off was feeding a much larger buffer.&lt;/p&gt;

&lt;p&gt;After the move to Rodio 0.22 and a smaller fixed-buffer request, the tested PipeWire route negotiated &lt;strong&gt;256 frames&lt;/strong&gt;, about &lt;strong&gt;5.8 ms&lt;/strong&gt;. The audible lag was gone or clearly reduced in that hardware check, and the stream stayed clean during normal typing.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft6zudr52f1lazwwf45mz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft6zudr52f1lazwwf45mz.png" alt="Earlier and revised negotiated Linux audio buffers: 1,102 frames is 25.0 ms and 256 frames is 5.8 ms at 44.1 kHz." width="800" height="407"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;These bars show calculated buffer durations. The dispatch figures describe the separate input-to-mixer step. &lt;a href="https://github.com/Muneer320/klicky/blob/edc6567e633ec83ec53848934bbb4741281e9596/docs/BENCHMARKS.md" rel="noopener noreferrer"&gt;Recorded environment and results&lt;/a&gt;.&lt;/em&gt; &lt;/p&gt;

&lt;p&gt;The Unix output setup tries 256 frames, then 512, then 1,024, then a device-selected fallback. Small buffers help responsiveness, but the application still needs to open a working stream on the user’s device.&lt;/p&gt;

&lt;p&gt;I carried the same debugging habit into Windows: inspect the actual output route, then sit down and type. Laptop speakers felt near-immediate and comfortable. AirPods had a noticeable delay. That was a useful reminder to include the device in the investigation instead of endlessly optimizing the quickest part of the program.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three desktops, three native edges
&lt;/h2&gt;

&lt;p&gt;The part that translates a physical keyboard into events depends on the operating system.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Platform&lt;/th&gt;
&lt;th&gt;Input&lt;/th&gt;
&lt;th&gt;Desktop integration&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Linux&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;evdev&lt;/code&gt;, below Wayland and X11&lt;/td&gt;
&lt;td&gt;systemd user service; Omarchy controls&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;macOS&lt;/td&gt;
&lt;td&gt;Native event taps&lt;/td&gt;
&lt;td&gt;launchd and a menu bar helper&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Windows&lt;/td&gt;
&lt;td&gt;Passive Raw Input on a dedicated thread&lt;/td&gt;
&lt;td&gt;Native tray app and console client&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Linux responds to initial key-down events and ignores releases and held-key repeats. Windows maintains repeat state per device. The adapters turn those platform events into the key names used by the packs.&lt;/p&gt;

&lt;p&gt;The sound data can be shared without making every operating system use an identical lifecycle. Linux and macOS keep their persistent Rodio output. Windows retains the Rodio mixer but uses a Windows-specific CPAL renderer and audio supervisor, including recovery when the output device changes.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7pq9x3h7h5fwtvh1rjq0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7pq9x3h7h5fwtvh1rjq0.png" alt="Linux and macOS input feed the Unix playback path; Windows Raw Input feeds its own coordinator and renderer. Both use shared prepared sound data and play through the operating-system audio stack." width="800" height="507"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;That separation let the Windows work grow without replacing an audio path that already worked on Linux and macOS. The shared part earns its place through actual common behaviour: pack definitions, decoding, slices and prepared audio.&lt;/p&gt;

&lt;h2&gt;
  
  
  A tiny tray menu can still get in the way
&lt;/h2&gt;

&lt;p&gt;A background utility needs more than a quick key handler. It also needs to stay pleasant while someone changes a sound pack, adjusts the volume or asks it to quit.&lt;/p&gt;

&lt;p&gt;On Windows, pack preparation and persistence run away from the input and audio callbacks. The tray submits controls asynchronously. A pack change is prepared and saved before it becomes active, rather than making the typing path wait for a file decode.&lt;/p&gt;

&lt;p&gt;The queues and active playback are bounded. During audio recovery, obsolete events are discarded so reconnecting a device does not play a burst of old typing. A second launch is supposed to find the existing owner instead of starting another engine with another tray icon.&lt;/p&gt;

&lt;p&gt;Some of the most useful feedback was much less abstract: “the volume didn’t change,” “there are two tray icons,” and “some keys went quiet.” Those reports sent the investigation through process ownership, control state and aggregate input/audio diagnostics. The diagnostics can distinguish dropped or stale events without storing typed text.&lt;/p&gt;

&lt;p&gt;The intermittent missing-sound report did not recur in later typing checks, so I closed it as not reproducible. The aggregate diagnostics remain available if it returns.&lt;/p&gt;

&lt;h2&gt;
  
  
  Leave room for a little personality
&lt;/h2&gt;

&lt;p&gt;I wanted the project to feel like the thing that made me want it in the first place: a small, enjoyable addition to an ordinary day at the keyboard.&lt;/p&gt;

&lt;p&gt;Klicky gives that feeling somewhere to live. The sound packs are its different voices. The illustrations suggest a little world under the keys. It is pleased when the typing gets going, and perfectly content when it stops.&lt;/p&gt;

&lt;p&gt;The actual controls remain familiar: choose a pack, set the volume, pause, resume, quit. The character can make the project welcoming while the settings still say exactly what they do.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fx8layagyx2rbg5fg4jb3.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fx8layagyx2rbg5fg4jb3.webp" alt="Klicky resting peacefully between stretches of typing." width="640" height="427"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it is now
&lt;/h2&gt;

&lt;p&gt;Klicky supports &lt;strong&gt;Linux, macOS and Windows 11 x64&lt;/strong&gt;. Linux has Debian/Arch packages and a source installer; macOS source setup includes the menu bar helper; Windows is available from the &lt;a href="https://apps.microsoft.com/detail/9NLVFX7T2X6Q" rel="noopener noreferrer"&gt;Microsoft Store&lt;/a&gt;, through Scoop, or as a standalone installer and portable ZIP, with native tray controls for sound packs, volume and Pause/Resume.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://klicky.muneer320.tech/guide.html#installation" rel="noopener noreferrer"&gt;installation guide&lt;/a&gt; covers each platform, including package-manager options and copy-and-run setup commands. On Windows, the Microsoft Store handles installation and updates. The separate standalone installer is unsigned; setup and security guidance are included in the guide.&lt;/p&gt;

&lt;p&gt;You can &lt;a href="https://klicky.muneer320.tech/" rel="noopener noreferrer"&gt;meet Klicky and listen to its ten sound packs&lt;/a&gt;, explore &lt;a href="https://github.com/Muneer320/klicky" rel="noopener noreferrer"&gt;the Rust source&lt;/a&gt;, browse the &lt;a href="https://github.com/Muneer320/klicky/releases" rel="noopener noreferrer"&gt;available releases&lt;/a&gt;, or read the &lt;a href="https://github.com/Muneer320/klicky/blob/master/docs/ARCHITECTURE.md" rel="noopener noreferrer"&gt;architecture guide&lt;/a&gt;. There is also a &lt;a href="https://muneer320.tech/projects/klicky/" rel="noopener noreferrer"&gt;longer Klicky case study&lt;/a&gt; on &lt;a href="https://muneer320.tech/" rel="noopener noreferrer"&gt;my portfolio&lt;/a&gt;, alongside my other projects.&lt;/p&gt;

&lt;p&gt;You can also find Klicky on &lt;a href="https://alternativeto.net/software/klicky/about/" rel="noopener noreferrer"&gt;AlternativeTo&lt;/a&gt; and &lt;a href="https://www.pitchhut.com/project/klicky" rel="noopener noreferrer"&gt;PitchHut&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;What began as “I want those clicks on my laptop” has involved input APIs, audio scheduling, concurrency, process ownership and packaging. The interaction on the other end is still wonderfully small: press a key, and Klicky answers.&lt;/p&gt;

&lt;p&gt;If you’ve built a tool where a tiny delay changed how it felt, I’d be interested to hear where the time turned out to be hiding.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Related reading: &lt;a href="https://dev.to/tuist/native-edges-principles-for-native-apps-with-a-shared-core-4ff1"&gt;Native edges: principles for native apps with a shared core&lt;/a&gt;, by Pedro Piñera Buendía, is a useful companion discussion of shared logic and native platform boundaries.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Drafted with AI assistance from my development work and project notes.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>rust</category>
      <category>opensource</category>
      <category>linux</category>
      <category>performance</category>
    </item>
    <item>
      <title>Three yeses, two living rooms, and one missing question</title>
      <dc:creator>Muneer Alam</dc:creator>
      <pubDate>Mon, 05 Oct 2026 03:28:18 +0000</pubDate>
      <link>https://dev.to/muneer320/three-yeses-two-living-rooms-and-one-missing-question-n8b</link>
      <guid>https://dev.to/muneer320/three-yeses-two-living-rooms-and-one-missing-question-n8b</guid>
      <description>&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;The One Missing Question&lt;/strong&gt; is a scrapbook-like page for the person who ends up coordinating every group plan. Paste a short chat, then get the messages that matter, the details still in the air, and one question you can edit and send.&lt;/p&gt;

&lt;p&gt;Take a board-game night in a busy group chat. Mira says Saturday is good. Jay can make it after 7. Noor can host, while Mira thought they were meeting at Jay's. Three people are interested, but there is still no agreed start time or venue. The friend organizing it needs one useful next message, not a confident summary of a plan nobody made.&lt;/p&gt;

&lt;p&gt;I built this around the friend who keeps the group chat moving when everyone is interested but nobody has agreed on the details. The built-in sample lets anyone try the flow without sharing a private conversation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://github.com/Muneer320/one-missing-question#run-locally" rel="noopener noreferrer"&gt;README&lt;/a&gt; has the local demo steps. Install Ollama and pull &lt;code&gt;gemma2:2b-instruct-q3_K_S&lt;/code&gt;, run &lt;code&gt;npm start&lt;/code&gt;, then click &lt;strong&gt;Try a sample chat&lt;/strong&gt; and &lt;strong&gt;Find the missing question&lt;/strong&gt;. The sample is included in the app.&lt;/p&gt;

&lt;p&gt;In one local run, the quote cards included “Mira: Saturday is good. I thought we were going to Jay's?” and “Noor: Any time after 6 works for me.” The open-details card said the time and place were still unclear. Gemma drafted:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Based on the chat, what time and place are we thinking for the game night this weekend?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I would tighten that before sending it: can everyone meet after 7, and should we go to Noor's or Jay's?&lt;/p&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/Muneer320/one-missing-question" rel="noopener noreferrer"&gt;The One Missing Question on GitHub&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The app is a small Node server and a dependency-free browser interface. Its Render Blueprint maps the page and API to a public web service and Ollama to a private service.&lt;/p&gt;

&lt;p&gt;That Blueprint is ready to deploy, but the Ollama service and its persistent disk require paid Render resources. I claimed the Hacktoberfest Render promo through MLH; Render's credits portal says the event has no codes in its pool yet and has saved my request. No credit was issued, so I could not use that promo to put the demo on Render. The local demo above runs the same app and Gemma model.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;The model receives the pasted chat and returns three fields in JSON: exact excerpts, open details, and one proposed question. The browser arranges these as paper notes. The user can edit the question before copying it.&lt;/p&gt;

&lt;p&gt;My first design asked Gemma to label details as agreed. That failed in a useful way. In one test case, a model called a venue confirmed even though the supporting message was phrased as a question. The quote was present in the input; the interpretation was wrong. An exact-match citation can prove the words appeared, but it cannot prove the group reached a decision.&lt;/p&gt;

&lt;p&gt;I changed the card from “Seems settled” to “What was said.” The server checks every excerpt against the pasted chat and drops any that cannot be found:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;quotes&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;raw&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;quotes&lt;/span&gt;
  &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;slice&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;4&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
  &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;((&lt;/span&gt;&lt;span class="nx"&gt;item&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nf"&gt;cleanText&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;item&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;220&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
  &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;filter&lt;/span&gt;&lt;span class="p"&gt;((&lt;/span&gt;&lt;span class="nx"&gt;quote&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nx"&gt;quote&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nx"&gt;source&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;quote&lt;/span&gt;&lt;span class="p"&gt;));&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The page no longer promotes a suggestion to a decision. Gemma still does the useful work of selecting relevant words and drafting the question; the person using the app remains the judge of what those words mean.&lt;/p&gt;

&lt;p&gt;The tested model is &lt;strong&gt;&lt;code&gt;gemma2:2b-instruct-q3_K_S&lt;/code&gt;&lt;/strong&gt; through Ollama. On my Windows laptop with an RTX 3050 6 GB GPU, one cold load plus answer took about &lt;strong&gt;72 seconds&lt;/strong&gt;; later short chats took about &lt;strong&gt;2–3 seconds&lt;/strong&gt; each. Those timings are local measurements, not a Render benchmark. The final five-case run returned valid structured responses in all five cases. It correctly surfaced Jay's conflict with the 10 am café plan and asked whether 11:30 worked. The edit to the game-night question above is part of the product, not a hidden fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;A planning chat can contain private names, places, and schedules. Running Gemma through Ollama means the same app can process that text on a laptop without sending it to a third-party model API. The model tag and runtime are configurable, which let me try Gemma 4, Gemma 3 1B, and compact Gemma 2 without rewriting the app. The smallest model missed important details; the larger one did not finish its cold start within my timeout. Gemma 2 gave the most useful local results in the lower-cost size range.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Best Use of Gemma&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where It Still Stumbles
&lt;/h2&gt;

&lt;p&gt;The model can still miss a conflict or ask a broad question when both time and place are unresolved. The app keeps its output editable and exposes the exact words it selected, so the organizer can tighten the question before sending it.&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>weekendchallenge</category>
      <category>hf26challenge</category>
      <category>gemma</category>
    </item>
    <item>
      <title>Python Tracebacks Tell You Where. Not Why. So I Built Something That Does Both.</title>
      <dc:creator>Muneer Alam</dc:creator>
      <pubDate>Sat, 04 Jul 2026 16:42:52 +0000</pubDate>
      <link>https://dev.to/muneer320/python-tracebacks-tell-you-where-not-why-so-i-built-something-that-does-both-39pp</link>
      <guid>https://dev.to/muneer320/python-tracebacks-tell-you-where-not-why-so-i-built-something-that-does-both-39pp</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkz5ccup7118gukg2fsa4.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkz5ccup7118gukg2fsa4.png" alt="Hero Banner" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;Friday, 11:47 PM. Production goes down.&lt;/p&gt;

&lt;p&gt;The alert says &lt;code&gt;KeyError: 'user_id'&lt;/code&gt;. The traceback points to line 42 of a file that has not changed in three months. You SSH in, tail the logs, and find nothing. No variable values. No request context. No path forward but to add a print statement, redeploy, and wait.&lt;/p&gt;

&lt;p&gt;Three hours later it happens again. You still do not know why.&lt;/p&gt;

&lt;p&gt;If you have written Python long enough, this sequence is familiar. The language gives you file names, line numbers, and function names. It leaves out the one thing you actually need: &lt;strong&gt;what the values were at the moment of failure&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Python's traceback module plays it safe. Capturing runtime state inside a crash handler risks a double fault. If the exception hook itself raises, CPython writes an error message and the original traceback is lost. So the standard library prints the stack and leaves frame locals untouched.&lt;/p&gt;

&lt;p&gt;We, as an ecosystem, have accepted this trade-off for decades.&lt;/p&gt;

&lt;p&gt;I recently built a tool to fix this. It is called Safedump. You install it in two lines:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;safedump&lt;/span&gt;
&lt;span class="n"&gt;safedump&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;install&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;When your application crashes, it captures every local variable, the full exception chain, and thread state. It saves this as structured JSON on your machine. Later, you inspect it with &lt;code&gt;safedump view&lt;/code&gt;. No cloud involved. No telemetry. No accounts.&lt;/p&gt;

&lt;p&gt;It is the missing layer between Python tracebacks and cloud crash reporting.&lt;/p&gt;




&lt;h2&gt;
  
  
  What a Traceback Actually Tells You
&lt;/h2&gt;

&lt;p&gt;Consider a real scenario. You are parsing user-submitted JSON:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;json&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;process_payment&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;dict&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;-&amp;gt;&lt;/span&gt; &lt;span class="nb"&gt;dict&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;user&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;user&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="n"&gt;amount&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;amount&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="n"&gt;currency&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;currency&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;USD&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;gateway&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;GATEWAYS&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;user&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;tier&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;]]&lt;/span&gt;  &lt;span class="c1"&gt;# this can fail
&lt;/span&gt;    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;gateway&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;charge&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;user&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;id&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt; &lt;span class="n"&gt;amount&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;currency&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The traceback when it crashes:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="nc"&gt;Traceback &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;most&lt;/span&gt; &lt;span class="n"&gt;recent&lt;/span&gt; &lt;span class="n"&gt;call&lt;/span&gt; &lt;span class="n"&gt;last&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
  &lt;span class="n"&gt;File&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;payments.py&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;line&lt;/span&gt; &lt;span class="mi"&gt;22&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;module&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="nf"&gt;process_payment&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;payload&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
  &lt;span class="n"&gt;File&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;payments.py&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;line&lt;/span&gt; &lt;span class="mi"&gt;8&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;process_payment&lt;/span&gt;
    &lt;span class="n"&gt;gateway&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;GATEWAYS&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;user&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;tier&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;]]&lt;/span&gt;
&lt;span class="nb"&gt;KeyError&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;premium_plus&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This tells you a &lt;code&gt;KeyError&lt;/code&gt; happened on line 8. The missing key was &lt;code&gt;premium_plus&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;What it does not tell you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What was &lt;code&gt;user["tier"]&lt;/code&gt;? &lt;code&gt;None&lt;/code&gt;? An empty string? A misspelled value?&lt;/li&gt;
&lt;li&gt;What was the full &lt;code&gt;data&lt;/code&gt; payload? Was &lt;code&gt;user&lt;/code&gt; even present?&lt;/li&gt;
&lt;li&gt;Which request triggered this? A specific customer or a random API scan?&lt;/li&gt;
&lt;li&gt;What did &lt;code&gt;GATEWAYS&lt;/code&gt; look like? Was &lt;code&gt;premium_plus&lt;/code&gt; supposed to be there?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each question requires a different technique. Add a log statement. Reproduce the input. Check CloudWatch. SSH into the box. By the time you have done all four, the incident timer has hit forty minutes.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Existing Tools Do Well
&lt;/h2&gt;

&lt;p&gt;The Python ecosystem has several tools that improve on the bare traceback. They deserve credit.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;code&gt;rich.traceback&lt;/code&gt;&lt;/strong&gt; makes tracebacks dramatically more readable with syntax highlighting and better formatting. If you are developing locally, it is a genuine quality-of-life improvement. But it is still terminal-only. It prints to stderr and disappears when the session ends.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;code&gt;stackprinter&lt;/code&gt;&lt;/strong&gt; goes further by showing source code context and local variable values. You can call &lt;code&gt;stackprinter.format()&lt;/code&gt; and get a string you can log. The output is plain text, readable anywhere but without structure. You cannot ask it what the value of &lt;code&gt;user&lt;/code&gt; was in frame 2.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sentry&lt;/strong&gt; is the most mature option. It captures exceptions, aggregates them, and handles the full monitoring lifecycle. It also captures frame locals. The trade-off is that it is cloud-dependent. Your data leaves your network and you need an account.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Rollbar&lt;/strong&gt; solves the same problem with a similar architecture. Useful, but the same constraint: your crash data lives on someone else's server.&lt;/p&gt;

&lt;p&gt;Each tool solves a real problem. But there is a gap between "make the terminal output prettier" and "ship your data to the cloud." Safedump sits in that gap.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why Not Just Use Logging?
&lt;/h3&gt;

&lt;p&gt;A common question: why not add &lt;code&gt;logger.exception()&lt;/code&gt; to your error handler?&lt;/p&gt;

&lt;p&gt;Logging captures a string. Safedump captures structured data. A log line requires parsing. A Safedump report is typed JSON ready for programmatic analysis. Logging also cannot redact secrets. If your log statement includes &lt;code&gt;password=request.form["password"]&lt;/code&gt;, that secret is in your aggregation system forever. Logging is essential for tracing application flow. But it is not designed for post-mortem crash analysis with full variable state.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Smallest Useful Crash Reporter
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqwatqouz272b7lbheqgg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqwatqouz272b7lbheqgg.png" alt="Safedump Terminal Output" width="800" height="491"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;When I started building this, one constraint drove everything: the crash handler must never crash. If capturing variable values makes the handler itself raise, CPython loses the original traceback entirely.&lt;/p&gt;

&lt;p&gt;I built something that separates capturing state from displaying it.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip &lt;span class="nb"&gt;install &lt;/span&gt;safedump
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;safedump&lt;/span&gt;
&lt;span class="n"&gt;safedump&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;install&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;When an unhandled exception occurs, you see two things. First, the original traceback, unchanged, so your existing workflows are not disrupted. Second:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Crash report saved: ~/.safedump/2026-06-25-19-48-11-ZeroDivisionError-a1b2c3.safedump.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Later, you inspect it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;safedump view
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The output shows the exception, every frame with local variables and their types, source code context, thread state, and environment metadata. Human-readable in the terminal and machine-parseable as JSON.&lt;/p&gt;

&lt;p&gt;You can also capture exceptions manually:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;try&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;result&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;dangerous_operation&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;span class="k"&gt;except&lt;/span&gt; &lt;span class="nb"&gt;Exception&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;path&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;safedump&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;capture_exception&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Crash captured: &lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;path&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;raise&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyznqggjfarn5dww9ef6o.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyznqggjfarn5dww9ef6o.png" alt="Workflow diagram" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  The Same Crash, Two Views
&lt;/h3&gt;

&lt;p&gt;Here is everything a standard traceback gives you from the earlier &lt;code&gt;KeyError&lt;/code&gt; example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;KeyError: 'premium_plus'
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Here is the same crash through a Safedump report. The report lives on disk as versioned JSON:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"safedump_version"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"1.0.0"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"timestamp"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"2026-06-25T19:48:11.000000"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"exception"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"KeyError"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"message"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"'premium_plus'"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"module"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"builtins"&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"frames"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"index"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"file"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"payments.py"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"line"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;8&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"function"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"process_payment"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"locals"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="nl"&gt;"user"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"dict"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"{'id': '...', 'tier': 'premium_plus', 'name': '...'}"&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="nl"&gt;"amount"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"int"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"2999"&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="nl"&gt;"currency"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"str"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"USD"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"redactions"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"location"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"process_payment.user.id"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"reason"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"variable_name_match"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"rule"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"DENYLIST_SUBSTRING: id"&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;[JSON Report Screenshot: Shows the reader what they get instead of a plain traceback. Structured, versioned JSON with a redaction audit trail.]&lt;/p&gt;

&lt;p&gt;With the standard traceback you have the exception type and message. With the report you have the exact value of &lt;code&gt;user["tier"]&lt;/code&gt;, the full payload context, thread state, and a redaction audit trail. You can answer every earlier question without reproducing the bug.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why the Name?
&lt;/h3&gt;

&lt;p&gt;Safedump combines two ideas: the report is &lt;strong&gt;safe&lt;/strong&gt; to share (secrets redacted), and it is a &lt;strong&gt;dump&lt;/strong&gt; of runtime state at the crash moment. The name is honest: this is a raw capture of what your program looked like when it failed, cleaned up enough to share without embarrassment.&lt;/p&gt;




&lt;h2&gt;
  
  
  Things That Almost Broke the Crash Handler
&lt;/h2&gt;

&lt;p&gt;Building a crash handler is harder than it looks. You are already in an error state. Memory might be corrupted. Any allocation could trigger another failure. Here are some of the problems I hit and how each shaped the design.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Handler Must Never Crash
&lt;/h3&gt;

&lt;p&gt;If &lt;code&gt;sys.excepthook&lt;/code&gt; raises, CPython writes an error to stderr. The original traceback is lost. Every operation inside the handler is wrapped in &lt;code&gt;try/except&lt;/code&gt;. Serialization fails? Caught. Disk full? Caught. Memory allocation fails? Falls back to a pre-allocated buffer. The original traceback always prints.&lt;/p&gt;

&lt;h3&gt;
  
  
  The 100x Problem
&lt;/h3&gt;

&lt;p&gt;Rich's traceback rendering is roughly 100x slower than stdlib formatting for large tracebacks. Inside a crash handler that is unacceptable. The solution was two phases. &lt;strong&gt;Capture&lt;/strong&gt; at crash time using stdlib only. &lt;strong&gt;Render&lt;/strong&gt; after the crash with Rich formatting and no time constraint. The capture phase never imports Rich. It never calls &lt;code&gt;__repr__&lt;/code&gt; on untrusted objects. It uses &lt;code&gt;reprlib.repr()&lt;/code&gt; with depth and length limits.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why JSON, Not Pickle
&lt;/h3&gt;

&lt;p&gt;JSON cannot execute code during deserialization. Pickle was rejected for this reason. So were cloudpickle and dill. JSON also means reports are universally readable. Pipe them into &lt;code&gt;jq&lt;/code&gt; or process them in CI. Every report includes a &lt;code&gt;safedump_version&lt;/code&gt; field for forward compatibility.&lt;/p&gt;

&lt;h3&gt;
  
  
  Sharing Crash Reports Without Sharing Secrets
&lt;/h3&gt;

&lt;p&gt;The first time you paste a crash report containing a production API key into a GitHub issue, you learn this lesson. Safedump applies two layers of redaction automatically. First, a variable name denylist: any local whose name contains patterns like &lt;code&gt;password&lt;/code&gt;, &lt;code&gt;token&lt;/code&gt;, or &lt;code&gt;key&lt;/code&gt; has its value replaced. The matching is tiered to avoid false positives. &lt;code&gt;keyboard&lt;/code&gt; does not match &lt;code&gt;key&lt;/code&gt;, but &lt;code&gt;api_key&lt;/code&gt; does. Second, regex-based credential detection catches AWS keys, GitHub tokens, and JWTs even when the variable name is not suspicious.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxyss168guf3nb5lyx9bm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxyss168guf3nb5lyx9bm.png" alt="Safedump Architecture" width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Atomic Writes or Corrupted Reports
&lt;/h3&gt;

&lt;p&gt;Reports are written to a temp file, then atomically renamed via &lt;code&gt;os.replace()&lt;/code&gt;. This prevents partial writes from overwriting valid reports. If the primary directory is unwritable, Safedump falls back to &lt;code&gt;/tmp&lt;/code&gt;. The original traceback always displays.&lt;/p&gt;




&lt;h2&gt;
  
  
  How It Compares
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Best for&lt;/th&gt;
&lt;th&gt;Limitation&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Stdlib traceback&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Zero-dependency debugging everywhere&lt;/td&gt;
&lt;td&gt;No variable values, no structure, no redaction&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;rich.traceback&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Local development, beautiful terminal output&lt;/td&gt;
&lt;td&gt;Terminal only, output disappears when session ends&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;stackprinter&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Getting variable values into logs, lightweight&lt;/td&gt;
&lt;td&gt;Plain text only, cannot query structure later&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Sentry&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Production aggregation, dashboards, team workflows&lt;/td&gt;
&lt;td&gt;Requires cloud, data leaves your network&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Safedump&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Local crash reports with full state. Offline inspection. Structured JSON. Secret redaction&lt;/td&gt;
&lt;td&gt;No built-in aggregation. Designed for single-crash analysis, not fleet monitoring&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The takeaway: if you already use Sentry, keep using it. If you want something between "add a print statement" and "set up a monitoring service," Safedump is worth trying. It also works alongside Sentry: Safedump captures more per-crash detail locally while Sentry handles aggregation across services.&lt;/p&gt;




&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Who this is for:&lt;/strong&gt; Python developers debugging production crashes who want more context than a traceback provides, but do not want to set up a monitoring service for every project. Open-source maintainers who want crash reports from users without asking them to create accounts or send log files.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Who this is not for:&lt;/strong&gt; Teams that need fleet-wide error aggregation, dashboards, and alerting. That is Sentry's job. If you already have a monitoring setup that works, Safedump is complementary, not a replacement.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Lessons That Apply Beyond Crash Handlers
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Research before architecture, and architecture before code.&lt;/strong&gt; The most expensive bug is the one you discover during implementation because you did not think through the design. A structured review caught five issues that would have required significant refactoring after code was written. Catching them before a single line existed cost nothing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Write down why you rejected alternatives.&lt;/strong&gt; Every "we chose X instead of Y" decision becomes a valuable artifact when someone later asks why you did not use Y. Safedump has four Architecture Decision Records documenting the constitution, API design, architecture approval, and public API freeze.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Test the crash handler by crashing it.&lt;/strong&gt; The hardest tests to write were the ones that deliberately triggered failures inside the handler. Simulating &lt;code&gt;MemoryError&lt;/code&gt;, disk full, permission denied, and corrupt inputs. These tests found real bugs that would not have appeared in normal use, but would have failed catastrophically in production.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Separation of concerns is not optional in error paths.&lt;/strong&gt; The hot path inside the exception handler and the cold path for rendering and CLI should share no code paths, no imports, and no mutable state. The hot path must be predictable. The cold path can be anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  What This Changes
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7rzdf5hw62uvx1rwr41o.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7rzdf5hw62uvx1rwr41o.gif" alt="Safedump Demo" width="720" height="405"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Going back to the opening scenario. Friday night. KeyError. No context.&lt;/p&gt;

&lt;p&gt;With Safedump installed, that same crash produces a file containing every local variable, the exception chain, thread state, and environment metadata. You run &lt;code&gt;safedump view&lt;/code&gt; and see that &lt;code&gt;user["tier"]&lt;/code&gt; was &lt;code&gt;None&lt;/code&gt;. A missing field in the request payload.&lt;/p&gt;

&lt;p&gt;No redeploy. No &lt;code&gt;logger.debug&lt;/code&gt;. No SSH session. No reproducing the bug.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;The traceback told me where. The report told me why.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;Safedump is open source, MIT licensed, and works on Python 3.9 through 3.13. Install it with &lt;code&gt;pip install safedump&lt;/code&gt; and capture crash context in under a minute.&lt;/p&gt;

&lt;p&gt;I would love to hear from you: &lt;strong&gt;what information do you wish Python tracebacks included?&lt;/strong&gt; What does your debugging workflow look like today? If you hit a production crash and the traceback was not enough, what did you reach for?&lt;/p&gt;

&lt;p&gt;If you try Safedump in a real project, I would like to know how it went. The &lt;code&gt;good first issue&lt;/code&gt; label on GitHub is where to start if you want to contribute. Bug reports and feature requests go through Issues. Discussion happens in the Discussions tab.&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/Muneer320/safedump" rel="noopener noreferrer"&gt;github.com/Muneer320/safedump&lt;/a&gt;&lt;/p&gt;

</description>
      <category>python</category>
      <category>opensource</category>
      <category>devtools</category>
      <category>productivity</category>
    </item>
    <item>
      <title>From Puzzle Generator to Puzzle Ecosystem: My Finish-Up-A-Thon Journey</title>
      <dc:creator>Muneer Alam</dc:creator>
      <pubDate>Fri, 05 Jun 2026 19:03:54 +0000</pubDate>
      <link>https://dev.to/muneer320/from-puzzle-generator-to-puzzle-ecosystem-my-finish-up-a-thon-journey-koh</link>
      <guid>https://dev.to/muneer320/from-puzzle-generator-to-puzzle-ecosystem-my-finish-up-a-thon-journey-koh</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/github-2026-05-21"&gt;GitHub Finish-Up-A-Thon Challenge&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;BOOP started life as a Python command-line tool that generated word search puzzle books as PDFs.&lt;/p&gt;

&lt;p&gt;Eventually I wrapped it in a React + FastAPI web application so anyone could create puzzle books from their browser. Technically, it worked. Users could choose topics, configure puzzle settings, and download a generated PDF.&lt;/p&gt;

&lt;p&gt;But it wasn't finished.&lt;/p&gt;

&lt;p&gt;At the start of the challenge BOOP had:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;31 commits&lt;/li&gt;
&lt;li&gt;12 components&lt;/li&gt;
&lt;li&gt;5 routes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;By the end of the challenge it had grown to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;162 commits&lt;/li&gt;
&lt;li&gt;20+ components&lt;/li&gt;
&lt;li&gt;7+ routes&lt;/li&gt;
&lt;li&gt;68+ features&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal wasn't to start over.&lt;/p&gt;

&lt;p&gt;The goal was to finally finish what already existed.&lt;/p&gt;

&lt;p&gt;The GitHub Finish-Up-A-Thon gave me the perfect excuse to revisit a project I had been postponing for months and turn it from a working prototype into something that felt like a complete product.&lt;/p&gt;

&lt;p&gt;Over the course of the challenge, BOOP evolved from a simple PDF generator into a complete puzzle platform with two distinct experiences:&lt;/p&gt;

&lt;h3&gt;
  
  
  Create
&lt;/h3&gt;

&lt;p&gt;Generate fully customized puzzle books with multiple difficulty levels, custom word lists, image uploads, progress tracking, previews, and downloadable PDFs.&lt;/p&gt;

&lt;h3&gt;
  
  
  Play
&lt;/h3&gt;

&lt;p&gt;Solve word searches directly in the browser with mouse, touch, keyboard controls, hints, timers, game persistence, poster downloads, and sharing features.&lt;/p&gt;

&lt;p&gt;By the end of the challenge the project grew from:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;Before&lt;/th&gt;
&lt;th&gt;After&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Commits&lt;/td&gt;
&lt;td&gt;31&lt;/td&gt;
&lt;td&gt;162&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Components&lt;/td&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;20+&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Routes&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;7+&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Features&lt;/td&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;td&gt;68+&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Accessibility Features&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Security Improvements&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Interactive Gameplay&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dark Mode&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The biggest realization was that people don't just want to generate puzzles.&lt;/p&gt;

&lt;p&gt;They want to play them.&lt;/p&gt;

&lt;p&gt;That insight completely changed the direction of the project.&lt;/p&gt;




&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Compare Both Versions
&lt;/h3&gt;

&lt;p&gt;One thing I'm particularly proud of is that both versions remain publicly available.&lt;/p&gt;

&lt;p&gt;You don't have to rely on screenshots or marketing claims. You can directly compare the before and after versions yourself, inspect the code in both branches, and see the entire transformation.&lt;/p&gt;

&lt;h3&gt;
  
  
  Before (Challenge Starting Point)
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Website:&lt;/strong&gt; &lt;a href="https://boop-m70hnwxro-muneer320s-projects.vercel.app/" rel="noopener noreferrer"&gt;https://boop-m70hnwxro-muneer320s-projects.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Branch:&lt;/strong&gt; &lt;code&gt;finishupathon-before&lt;/code&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  After (Current Version)
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Website:&lt;/strong&gt; &lt;a href="https://boop-web.vercel.app/" rel="noopener noreferrer"&gt;https://boop-web.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Branch:&lt;/strong&gt; &lt;code&gt;master&lt;/code&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Repository
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://github.com/Muneer320/BOOP-web" rel="noopener noreferrer"&gt;https://github.com/Muneer320/BOOP-web&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Before vs After
&lt;/h3&gt;

&lt;h4&gt;
  
  
  Landing Page
&lt;/h4&gt;

&lt;p&gt;Before: a functional blue interface.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftxvsbivcnv71ivxctm1u.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftxvsbivcnv71ivxctm1u.jpeg" alt="Before\_Web\_LandingPage" width="800" height="959"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;After: a complete visual identity inspired by puzzle books, newspapers, and vintage publishing.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fy0b1v0wpd9iri2at6s4z.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fy0b1v0wpd9iri2at6s4z.jpeg" alt="After\_Web\_LandingPage" width="800" height="802"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Mobile Experience
&lt;/h4&gt;

&lt;p&gt;The entire experience was redesigned to work naturally on mobile devices.&lt;/p&gt;

&lt;p&gt;Before:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Flhbeavyy6aepsuafjwy5.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Flhbeavyy6aepsuafjwy5.png" alt="Before\_Phone\_LandingPage" width="421" height="913"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;After:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fxqrwt8sikqpdj2ncbsr7.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fxqrwt8sikqpdj2ncbsr7.png" alt="After\_Phone\_LadingPage\_Light" width="421" height="913"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Interactive Play
&lt;/h4&gt;

&lt;p&gt;The largest feature added during the challenge was an entirely new gameplay system.&lt;/p&gt;

&lt;p&gt;BOOP can now be used without generating a PDF at all.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fdrxmw2uh6v0z81s0bjev.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fdrxmw2uh6v0z81s0bjev.jpeg" alt="After\_Web\_Play" width="800" height="741"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F37vu7ev0mbkln724teqk.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F37vu7ev0mbkln724teqk.jpeg" alt="After\_Web\_Play\_Done" width="800" height="545"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Dark Mode
&lt;/h4&gt;

&lt;p&gt;A fully themed dark experience was added across the entire application.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftjo2pv9rye5cfxfqgfrc.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftjo2pv9rye5cfxfqgfrc.jpeg" alt="After\_Web\_LandingPage\_Dark" width="800" height="802"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwy9no6ujba1t0ju88hnc.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwy9no6ujba1t0ju88hnc.jpeg" alt="After\_Phone\_LandingPageFull\_Light" width="430" height="3885"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  The Comeback Story
&lt;/h2&gt;

&lt;h3&gt;
  
  
  The Project Was Already "Done"
&lt;/h3&gt;

&lt;p&gt;At least that's what I told myself.&lt;/p&gt;

&lt;p&gt;The PDF generation worked.&lt;/p&gt;

&lt;p&gt;The backend generated books.&lt;/p&gt;

&lt;p&gt;The frontend could submit requests.&lt;/p&gt;

&lt;p&gt;Users could download files.&lt;/p&gt;

&lt;p&gt;Mission accomplished... right?&lt;/p&gt;

&lt;p&gt;Not really.&lt;/p&gt;

&lt;p&gt;When I revisited the project, I realized it was a prototype pretending to be a product.&lt;/p&gt;

&lt;p&gt;It solved the core problem but ignored everything around it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No accessibility&lt;/li&gt;
&lt;li&gt;No dark mode&lt;/li&gt;
&lt;li&gt;No interactive gameplay&lt;/li&gt;
&lt;li&gt;No meaningful feedback during generation&lt;/li&gt;
&lt;li&gt;No proper security protections&lt;/li&gt;
&lt;li&gt;No polished mobile experience&lt;/li&gt;
&lt;li&gt;Minimal documentation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The challenge wasn't building BOOP.&lt;/p&gt;

&lt;p&gt;The challenge was finishing BOOP.&lt;/p&gt;




&lt;h3&gt;
  
  
  A Complete Visual Redesign
&lt;/h3&gt;

&lt;p&gt;One of the first things I changed was the visual identity.&lt;/p&gt;

&lt;p&gt;The original version used a fairly generic blue theme.&lt;/p&gt;

&lt;p&gt;The new version embraces a puzzle-book aesthetic:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Warm paper-inspired colors&lt;/li&gt;
&lt;li&gt;Vintage typography&lt;/li&gt;
&lt;li&gt;Custom SVG iconography&lt;/li&gt;
&lt;li&gt;Newspaper-inspired layout elements&lt;/li&gt;
&lt;li&gt;Full dark mode support&lt;/li&gt;
&lt;li&gt;Responsive layouts across desktop and mobile&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Instead of feeling like another web form, BOOP now feels like a digital puzzle publication.&lt;/p&gt;




&lt;h3&gt;
  
  
  The Biggest Feature: Interactive Play
&lt;/h3&gt;

&lt;p&gt;The largest addition was an entirely new gameplay system.&lt;/p&gt;

&lt;p&gt;Before the challenge:&lt;/p&gt;

&lt;p&gt;Generate → Download PDF&lt;/p&gt;

&lt;p&gt;After the challenge:&lt;/p&gt;

&lt;p&gt;Generate → Download PDF&lt;/p&gt;

&lt;p&gt;or&lt;/p&gt;

&lt;p&gt;Play Immediately&lt;/p&gt;

&lt;p&gt;The new Play mode includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;6 difficulty levels&lt;/li&gt;
&lt;li&gt;Mouse selection&lt;/li&gt;
&lt;li&gt;Touch drag support&lt;/li&gt;
&lt;li&gt;Keyboard navigation&lt;/li&gt;
&lt;li&gt;Hint system with cooldowns&lt;/li&gt;
&lt;li&gt;Persistent timers&lt;/li&gt;
&lt;li&gt;Saved progress&lt;/li&gt;
&lt;li&gt;Poster generation&lt;/li&gt;
&lt;li&gt;Sharing support&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This single feature transformed BOOP from a utility into an actual puzzle platform.&lt;/p&gt;




&lt;h3&gt;
  
  
  Rebuilding the User Experience
&lt;/h3&gt;

&lt;p&gt;The original application communicated very little.&lt;/p&gt;

&lt;p&gt;Loading meant:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Loading...&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That's it.&lt;/p&gt;

&lt;p&gt;The redesigned version introduces:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Skeleton loading states&lt;/li&gt;
&lt;li&gt;Animated generation progress&lt;/li&gt;
&lt;li&gt;Multi-stage status tracking&lt;/li&gt;
&lt;li&gt;Better success screens&lt;/li&gt;
&lt;li&gt;Error recovery flows&lt;/li&gt;
&lt;li&gt;File previews&lt;/li&gt;
&lt;li&gt;Improved navigation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Users can now understand what is happening instead of waiting blindly.&lt;/p&gt;




&lt;h3&gt;
  
  
  Accessibility Improvements
&lt;/h3&gt;

&lt;p&gt;The original project effectively had zero accessibility support.&lt;/p&gt;

&lt;p&gt;The updated version includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;ARIA labels&lt;/li&gt;
&lt;li&gt;Keyboard navigation&lt;/li&gt;
&lt;li&gt;Focus management&lt;/li&gt;
&lt;li&gt;Focus-visible styling&lt;/li&gt;
&lt;li&gt;Reduced-motion support&lt;/li&gt;
&lt;li&gt;Accessible puzzle controls&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A user can now navigate and play the application without relying entirely on a mouse.&lt;/p&gt;




&lt;h3&gt;
  
  
  Security and Backend Improvements
&lt;/h3&gt;

&lt;p&gt;The backend also received significant attention.&lt;/p&gt;

&lt;p&gt;New additions include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Rate limiting&lt;/li&gt;
&lt;li&gt;Security headers&lt;/li&gt;
&lt;li&gt;Input validation&lt;/li&gt;
&lt;li&gt;Async generation&lt;/li&gt;
&lt;li&gt;Safe file handling&lt;/li&gt;
&lt;li&gt;Exception handling&lt;/li&gt;
&lt;li&gt;Path traversal protection&lt;/li&gt;
&lt;li&gt;Improved deployment configuration&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal was simple:&lt;/p&gt;

&lt;p&gt;Move from "it works on my machine" to something I would actually feel comfortable deploying.&lt;/p&gt;




&lt;h3&gt;
  
  
  Refactoring and Documentation
&lt;/h3&gt;

&lt;p&gt;A surprising amount of work happened behind the scenes.&lt;/p&gt;

&lt;p&gt;Some highlights:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Large sections of repetitive JSX replaced with reusable components&lt;/li&gt;
&lt;li&gt;Route-level code splitting&lt;/li&gt;
&lt;li&gt;Dependency cleanup&lt;/li&gt;
&lt;li&gt;Documentation overhaul&lt;/li&gt;
&lt;li&gt;Backend documentation&lt;/li&gt;
&lt;li&gt;Frontend documentation&lt;/li&gt;
&lt;li&gt;Deployment instructions&lt;/li&gt;
&lt;li&gt;Audit reports&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The project is now significantly easier to maintain than when the challenge started.&lt;/p&gt;




&lt;h2&gt;
  
  
  My Experience with GitHub Copilot
&lt;/h2&gt;

&lt;p&gt;GitHub Copilot wasn't used as a code vending machine.&lt;/p&gt;

&lt;p&gt;It worked best as a collaborator.&lt;/p&gt;

&lt;p&gt;I used Copilot heavily for:&lt;/p&gt;

&lt;h3&gt;
  
  
  UI Development
&lt;/h3&gt;

&lt;p&gt;Copilot helped generate:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Dark mode token structures&lt;/li&gt;
&lt;li&gt;Accessibility patterns&lt;/li&gt;
&lt;li&gt;Skeleton loading components&lt;/li&gt;
&lt;li&gt;SVG icon implementations&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Gameplay Features
&lt;/h3&gt;

&lt;p&gt;One example was the new Play mode.&lt;/p&gt;

&lt;p&gt;Copilot helped scaffold parts of the touch interaction system used for selecting words on mobile devices, allowing me to focus on integrating the logic into BOOP's game state and user experience.&lt;/p&gt;

&lt;p&gt;It also helped accelerate development of:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Touch interaction logic&lt;/li&gt;
&lt;li&gt;Keyboard controls&lt;/li&gt;
&lt;li&gt;Timer persistence&lt;/li&gt;
&lt;li&gt;Hint cooldown systems&lt;/li&gt;
&lt;li&gt;Canvas poster generation&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Backend Improvements
&lt;/h3&gt;

&lt;p&gt;Copilot was particularly useful when implementing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Validation logic&lt;/li&gt;
&lt;li&gt;Middleware patterns&lt;/li&gt;
&lt;li&gt;Security headers&lt;/li&gt;
&lt;li&gt;Async processing flows&lt;/li&gt;
&lt;li&gt;Error handling structures&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Refactoring
&lt;/h3&gt;

&lt;p&gt;The project contained a lot of repetitive code accumulated over time.&lt;/p&gt;

&lt;p&gt;Copilot helped identify patterns, suggest abstractions, and accelerate the process of turning one-off implementations into reusable components.&lt;/p&gt;

&lt;p&gt;The result wasn't code that Copilot built for me.&lt;/p&gt;

&lt;p&gt;It was code that I was able to build faster because Copilot handled much of the repetitive scaffolding and exploration work.&lt;/p&gt;




&lt;h2&gt;
  
  
  What I Learned
&lt;/h2&gt;

&lt;p&gt;The biggest lesson from this challenge is simple:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Working software is not finished software.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A project can successfully solve its core problem and still feel incomplete.&lt;/p&gt;

&lt;p&gt;The difference between a prototype and a product is often everything around the main feature:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Accessibility&lt;/li&gt;
&lt;li&gt;UX&lt;/li&gt;
&lt;li&gt;Documentation&lt;/li&gt;
&lt;li&gt;Performance&lt;/li&gt;
&lt;li&gt;Security&lt;/li&gt;
&lt;li&gt;Feedback&lt;/li&gt;
&lt;li&gt;Polish&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Before this challenge, BOOP generated puzzle books.&lt;/p&gt;

&lt;p&gt;After this challenge, BOOP became a puzzle ecosystem.&lt;/p&gt;

&lt;p&gt;And for the first time, it finally feels finished.&lt;/p&gt;




&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Current Version&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://boop-web.vercel.app/" rel="noopener noreferrer"&gt;https://boop-web.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Before Version&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://boop-m70hnwxro-muneer320s-projects.vercel.app/" rel="noopener noreferrer"&gt;https://boop-m70hnwxro-muneer320s-projects.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Repository&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://github.com/Muneer320/BOOP-web" rel="noopener noreferrer"&gt;https://github.com/Muneer320/BOOP-web&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>githubchallenge</category>
    </item>
  </channel>
</rss>
