<?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: Mia Keller</title>
    <description>The latest articles on DEV Community by Mia Keller (@mia_keller_ffd2584c046ecb).</description>
    <link>https://dev.to/mia_keller_ffd2584c046ecb</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%2F4008633%2Fbe4e1f06-5ae2-4b3c-95e1-446ae32be7df.png</url>
      <title>DEV Community: Mia Keller</title>
      <link>https://dev.to/mia_keller_ffd2584c046ecb</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mia_keller_ffd2584c046ecb"/>
    <language>en</language>
    <item>
      <title>Why Coding on a Low-Spec Laptop Made Me a Way Better Developer</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Mon, 16 Nov 2026 13:45:55 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/why-coding-on-a-low-spec-laptop-made-me-a-way-better-developer-2a03</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/why-coding-on-a-low-spec-laptop-made-me-a-way-better-developer-2a03</guid>
      <description>&lt;p&gt;Scroll through tech Twitter or YouTube for five minutes, and you’ll start thinking you need a maxed-out MacBook Pro, three vertical monitors, and a $200 mechanical keyboard just to write a basic for loop.&lt;/p&gt;

&lt;p&gt;I used to buy into that hype. For a long time, I was coding on a basic setup with an older processor and 8GB of RAM. Every time I opened a heavy IDE alongside a few browser tabs, my laptop fans would sound like a jet engine preparing for takeoff.&lt;/p&gt;

&lt;p&gt;At first, it was super frustrating. I felt like my hardware was holding me back.&lt;/p&gt;

&lt;p&gt;Looking back now, though? Having a slow machine was the best thing that ever happened to my coding skills. When you don't have infinite RAM to bail you out, you stop being lazy and start actually understanding how software works.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;You Learn to Hate Bloat&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;When you have 32GB of RAM, you don't care if your dev environment eats up 4GB just sitting idle. When you only have 8GB, every megabyte is precious.&lt;/p&gt;

&lt;p&gt;I had to ditch heavy, sluggish tools and learn lightweight alternatives. I switched to faster text editors, learned to love the terminal, and stopped installing massive libraries just to do things I could write in ten lines of clean code. You quickly realize how much modern software is completely bloated—and you stop contributing to the mess.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;You Write Actually Efficient Code&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Nothing teaches you about memory leaks and infinite loops faster than a laptop that freezes completely when you mess up a while loop.&lt;/p&gt;

&lt;p&gt;Instead of blindly hitting "run" and hoping for the best, I started thinking before typing. I began paying attention to how much data I was loading at once, optimizing my loops, and keeping my logic tight. When your machine forces you to respect hardware limits, writing clean, fast code becomes a habit rather than an afterthought.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;You Master the Art of Troubleshooting&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;When you run into performance bottlenecks on an older machine, you can't just throw money at the problem. You have to get creative.&lt;/p&gt;

&lt;p&gt;I spent hours learning how to tweak background processes, optimize local environments, and strip away unnecessary visual fluff just to squeeze out a little extra speed. That curiosity bled into my actual development work. I became way better at debugging, reading documentation, and figuring out what was happening under the hood instead of just copy-pasting fixes.&lt;/p&gt;

&lt;p&gt;Don't Let Your Gear Be an Excuse&lt;/p&gt;

&lt;p&gt;If you're sitting there right now thinking you can't start building cool projects because your setup isn't good enough—stop waiting.&lt;/p&gt;

&lt;p&gt;Some of the best software in the world was built on machines weaker than a modern smartwatch. Your brain is the main tool, not your processor. Use what you have, keep your code lean, and focus on building things that actually work.&lt;/p&gt;

&lt;p&gt;What kind of setup did you start coding on? Drop your specs in the comments—let's see who survived the biggest potato PC!&lt;/p&gt;

</description>
      <category>programming</category>
      <category>beginners</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>The Joy of Boring Code: Why Writing "Clever" Code is Overrated</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Mon, 16 Nov 2026 10:44:35 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/the-joy-of-boring-code-why-writing-clever-code-is-overrated-6ig</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/the-joy-of-boring-code-why-writing-clever-code-is-overrated-6ig</guid>
      <description>&lt;p&gt;Let’s be honest for a second. We’ve all done it.&lt;/p&gt;

&lt;p&gt;You’re staring at a problem, and instead of writing a straightforward, five-line if/else statement, you decide to flex. You chain together three map-reduce operations, throw in a clever ternary operator, and use a regex string that looks like a cat walking across a keyboard. When it compiles on the first try, you lean back in your chair like you just solved the universe.&lt;/p&gt;

&lt;p&gt;Two months later, you’re staring at that exact same block of code at 2:00 AM during an incident, whispering, "What on earth was past-me thinking?"&lt;/p&gt;

&lt;p&gt;In software development, we often fall in love with cleverness. But the dirty little secret of senior engineering is this: the best code is painfully, wonderfully boring.&lt;/p&gt;

&lt;p&gt;Why We Fall for the "Clever" Trap&lt;br&gt;
From day one, coding feels like a puzzle. We’re rewarded for finding short, compact solutions. Hackathons and coding interviews celebrate the person who can compress a solution into the fewest lines possible.&lt;/p&gt;

&lt;p&gt;Because of this, we start treating code like poetry, where density and abstraction equal beauty.&lt;/p&gt;

&lt;p&gt;"Look how idiomatic this is!"&lt;/p&gt;

&lt;p&gt;"Check out this slick functional pattern!"&lt;/p&gt;

&lt;p&gt;The problem? Code is read infinitely more times than it is written. When you write clever code, you’re writing a love letter to your current self while leaving a time bomb for your future self (and your team).&lt;/p&gt;

&lt;p&gt;What Does "Boring" Code Actually Look Like?&lt;br&gt;
Boring code isn't bad code. In fact, writing boring code takes a lot more discipline than writing clever code.&lt;/p&gt;

&lt;p&gt;Boring code looks like this:&lt;/p&gt;

&lt;p&gt;Obvious names: Variables and functions are named exactly what they do, even if it means typing isUserActiveAndVerified instead of just flag.&lt;/p&gt;

&lt;p&gt;Linear logic: It reads like a book from top to bottom, minimizing mental gymnastics and deep nesting.&lt;/p&gt;

&lt;p&gt;Fewer hidden abstractions: It doesn't use a custom framework-within-a-framework just to save three lines of repetition.&lt;/p&gt;

&lt;p&gt;When code is boring, anyone can drop into it, understand it in ten seconds, and make a change without breaking production.&lt;/p&gt;

&lt;p&gt;The Superpower of Predictability&lt;br&gt;
When you optimize for readability and simplicity, magic happens:&lt;/p&gt;

&lt;p&gt;Onboarding becomes a breeze: New teammates aren't terrified of touching your codebase. They can actually ship features in week one.&lt;/p&gt;

&lt;p&gt;Debugging stops being detective work: When a bug happens, boring code makes it instantly obvious where the failure occurred.&lt;/p&gt;

&lt;p&gt;AI loves it too: If you’re using AI coding assistants, they thrive on clear, predictable patterns. Clever, overly abstracted code usually just confuses them.&lt;/p&gt;

&lt;p&gt;How to Embrace the Mundane&lt;br&gt;
You don’t have to sacrifice your creativity to write boring code. Save your creativity for architecture, system design, and solving complex user problems—not for inventing a novel way to loop through an array.&lt;/p&gt;

&lt;p&gt;Next time you're about to push a piece of code that makes you feel like a wizard, pause and ask yourself: If a tired junior developer had to read this at the end of a long Friday, would they cry?&lt;/p&gt;

&lt;p&gt;If the answer is yes, hit backspace and write the boring version. Your future self will thank you with a good night's sleep.&lt;/p&gt;

</description>
      <category>softwareengineering</category>
      <category>webdev</category>
      <category>cleancode</category>
      <category>developerlife</category>
    </item>
    <item>
      <title>Why Is COUNT(*) So Slow on Large Tables?</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Sun, 15 Nov 2026 17:40:27 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/why-is-count-so-slow-on-large-tables-3h5k</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/why-is-count-so-slow-on-large-tables-3h5k</guid>
      <description>&lt;p&gt;&lt;code&gt;COUNT(*)&lt;/code&gt; feels like it should be instant. The table already exists, an index already exists, so why does Postgres sometimes scan a large table just to answer how many rows it holds?&lt;/p&gt;

&lt;p&gt;The short answer is that in Postgres, a count is not a stored number. It depends on what the current transaction can see.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Postgres checks rows instead of reading a stored count
&lt;/h2&gt;

&lt;p&gt;Postgres uses MVCC, which means different transactions can see different versions of the same table at the same time. A row inserted by an uncommitted transaction, or deleted but not yet vacuumed, may be visible to one transaction and invisible to another.&lt;/p&gt;

&lt;p&gt;That means there is no single correct count for a table in isolation. The count depends on the snapshot of the transaction running the query. Postgres therefore has to check visibility, row by row or index entry by index entry, rather than returning a cached total.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="nb"&gt;COUNT&lt;/span&gt;&lt;span class="cm"&gt;(*) FROM orders;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On a small table this is fast. On a table with millions of rows, that visibility work adds up, even when the query itself looks trivial.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why an index does not always save the query
&lt;/h2&gt;

&lt;p&gt;An index can help, but only in the right conditions. Postgres may use an index-only scan for &lt;code&gt;COUNT(*)&lt;/code&gt;, which avoids reading the main table heap for every row. Even then, it still needs to confirm visibility.&lt;/p&gt;

&lt;p&gt;Postgres keeps a visibility map to track which pages hold only visible tuples. If a page is marked all-visible, an index-only scan can skip heap checks for that page. If the table has not been vacuumed recently, or has a lot of recent updates and deletes, many pages will not be all-visible. The scan then falls back to heap fetches to check visibility, and much of the benefit disappears.&lt;/p&gt;

&lt;p&gt;In practical terms: regular &lt;code&gt;VACUUM&lt;/code&gt; and &lt;code&gt;ANALYZE&lt;/code&gt;, a suitable index, and low bloat help index-only scans. Without those conditions, &lt;code&gt;COUNT(*)&lt;/code&gt; can still be slow despite an index being present.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to see what is happening
&lt;/h2&gt;

&lt;p&gt;Start with &lt;code&gt;EXPLAIN&lt;/code&gt;, and add &lt;code&gt;ANALYZE&lt;/code&gt; and &lt;code&gt;BUFFERS&lt;/code&gt; when checking a slow query in a safe environment:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;EXPLAIN&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;ANALYZE&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="no"&gt;BUFFERS&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="nb"&gt;COUNT&lt;/span&gt;&lt;span class="cm"&gt;(*) FROM orders;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Look for the scan type, whether heap fetches appear on an index-only scan, and how many buffers were read. A sequential scan on a large table, or a high heap fetch count, usually points to visibility work rather than a missing index alone.&lt;/p&gt;

&lt;p&gt;Avoid treating one plan as proof for every case. Table size, write patterns, vacuum history, and Postgres settings all change the result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Faster options when an exact count is not required
&lt;/h2&gt;

&lt;p&gt;Many uses of &lt;code&gt;COUNT(*)&lt;/code&gt; do not need an exact number. Dashboards, admin totals, and rough progress indicators often work well with an estimate.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Use the planner estimate from &lt;code&gt;pg_class&lt;/code&gt;
&lt;/h3&gt;

&lt;p&gt;Postgres stores an estimated row count in &lt;code&gt;pg_class.reltuples&lt;/code&gt;, updated by &lt;code&gt;VACUUM&lt;/code&gt; and &lt;code&gt;ANALYZE&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="n"&gt;reltuples&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="kt"&gt;bigint&lt;/span&gt; &lt;span class="k"&gt;AS&lt;/span&gt; &lt;span class="n"&gt;estimated_rows&lt;/span&gt;
&lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="n"&gt;pg_class&lt;/span&gt;
&lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="n"&gt;relname&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'orders'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is fast because it reads catalog metadata, not the table. The trade-off is accuracy. The estimate can be stale after bulk loads, large deletes, or before the next analyze run. Use it when “about right” is good enough, and say so in the interface if users will see the number.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Read the estimate from &lt;code&gt;EXPLAIN&lt;/code&gt;
&lt;/h3&gt;

&lt;p&gt;A plain &lt;code&gt;EXPLAIN&lt;/code&gt; without &lt;code&gt;ANALYZE&lt;/code&gt; shows a row estimate for the query without executing it. It comes from the same planner statistics, so it shares the same staleness trade-off. It is useful for a quick check, but it is not a substitute for an exact count when exactness matters.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Maintain a counter for hot totals
&lt;/h3&gt;

&lt;p&gt;For a total that is read often and written often, a separate counter can help. The usual pattern is a small table holding one row per counted thing, updated when rows are inserted or deleted, or refreshed on a schedule from a background job.&lt;/p&gt;

&lt;p&gt;This moves the cost from read time to write time or to a periodic refresh. It also introduces new trade-offs: a single counter row can become a contention point under heavy writes, and a scheduled refresh means the displayed total lags behind reality. It suits dashboards and cached totals more than billing or audit queries.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Avoid needing the total at all
&lt;/h3&gt;

&lt;p&gt;Pagination is a common source of expensive counts. Showing “Page 1 of 4,203” forces an exact total on every page load. Alternatives include keyset pagination, a “Load more” pattern, or fetching one extra row to decide whether another page exists. These approaches avoid the full count while still giving readers a way forward.&lt;/p&gt;

&lt;h2&gt;
  
  
  When an exact count is still the right choice
&lt;/h2&gt;

&lt;p&gt;Exact counts are the right choice when correctness matters more than speed: small tables, infrequent admin checks, reports where the number must reconcile, and any case where an estimate would mislead.&lt;/p&gt;

&lt;p&gt;In those cases, accept the cost, run the query when load is lower if possible, and keep the table healthy with vacuum and analyze. Adding a covering index can help, but only if the visibility map is in good shape. There is no index trick that removes MVCC visibility checks entirely.&lt;/p&gt;

&lt;h2&gt;
  
  
  A short checklist
&lt;/h2&gt;

&lt;p&gt;Before optimising a slow &lt;code&gt;COUNT(*)&lt;/code&gt;, check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Is an exact count required, or would an estimate be acceptable?&lt;/li&gt;
&lt;li&gt;How large is the table, and how often does it change?&lt;/li&gt;
&lt;li&gt;When was it last vacuumed and analyzed?&lt;/li&gt;
&lt;li&gt;Does the plan use an index-only scan, and are heap fetches high?&lt;/li&gt;
&lt;li&gt;Is the count feeding pagination, a dashboard, or a report that must reconcile?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Answering those questions usually points to the right fix: an estimate, a counter, a different pagination pattern, or simply accepting an exact count and keeping the table maintained.&lt;/p&gt;

&lt;p&gt;How do you handle counts on large tables: estimates, counters, or a different pattern entirely?&lt;/p&gt;

</description>
      <category>database</category>
      <category>postgres</category>
      <category>sql</category>
      <category>performance</category>
    </item>
    <item>
      <title>Cutting through the noise: A fresh, no-nonsense resource for GTA 6 info</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Mon, 26 Oct 2026 17:47:50 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/cutting-through-the-noise-a-fresh-no-nonsense-resource-for-gta-6-info-nfj</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/cutting-through-the-noise-a-fresh-no-nonsense-resource-for-gta-6-info-nfj</guid>
      <description>&lt;p&gt;If you've been keeping up with all the anticipation surrounding Grand Theft Auto VI, finding a clean, well-organized community hub can be pretty tough. Recently, I came across &lt;a href="https://leocheats.com/" rel="noopener noreferrer"&gt;LeoCheats&lt;/a&gt;—a fantastic fan site and guide that stands out by cutting through all the typical clickbait and noise.&lt;/p&gt;

&lt;p&gt;Instead of shady "cheat code generators," intrusive ads, or unverified rumors, the site takes a much cleaner, developer-friendly approach to tracking character breakdowns, news, and managing expectations.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Makes It Worth Checking Out
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Verified Character Profiles:&lt;/strong&gt; It features clean breakdowns of known game details and official character profiles sourced strictly from Rockstar releases, like &lt;a href="https://leocheats.com/gta-6-characters/lucia/" rel="noopener noreferrer"&gt;Lucia&lt;/a&gt; and &lt;a href="https://leocheats.com/gta-6-characters/jason-duval/" rel="noopener noreferrer"&gt;Jason Duval&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No-Nonsense Guides:&lt;/strong&gt; Rather than pushing fake leaks for PS5 and Xbox Series X|S, the site focuses on realistic expectations and historical context on how past game mechanics worked.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Clean UI &amp;amp; Fast Experience:&lt;/strong&gt; Unlike most cluttered gaming wiki pages filled with intrusive ads and terrible mobile layouts, this site is super fast, modern, and mobile-friendly.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Why Good Curation Matters in the Gaming Space
&lt;/h2&gt;

&lt;p&gt;When a massive title like GTA 6 approaches launch, the web gets flooded with low-quality SEO spam, fake trailer breakdowns, and clickbait articles that waste users' time. Seeing independent platforms that focus on performance, clarity, and actual factual data is pretty refreshing. It proves that fan sites can be both informative and well-engineered without relying on dark patterns or bloated ad networks.&lt;/p&gt;




&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;If you're hyped for the game or just want a reliable spot to keep up with official details without wading through rumors, definitely give &lt;a href="https://leocheats.com/" rel="noopener noreferrer"&gt;LeoCheats&lt;/a&gt; a look.&lt;/p&gt;

&lt;p&gt;Have you found any other cool fan sites or resources for tracking the buildup to release? Let me know in the comments below!&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
      <category>discuss</category>
      <category>gamedev</category>
    </item>
    <item>
      <title>Midnight Ramen Lab 🍜 — Interactive Comfort Food Landing Page</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Wed, 05 Aug 2026 15:22:13 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/midnight-ramen-lab-interactive-comfort-food-landing-page-25fp</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/midnight-ramen-lab-interactive-comfort-food-landing-page-25fp</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for &lt;a href="https://dev.to/challenges/frontend-2026-07-29"&gt;Frontend Challenge - Comfort Food Edition, Perfect Landing&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

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

&lt;p&gt;For this challenge, I wanted to capture the ultimate late-night comfort food vibe: a warm, neon-drenched ramen bar landing page called &lt;strong&gt;Midnight Ramen Lab&lt;/strong&gt;, complete with an &lt;strong&gt;interactive noodle bowl builder&lt;/strong&gt;. &lt;/p&gt;

&lt;p&gt;Instead of just a static landing page, I wanted users to experience the joy of customizing their own comfort food right in the browser. Users can mix and match rich broths, artisan noodles, and gourmet toppings (like soft-boiled ajitsuke tamago, crispy nori, and tender chashu pork) to build their dream bowl with real-time visual updates.&lt;/p&gt;

&lt;h2&gt;
  
  
  Features
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Moody Neon Aesthetics:&lt;/strong&gt; Designed with a dark-mode color palette, glowing neon accents, and cozy typography to evoke a late-night street food stall feeling.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Interactive Bowl Customization:&lt;/strong&gt; Powered by lightweight JavaScript state management to let users toggle ingredients dynamically.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fully Responsive:&lt;/strong&gt; Optimized for seamless viewing across mobile, tablet, and desktop screens.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Journey &amp;amp; Process
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Conceptualization &amp;amp; Vibe
&lt;/h3&gt;

&lt;p&gt;I started by defining the emotional goal of the landing page: &lt;strong&gt;comfort and warmth&lt;/strong&gt;. I chose a dark, atmospheric color scheme accented with warm amber, fiery red, and neon teal to mimic a cyberpunk-meets-traditional ramen shop.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Crafting the Layout
&lt;/h3&gt;

&lt;p&gt;Using Tailwind CSS via CDN, I quickly laid out a high-impact hero section featuring bold typography, a mouth-watering call-to-action, and the core interactive workspace. &lt;/p&gt;

&lt;h3&gt;
  
  
  3. Implementing Interactivity
&lt;/h3&gt;

&lt;p&gt;The biggest challenge—and the most fun part—was building the interactive noodle builder. I used vanilla JavaScript to listen to user clicks on the topping selections, updating the UI elements instantly to reflect their custom ramen bowl configuration.&lt;/p&gt;

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

&lt;p&gt;This challenge was a fantastic reminder of how micro-interactions and thematic design can completely transform a standard landing page into an engaging user experience. Balancing clean layout design with playful frontend state management was both challenging and rewarding!&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Thanks for checking out my project! Drop your feedback or questions in the comments below.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>frontendchallenge</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Stop Writing Cover Letters From Scratch: How I Automated the Most Annoying Part of Job Hunting</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Sat, 01 Aug 2026 18:27:16 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/stop-writing-cover-letters-from-scratch-how-i-automated-the-most-annoying-part-of-job-hunting-p4e</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/stop-writing-cover-letters-from-scratch-how-i-automated-the-most-annoying-part-of-job-hunting-p4e</guid>
      <description>&lt;p&gt;Job hunting is exhausting. Between tweaking resumes, updating portfolios, and filling out endless application forms, the absolute worst part has always been &lt;strong&gt;writing a custom cover letter for every single role&lt;/strong&gt;. &lt;/p&gt;

&lt;p&gt;Let's be honest: &lt;strong&gt;nobody wants to write them&lt;/strong&gt;, and recruiters rarely want to read generic templates. &lt;/p&gt;

&lt;p&gt;A few weeks ago, I finally snapped after spending an entire evening staring at a blank document trying to sound "professionally passionate" about a company I barely knew. I decided to build a quick utility tool for myself called &lt;strong&gt;&lt;a href="https://coverforge.io" rel="noopener noreferrer"&gt;CoverForge&lt;/a&gt;&lt;/strong&gt; just to pipe my resume and a job description into an LLM and get a &lt;strong&gt;tailored draft instantly&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;It turned out to be a &lt;strong&gt;massive time-saver&lt;/strong&gt;. Instead of wasting hours tailoring buzzwords, it structures a clean, compelling draft in seconds that actually sounds human. &lt;/p&gt;

&lt;p&gt;If you are currently applying for roles and drowning in boilerplate text, here is my advice: &lt;strong&gt;stop doing it manually&lt;/strong&gt;. You can check out &lt;strong&gt;&lt;a href="https://coverforge.io" rel="noopener noreferrer"&gt;CoverForge&lt;/a&gt;&lt;/strong&gt; to handle the heavy lifting of tailoring cover letters so you can &lt;strong&gt;focus on actual interview prep&lt;/strong&gt;. &lt;/p&gt;

&lt;p&gt;How do you usually handle cover letters? Let me know your workflow in the comments below!&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
      <category>beginners</category>
      <category>showdev</category>
    </item>
    <item>
      <title>The Junior Developer Pipeline Is Broken... And AI Broke It</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Wed, 29 Jul 2026 18:20:33 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/the-junior-developer-pipeline-is-broken-and-ai-broke-it-4i19</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/the-junior-developer-pipeline-is-broken-and-ai-broke-it-4i19</guid>
      <description>&lt;p&gt;Every senior developer, engineering manager, and tech recruiter I’ve talked to recently is echoing the exact same sentiment: &lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"We just don't have the bandwidth to onboard entry-level developers right now when AI can write boilerplate code, draft unit tests, and refactor functions in seconds."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;On paper, it sounds like peak efficiency. Companies save budgets, mid/senior devs move faster, and code gets shipped. But if you look just two inches past your nose, there is a massive, terrifying crisis looming over our industry:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If we stop hiring and training junior developers today, where do senior engineers come from five years from now?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We are actively sawing off the bottom rongs of the software engineering career ladderBilkul! Aapse seedha optimized aur full-length draft share kar raha hoon. &lt;/p&gt;

&lt;p&gt;Iss expanded draft mein &lt;strong&gt;~1,200+ words&lt;/strong&gt; hain, clean structure hai, aur &lt;strong&gt;Point 3 aur 4 ke beech ek dedicated section&lt;/strong&gt; bana diya hai jahan aap dev.to ki kisi purani post, project, ya related topic ka internal link insert kar sakte hain.&lt;/p&gt;




&lt;h3&gt;
  
  
  📄 Complete Markdown Body
&lt;/h3&gt;

&lt;p&gt;markdown&lt;br&gt;
Every senior software engineer, tech lead, and hiring manager I’ve spoken with over the last few months seems to be coming to the exact same conclusion: &lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"We simply don't have the bandwidth, time, or budget to onboard entry-level developers right now—not when modern AI tools can generate boilerplate code, draft suite tests, and refactor functions in a fraction of a second."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;On paper, this shift looks like the ultimate win for software business efficiency. Engineering budgets are trimmed, senior teams report faster sprint cycles, and software gets pushed to production faster than ever. But if you step back and look at the larger trajectory of our industry, a critical problem emerges:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If tech companies stop hiring, mentoring, and retaining junior engineers today, where will the next generation of senior engineers come from five years down the line?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We are actively dismantling the foundational steps of the software engineering career ladder while falsely assuming that everyone can simply remain at the top forever.&lt;/p&gt;




&lt;h3&gt;
  
  
  💡 Table of Contents
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;1. The Extinction of Traditional "Junior" Tasks&lt;/li&gt;
&lt;li&gt;2. The Unrealistic Velocity Expectation Gap&lt;/li&gt;
&lt;li&gt;3. The Illusion of Competence &amp;amp; Synthetic Debugging Debt&lt;/li&gt;
&lt;li&gt;🔗 Deep Dive: Related Reading &amp;amp; Architecture Case Studies&lt;/li&gt;
&lt;li&gt;4. Rebuilding the Pipeline: What Needs to Change&lt;/li&gt;
&lt;li&gt;💬 Join the Discussion&lt;/li&gt;
&lt;/ul&gt;




&lt;h3&gt;
  
  
  1. The Extinction of Traditional "Junior" Tasks
&lt;/h3&gt;

&lt;p&gt;Historically, software engineers did not master system design by reading books or watching lectures—they built their mental models by tackling grunt work. Junior developers steadily gained confidence and mapped out complex codebases by handling essential, repetitive tasks:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Writing basic unit tests and increasing test coverage&lt;/li&gt;
&lt;li&gt;Squashing minor CSS alignment bugs and front-end quirks&lt;/li&gt;
&lt;li&gt;Migrating legacy code patterns to updated syntax&lt;/li&gt;
&lt;li&gt;Updating outdated internal API documentation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Today, AI coding assistants and autonomous agents process these exact tasks in moments. Because these introductory assignments have been fully automated, the barrier to entering the industry has skyrocketed overnight. The safe runway where new developers once learned, made mistakes, and matured as engineers has largely vanished.&lt;/p&gt;




&lt;h3&gt;
  
  
  2. The Unrealistic Velocity Expectation Gap
&lt;/h3&gt;

&lt;p&gt;Because generative tools make code output nearly instantaneous, project leaders and executives now expect fresh graduates to deliver with the output velocity of mid-level engineers right from their first week.&lt;/p&gt;

&lt;p&gt;We are placing developers who are still building their technical fundamentals into complex environments and expecting them to navigate distributed systems without support. When a beginner is dropped into a massive microservices setup, AI won't save them from fundamental mistakes—it will merely supply plausible-sounding solutions that the engineer doesn't yet know how to evaluate or test.&lt;/p&gt;




&lt;h3&gt;
  
  
  3. The Illusion of Competence &amp;amp; Synthetic Debugging Debt
&lt;/h3&gt;

&lt;p&gt;This dynamic gives rise to one of the most dangerous hidden threats in modern software development: &lt;strong&gt;The Illusion of Competence.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Early-career engineers are increasingly relying on AI models to generate code blocks that they don't fully comprehend. The generated code might look clean, pass surface-level linters, and get approved during quick reviews. However, when those modules hit unexpected edge cases in live production, the developer lacks the underlying mental framework needed to diagnose the failure.&lt;/p&gt;

&lt;p&gt;True debugging skills aren't built on syntax memorization; they require a deep mental model of memory behavior, network calls, state execution, and logic flow. Prompting an AI assistant cannot substitute for hands-on experience when diagnosing a core architectural failure.&lt;/p&gt;




&lt;h3&gt;
  
  
  🔗 Deep Dive: Martin Fowler’s classic guide on Refactoring and System Design
&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;📌 Related Reading: If you want to understand how developer roles evolve with automation, I highly recommend reading Martin Fowler’s classic guide on &lt;a href="https://martinfowler.com/architecture/" rel="noopener noreferrer"&gt;Refactoring and System Design&lt;/a&gt;, which breaks down why fundamental architectural design matters more than fast code generation.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h3&gt;
  
  
  4. Rebuilding the Pipeline: What Needs to Change
&lt;/h3&gt;

&lt;p&gt;We cannot eliminate AI from developer workflows, nor should we try—it remains an extraordinary force multiplier when applied correctly. However, engineering culture must evolve to accommodate this new reality:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Shift Mentorship Toward Code Auditing:&lt;/strong&gt; Senior developers should shift their focus from teaching juniors &lt;em&gt;how to write syntax&lt;/em&gt; to guiding them on &lt;em&gt;how to review, audit, and evaluate AI-generated architectures&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Treat Onboarding as Talent Sustainability:&lt;/strong&gt; Companies must recognize that hiring junior engineers was never meant to yield immediate financial returns; it is an essential investment in long-term engineering sustainability.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Overhaul Computer Science &amp;amp; Bootcamp Curricula:&lt;/strong&gt; Educational programs need to move away from teaching basic CRUD app generation and prioritize real-world debugging, system architecture, and AI output validation.&lt;/li&gt;
&lt;/ol&gt;




&lt;h3&gt;
  
  
  💬 Join the Discussion
&lt;/h3&gt;

&lt;p&gt;I would love to hear how your engineering organization is approaching this shift:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;For Senior Devs &amp;amp; Engineering Managers:&lt;/strong&gt; How is your team adapting its hiring and mentorship strategies? Are you still opening entry-level positions?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;For Juniors &amp;amp; Career Switchers:&lt;/strong&gt; How are you navigating the current market? What steps are you taking to demonstrate value beyond code generation?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Leave your thoughts in the comments below—I’ll be active and replying to every perspective!&lt;/em&gt;&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>ai</category>
      <category>programming</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Tool definitions as untrusted input makes total sense! Metadata/schema injections are real risk as MCP ecosystems grow. Are you implementing signature verification or cryptographically signed manifests to enforce provenance?</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Wed, 29 Jul 2026 17:37:33 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/tool-definitions-as-untrusted-input-makes-total-sense-metadataschema-injections-are-real-risk-as-12g7</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/tool-definitions-as-untrusted-input-makes-total-sense-metadataschema-injections-are-real-risk-as-12g7</guid>
      <description></description>
      <category>programming</category>
      <category>coding</category>
      <category>softwareengineering</category>
      <category>webdev</category>
    </item>
    <item>
      <title>The point about AI deleting the curriculum rather than just the work is spot on. Essential read for engineering leads trying to figure out where future senior devs will come from.</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Wed, 29 Jul 2026 17:16:24 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/the-point-about-ai-deleting-the-curriculum-rather-than-just-the-work-is-spot-on-essential-read-for-2567</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/the-point-about-ai-deleting-the-curriculum-rather-than-just-the-work-is-spot-on-essential-read-for-2567</guid>
      <description>&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/nazar-boyko/the-junior-developer-pipeline-is-broken-and-ai-broke-it-1aai" class="crayons-story__hidden-navigation-link"&gt;The Junior Developer Pipeline Is Broken... And AI Broke It&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
      &lt;a href="https://dev.to/nazar-boyko/the-junior-developer-pipeline-is-broken-and-ai-broke-it-1aai" class="crayons-article__context-note crayons-article__context-note__feed"&gt;&lt;p&gt;Deletes the career ladder&lt;/p&gt;

&lt;/a&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/nazar-boyko" class="crayons-avatar  crayons-avatar--l  "&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%2Fuser%2Fprofile_image%2F1875383%2F1b3f5dc9-df1c-4551-9f6e-e3b6234b3d6c.gif" alt="nazar-boyko profile" class="crayons-avatar__image"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/nazar-boyko" class="crayons-story__secondary fw-medium m:hidden"&gt;
              Nazar Boyko
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                Nazar Boyko
                
                
              
              &lt;div id="story-author-preview-content-4240237" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/nazar-boyko" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&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%2Fuser%2Fprofile_image%2F1875383%2F1b3f5dc9-df1c-4551-9f6e-e3b6234b3d6c.gif" class="crayons-avatar__image" alt=""&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;Nazar Boyko&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/nazar-boyko/the-junior-developer-pipeline-is-broken-and-ai-broke-it-1aai" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Jul 27&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/nazar-boyko/the-junior-developer-pipeline-is-broken-and-ai-broke-it-1aai" id="article-link-4240237"&gt;
          The Junior Developer Pipeline Is Broken... And AI Broke It
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag crayons-tag--filled  " href="/t/discuss"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;discuss&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/ai"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;ai&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/career"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;career&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/programming"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;programming&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/nazar-boyko/the-junior-developer-pipeline-is-broken-and-ai-broke-it-1aai" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/raised-hands-74b2099fd66a39f2d7eed9305ee0f4553df0eb7b4f11b01b6b1b499973048fe5.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/fire-f60e7a582391810302117f987b22a8ef04a2fe0df7e3258a5f49332df1cec71e.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;267&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/nazar-boyko/the-junior-developer-pipeline-is-broken-and-ai-broke-it-1aai#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              217&lt;span class="hidden s:inline"&gt;&amp;nbsp;comments&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            9 min read
          &lt;/small&gt;
          
          &lt;div class="only-sidebar-menu-item trusted-visible-block print-hidden align-center"&gt;
                
                    
                
          &lt;/div&gt;

        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;


</description>
    </item>
    <item>
      <title>How an Unindexed Column Silently Killed Our Database under Load (and the 5-Minute Fix)</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Wed, 29 Jul 2026 13:00:00 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/how-an-unindexed-column-silently-killed-our-database-under-load-and-the-5-minute-fix-m32</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/how-an-unindexed-column-silently-killed-our-database-under-load-and-the-5-minute-fix-m32</guid>
      <description>&lt;h2&gt;
  
  
  How a Missing Database Index Turned an 8ms API into an 8-Second Nightmare
&lt;/h2&gt;

&lt;p&gt;Every developer has a fear of the silent killer: a bug that doesn’t throw a &lt;strong&gt;500 error&lt;/strong&gt; or crash your server immediately, but slowly chokes your application until your database connections completely freeze under heavy traffic.&lt;/p&gt;

&lt;p&gt;This is the story of how a single missing index on a foreign key brought down our staging API during a load test—and how a simple &lt;strong&gt;5-minute fix&lt;/strong&gt; brought response times down from &lt;strong&gt;8 seconds to 12ms&lt;/strong&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  😱 The Incident: Connection Timeout &amp;amp; 100% DB CPU
&lt;/h2&gt;

&lt;p&gt;It all started during a routine load test prior to a major feature release. Everything ran smoothly in local development with &lt;strong&gt;100 sample records&lt;/strong&gt;, but as soon as we simulated &lt;strong&gt;500 concurrent users&lt;/strong&gt; against production-sized data (around &lt;strong&gt;1.5 million rows&lt;/strong&gt;):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;API Response Times&lt;/strong&gt; exploded from &lt;strong&gt;45ms&lt;/strong&gt; to over &lt;strong&gt;8,000ms&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Database CPU&lt;/strong&gt; hit &lt;strong&gt;100%&lt;/strong&gt; and stayed pinned there.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Connection Pool Exhaustion:&lt;/strong&gt; Requests started timing out with &lt;strong&gt;ETIMEDOUT&lt;/strong&gt; errors because every database connection was stuck waiting on open queries.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  🔍 The Investigation: Uncovering the Full Table Scan
&lt;/h2&gt;

&lt;p&gt;We pulled up query performance metrics and looked at the slow query log. The offending endpoint was &lt;strong&gt;&lt;code&gt;/api/v1/orders/history&lt;/code&gt;&lt;/strong&gt;, which fetches recent orders for a user filtered by status.&lt;/p&gt;

&lt;h3&gt;
  
  
  📦 Express.js Route
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Express.js route handling user order history&lt;/span&gt;
&lt;span class="nx"&gt;app&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="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;/api/v1/orders/history&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;async &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;userId&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;status&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;query&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

  &lt;span class="k"&gt;try&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;orders&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;db&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;query&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
      &lt;span class="s2"&gt;`SELECT * FROM orders
       WHERE user_id = $1
         AND status = $2
       ORDER BY created_at DESC
       LIMIT 20`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nx"&gt;userId&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;status&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="p"&gt;);&lt;/span&gt;

    &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
      &lt;span class="na"&gt;success&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;data&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;orders&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;rows&lt;/span&gt;
    &lt;span class="p"&gt;});&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;catch &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;err&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;status&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;500&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
      &lt;span class="na"&gt;error&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Database query timed out&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;
    &lt;span class="p"&gt;});&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;When we ran &lt;strong&gt;&lt;code&gt;EXPLAIN ANALYZE&lt;/code&gt;&lt;/strong&gt; on PostgreSQL for that query, the diagnosis was brutal.&lt;/p&gt;

&lt;h3&gt;
  
  
  📦 Query Plan (Before Index)
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;QUERY PLAN
----------------------------------------------------------------------------------
Seq Scan on orders  (cost=0.00..38420.00 rows=15 width=128)
(actual time=412.304..8150.120 rows=20 loops=1)

Filter: ((user_id = 10482)
      AND ((status)::text = 'completed'::text))

Rows Removed by Filter: 1499980

Planning Time: 0.182 ms
Execution Time: 8150.210 ms
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Because there was &lt;strong&gt;no index on &lt;code&gt;user_id&lt;/code&gt;&lt;/strong&gt;, PostgreSQL had to perform a &lt;strong&gt;Sequential Scan&lt;/strong&gt;, reading through all &lt;strong&gt;1.5 million rows&lt;/strong&gt; for every single API request.&lt;/p&gt;

&lt;p&gt;With &lt;strong&gt;100 concurrent requests&lt;/strong&gt;, the database engine was effectively scanning &lt;strong&gt;150 million rows&lt;/strong&gt; simultaneously.&lt;/p&gt;




&lt;h2&gt;
  
  
  🛠️ The Fix: Compound Indexing
&lt;/h2&gt;

&lt;p&gt;The fix was deceptively simple, but choosing the right index mattered.&lt;/p&gt;

&lt;p&gt;Adding an index on only &lt;strong&gt;&lt;code&gt;user_id&lt;/code&gt;&lt;/strong&gt; would improve filtering, but a &lt;strong&gt;composite index&lt;/strong&gt; on &lt;strong&gt;&lt;code&gt;(user_id, status, created_at DESC)&lt;/code&gt;&lt;/strong&gt; allows PostgreSQL to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Filter by &lt;strong&gt;user_id&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Filter by &lt;strong&gt;status&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Return the newest rows immediately&lt;/li&gt;
&lt;li&gt;Avoid an extra sorting step&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  📦 Migration Script
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Database Migration Script (Knex.js)&lt;/span&gt;
&lt;span class="nx"&gt;exports&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;up&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="nf"&gt;function &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;knex&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="c1"&gt;// Build the index without blocking writes&lt;/span&gt;
  &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;knex&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;raw&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;`
    CREATE INDEX CONCURRENTLY IF NOT EXISTS
    idx_orders_user_status_created
    ON orders (user_id, status, created_at DESC);
  `&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;blockquote&gt;
&lt;p&gt;💡 &lt;strong&gt;Pro Tip:&lt;/strong&gt; In production, build indexes using &lt;strong&gt;&lt;code&gt;CONCURRENTLY&lt;/code&gt;&lt;/strong&gt; whenever possible so PostgreSQL doesn't lock the table for incoming writes while creating the index.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  📊 The Results
&lt;/h2&gt;

&lt;p&gt;Running &lt;strong&gt;&lt;code&gt;EXPLAIN ANALYZE&lt;/code&gt;&lt;/strong&gt; after the index was created:&lt;/p&gt;

&lt;h3&gt;
  
  
  📦 Query Plan (After Index)
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;QUERY PLAN
----------------------------------------------------------------------------------
Index Scan using idx_orders_user_status_created on orders
(cost=0.43..8.45 rows=20 width=128)
(actual time=0.042..0.118 rows=20 loops=1)

Planning Time: 0.085 ms
Execution Time: 0.142 ms
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h4&gt;
  
  
  🚀 Performance Improvements
&lt;/h4&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Query Execution Time:&lt;/strong&gt; &lt;strong&gt;8,150ms ➜ 0.14ms&lt;/strong&gt; (&lt;strong&gt;99.9% faster&lt;/strong&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;API Latency:&lt;/strong&gt; &lt;strong&gt;8 seconds ➜ 12ms&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Database CPU Usage:&lt;/strong&gt; &lt;strong&gt;100% ➜ under 8%&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Connection Pool:&lt;/strong&gt; No more timeout errors under load&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  💡 Key Takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Local development can be misleading.&lt;/strong&gt; Queries that perform perfectly on &lt;strong&gt;100 rows&lt;/strong&gt; may completely fall apart with &lt;strong&gt;1,000,000+ rows&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Index your foreign keys.&lt;/strong&gt; Many ORMs don't automatically create indexes for columns like &lt;code&gt;user_id&lt;/code&gt;, &lt;code&gt;tenant_id&lt;/code&gt;, or &lt;code&gt;organization_id&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Always use &lt;code&gt;EXPLAIN ANALYZE&lt;/code&gt;.&lt;/strong&gt; Before upgrading hardware or increasing database resources, inspect the execution plan. The database usually tells you exactly what's wrong.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Design indexes around your queries&lt;/strong&gt;, not just your schema.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  🧠 Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Performance problems don't always come from bad code.&lt;/p&gt;

&lt;p&gt;Sometimes, a &lt;strong&gt;single missing database index&lt;/strong&gt; is enough to turn a fast API into an unusable one under real traffic.&lt;/p&gt;

&lt;p&gt;Before scaling your infrastructure, make sure you've optimized your queries.&lt;/p&gt;

&lt;p&gt;Your database—and your future self—will thank you.&lt;/p&gt;




&lt;p&gt;If this post helped you, consider dropping a ❤️ and sharing your own database performance horror story in the comments.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Remember:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Don't scale your servers...&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Scale your queries first.&lt;/strong&gt; 🚀&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Happy coding! 💙&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>database</category>
      <category>javascript</category>
      <category>performance</category>
    </item>
    <item>
      <title>How a Silent N+1 Query Almost Melted Our Production Database (and How We Smashed It)</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Tue, 28 Jul 2026 10:22:48 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/how-a-silent-n1-query-almost-melted-our-production-database-and-how-we-smashed-it-49no</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/how-a-silent-n1-query-almost-melted-our-production-database-and-how-we-smashed-it-49no</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for &lt;a href="https://dev.to/bugsmash"&gt;DEV's Summer Bug Smash: Smash Stories&lt;/a&gt; powered by &lt;a href="https://sentry.io/" rel="noopener noreferrer"&gt;Sentry&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Every developer fears the silent killer: a bug that doesn’t throw a 500 Internal Server Error, doesn't crash the server instantly, but quietly turns your API into a slow, memory-choking nightmare.&lt;/p&gt;

&lt;p&gt;This is the story of how a seemingly harmless 3-line code change triggered an N+1 query monster, and how we used Sentry performance monitoring to track it down and smash it before a major launch.&lt;/p&gt;




&lt;h2&gt;
  
  
  😱 The Incident: High Latency &amp;amp; Spiking CPU
&lt;/h2&gt;

&lt;p&gt;It started on a Tuesday afternoon. Users began reporting that our dashboard's "Recent Activity" feed was taking 6–8 seconds to load. &lt;/p&gt;

&lt;p&gt;Looking at our metrics:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;API response times&lt;/strong&gt; shot up from &lt;strong&gt;120ms&lt;/strong&gt; to &lt;strong&gt;6,500ms&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Database CPU utilization&lt;/strong&gt; spiked to 92%.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zero exceptions&lt;/strong&gt; were being thrown. Everything technically "worked"—it was just painfully slow.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  🔍 The Investigation: Following the Traces
&lt;/h2&gt;

&lt;p&gt;We pulled up Sentry Performance Tracing to inspect the API endpoint &lt;code&gt;/api/v1/user/activity&lt;/code&gt;. &lt;/p&gt;

&lt;p&gt;When we looked at the waterfall span breakdown, the problem jumped out immediately:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&lt;/code&gt; &lt;code&gt;&lt;br&gt;
[GET] /api/v1/user/activity&lt;br&gt;
  └── SELECT * FROM activities LIMIT 50           ( 15ms )&lt;br&gt;
  └── SELECT * FROM users WHERE id = 12           ( 12ms )&lt;br&gt;
  └── SELECT * FROM users WHERE id = 18           ( 14ms )&lt;br&gt;
  └── SELECT * FROM users WHERE id = 42           ( 11ms )&lt;br&gt;
  ... (47 identical individual queries later) ...&lt;br&gt;
&lt;/code&gt; &lt;code&gt;&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Instead of fetching all user profiles in a single query, the application was executing &lt;strong&gt;one query for the activity feed, plus 50 additional database queries&lt;/strong&gt;—one for every single user row!&lt;/p&gt;




&lt;h2&gt;
  
  
  🐛 The Root Cause
&lt;/h2&gt;

&lt;p&gt;A quick &lt;code&gt;git blame&lt;/code&gt; revealed a pull request merged earlier that day. A well-intentioned cleanup in our serializer removed eager loading:&lt;/p&gt;

&lt;h3&gt;
  
  
  ❌ Before (Broken Code):
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;&lt;/code&gt; `javascript&lt;br&gt;
// Missing eager loading of the user relation!&lt;br&gt;
const activities = await Activity.findAll({&lt;br&gt;
  limit: 50,&lt;br&gt;
  order: [['createdAt', 'DESC']]&lt;br&gt;
});&lt;/p&gt;

&lt;p&gt;const response = await Promise.all(&lt;br&gt;
  activities.map(async (activity) =&amp;gt; ({&lt;br&gt;
    id: activity.id,&lt;br&gt;
    action: activity.action,&lt;br&gt;
    user: await activity.getUser() // 💥 50 separate DB calls in a loop!&lt;br&gt;
  }))&lt;br&gt;
);&lt;br&gt;
&lt;code&gt; &lt;/code&gt; `&lt;/p&gt;




&lt;h2&gt;
  
  
  🛠️ The Smash: Fixing the Leak
&lt;/h2&gt;

&lt;p&gt;To fix this, we updated the query to use &lt;strong&gt;eager loading&lt;/strong&gt; (JOIN), fetching all related user data in &lt;strong&gt;a single SQL query&lt;/strong&gt;:&lt;/p&gt;

&lt;h3&gt;
  
  
  ✅ After (Fixed Code):
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;&lt;/code&gt; `javascript&lt;br&gt;
const activities = await Activity.findAll({&lt;br&gt;
  limit: 50,&lt;br&gt;
  order: [['createdAt', 'DESC']],&lt;br&gt;
  include: [{ model: User, attributes: ['id', 'username', 'avatar'] }] // 🚀 Single JOIN query&lt;br&gt;
});&lt;/p&gt;

&lt;p&gt;const response = activities.map((activity) =&amp;gt; ({&lt;br&gt;
  id: activity.id,&lt;br&gt;
  action: activity.action,&lt;br&gt;
  user: activity.User&lt;br&gt;
}));&lt;br&gt;
&lt;code&gt; &lt;/code&gt; `&lt;/p&gt;




&lt;h2&gt;
  
  
  📊 The Results
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Database Queries:&lt;/strong&gt; Reduced from &lt;strong&gt;51 queries&lt;/strong&gt; down to &lt;strong&gt;1 single query&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Response Time:&lt;/strong&gt; Dropped from &lt;strong&gt;6,500ms ➡️ 85ms&lt;/strong&gt; (a &lt;strong&gt;98.6% speedup!&lt;/strong&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DB CPU Load:&lt;/strong&gt; Plummeted back down to normal levels (&amp;lt; 15%).&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  💡 Lessons Learned
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Beware of async operations inside loops/maps:&lt;/strong&gt; Whenever you see &lt;code&gt;await&lt;/code&gt; inside a &lt;code&gt;.map()&lt;/code&gt;, double-check if you're causing an N+1 problem.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Monitor transaction spans:&lt;/strong&gt; Errors aren't the only metric that matters. Sentry’s performance spans and transaction traces saved us hours of blind guessing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Set up query thresholds:&lt;/strong&gt; Catching query bloat in staging before it hits production is the ultimate flex!&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>devchallenge</category>
      <category>bugsmash</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Struggling to manage workload boundaries? Here are 4 easy templates to turn down extra tasks professionally!</title>
      <dc:creator>Mia Keller</dc:creator>
      <pubDate>Tue, 28 Jul 2026 10:07:30 +0000</pubDate>
      <link>https://dev.to/mia_keller_ffd2584c046ecb/struggling-to-manage-workload-boundaries-here-are-4-easy-templates-to-turn-down-extra-tasks-12ld</link>
      <guid>https://dev.to/mia_keller_ffd2584c046ecb/struggling-to-manage-workload-boundaries-here-are-4-easy-templates-to-turn-down-extra-tasks-12ld</guid>
      <description>&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/mia_keller_ffd2584c046ecb/how-to-say-no-at-work-without-looking-lazy-or-unhelpful-1jhb" class="crayons-story__hidden-navigation-link"&gt;How to Say "No" at Work Without Looking Lazy or Unhelpful&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/mia_keller_ffd2584c046ecb" class="crayons-avatar  crayons-avatar--l  "&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%2Fuser%2Fprofile_image%2F4008633%2Fbe4e1f06-5ae2-4b3c-95e1-446ae32be7df.png" alt="mia_keller_ffd2584c046ecb profile" class="crayons-avatar__image"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/mia_keller_ffd2584c046ecb" class="crayons-story__secondary fw-medium m:hidden"&gt;
              Mia Keller
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                Mia Keller
                
              
              &lt;div id="story-author-preview-content-4252851" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/mia_keller_ffd2584c046ecb" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&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%2Fuser%2Fprofile_image%2F4008633%2Fbe4e1f06-5ae2-4b3c-95e1-446ae32be7df.png" class="crayons-avatar__image" alt=""&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;Mia Keller&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/mia_keller_ffd2584c046ecb/how-to-say-no-at-work-without-looking-lazy-or-unhelpful-1jhb" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Jul 28&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/mia_keller_ffd2584c046ecb/how-to-say-no-at-work-without-looking-lazy-or-unhelpful-1jhb" id="article-link-4252851"&gt;
          How to Say "No" at Work Without Looking Lazy or Unhelpful
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/productivity"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;productivity&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/career"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;career&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/workplace"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;workplace&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/softskills"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;softskills&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/mia_keller_ffd2584c046ecb/how-to-say-no-at-work-without-looking-lazy-or-unhelpful-1jhb" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;1&lt;span class="hidden s:inline"&gt;&amp;nbsp;reaction&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/mia_keller_ffd2584c046ecb/how-to-say-no-at-work-without-looking-lazy-or-unhelpful-1jhb#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              1&lt;span class="hidden s:inline"&gt;&amp;nbsp;comment&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            2 min read
          &lt;/small&gt;
            
              &lt;span class="bm-initial crayons-icon c-btn__icon"&gt;
                

              &lt;/span&gt;
              &lt;span class="bm-success crayons-icon c-btn__icon"&gt;
                

              &lt;/span&gt;
            
        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;


</description>
    </item>
  </channel>
</rss>
