Joud Awad·9wFree e-book with 60 scenario-based system design interview questions
A free e-book of 60+ scenario-based system design interview questions, designed to go beyond memorizing architectures and focus on tradeoffs — like handling 10x traffic, eventual consistency costs, and queue usage patterns. Questions range from beginner-friendly to advanced, useful both for interview prep and for pressure-testing assumptions in production systems.
Nestjs Developers·6wDay 1/30 — Why NestJS?
A brief introductory post kicking off a 30-day NestJS series. The core argument is that NestJS's real value lies in providing structural conventions — modules, providers, guards, pipes, and interceptors — that give teams a shared way to build, preventing the chaos of multiple developers inventing different architectures in the same codebase. NestJS doesn't guarantee good architecture, but it gives it a place to live.
DEVCLASS·8wHTTP gets a QUERY method so complex searches can stop pretending to be POST
The IETF has officially published RFC 10008, introducing a new HTTP request method called QUERY. It fills a long-standing gap: complex search queries have historically been sent via POST (which is neither safe nor idempotent) or crammed into unwieldy GET URLs. QUERY combines POST's ability to carry a request body with GET's safe and idempotent semantics, enabling proxies, CDNs, and browsers to cache and automatically retry these requests. Cloudflare and Akamai engineers co-authored the spec. Adoption is still early — HTML forms only support GET and POST, and the broader ecosystem (reverse proxies, load balancers, frameworks) needs updating — but Node.js, Go, and Laravel are already moving toward support.
Medium·8wReact Folder Structure for Beginners: The Folder Organization That Finally Made Sense to Me
A beginner-friendly guide to organizing React projects with a clear folder structure. Covers the purpose of each directory including assets, components, pages, layouts, hooks, context, services, utils, constants, routes, and styles. Also touches on keeping components small, feature-based organization for larger apps, and consistent naming conventions.
BleepingComputer·9wDuckDuckGo browser now blocks YouTube video ads
DuckDuckGo's browser now blocks most YouTube video ads, including pre-roll and mid-roll ads, across iOS, Mac, and Windows by default. Android users must enable it manually in Settings. The feature uses community-maintained filter lists from uBlock Origin, supplemented by DuckDuckGo's own compatibility rules. It works separately from the existing Duck Player feature, and both can be used simultaneously. DuckDuckGo joins Brave and Opera in offering built-in YouTube ad blocking without third-party extensions. Minor buffering delays may occur, and the feature may occasionally break as YouTube changes its ad-serving methods.
Joud Awad·7wDay 1/30 AWS System Design Patterns
A gaming platform leaderboard stored in DynamoDB experiences ThrottlingException errors and high P99 latency on reads for a single dominant game ('battle-royale'), despite CloudWatch showing consumed RCUs well below provisioned capacity. Doubling provisioned RCUs fails to resolve the issue. The root cause is a hot partition: when traffic concentrates on a single partition key, that partition hits its own throughput ceiling regardless of total table-level RCU headroom. The correct answer is C — per-partition limits apply independently of aggregate table provisioning.
freeCodeCamp·9wLevel Up Your React Skills with Typescript
A freeCodeCamp tutorial teaching how to use TypeScript with React, covering TypeScript basics, typing useState, component architecture with custom prop types, and passing typed function props between components. The course walks through refactoring a real-world project to be fully type-safe, improving readability and maintainability. Available as a 1-hour video on YouTube.
daily.dev World·7wAI is everywhere, but is it really what we read the most?
A data-driven look at what developers actually read on daily.dev reveals that JavaScript content gets 2.6 reads per post published, far outpacing AI content which sits at roughly a 1:1 ratio. Despite AI dominating content volume and developer perception (55% of poll respondents guessed AI was the most-read topic), the numbers tell a different story. The analysis used BigQuery SQL to compare each topic's share of posts published against its share of reading to normalize for topic size.
Joud Awad·9w60/60 Days System Design Questions
A system design challenge posing the classic architecture decision for a new SaaS platform needing 50,000 RPS, multi-tenancy, real-time data, global users, and AI inference. Four architectural approaches are presented: distributed microservices from day one, a modular monolith with incremental extraction, serverless with Lambda/DynamoDB/SQS, and event-driven architecture with Kafka as the backbone. This is framed as the final entry in a 60-day system design series, inviting engineers to debate the tradeoffs.
Swapnoneel Saha·8wLinus Torvalds just told the AI haters to fork off. Literally.
Linus Torvalds publicly declared on the Linux kernel mailing list that Linux is not an anti-AI project, telling critics to fork the kernel or walk away. He described AI as a useful tool, noting that anyone who doubts it 'clearly hasn't actually used it.' This marks a notable shift from his stance 21 months ago when he called 90% of AI marketing hype. Senior kernel maintainer Greg Kroah-Hartman echoed the sentiment, saying something shifted about a month ago and AI contributions are now genuinely good. Torvalds acknowledged AI causes maintainer burnout and bugs but rejected outright rejection as the solution, closing with a pointed remark that natural intelligence isn't always great either.
Awesome·7wWeb dev is finally getting good
Several significant web platform developments are converging: Chrome is experimenting with out-of-order HTML streaming via declarative partial updates using processing instruction markers and the template element, enabling servers to deliver page sections as their data becomes available without JavaScript workarounds. Chrome is also experimenting with rendering real DOM elements inside canvas, preserving browser interactions like text selection and accessibility. ECMAScript 2026 has been officially approved, adding Math.sumPrecise, iterator concat, Array.fromAsync, Map.getOrInsert, and improved JSON handling. TypeScript 7.0 has shipped with its compiler fully rewritten in Go, delivering roughly 10x faster build times through native execution, shared memory, and multi-threading — compiling the VS Code codebase dropped from 126 seconds to under 11 seconds.
ExpressoTS·8wExpressoTS 4.0 is officially released
ExpressoTS 4.0 has been released, introducing ExpressoTS Studio — a local developer experience platform providing a status dashboard, architecture map, request timeline with OpenTelemetry tracing, live logs, error inspector, security view (npm audit + OSV.dev), and an API client. The framework is built on Express 5 with TypeScript-first design and an Inversify-compatible DI container. Version 4.0 also brings strict TypeScript configs, leaner install footprint, subpath exports, optional validator peers (zod/yup/class-validator), and a CI compatibility gate. Studio activates automatically in development with zero production overhead.
InfoWorld·9wECMAScript 2026 specification approved
ECMA International has approved ECMAScript 2026 (ES2026), the 17th edition of the JavaScript specification, on June 30. The new edition introduces several additions: Math.sumPrecise for precise summation of iterables, Iterator.concat for sequencing iterators, Array.fromAsync for building arrays from async sources, Error.isError for identifying error objects, new Map and WeakMap prototype methods for default-value retrieval, Uint8Array methods for hex and base64 string conversion, a JSON.parse reviver parameter for accessing raw JSON source, and JSON.rawJSON for fine-grained control over JSON.stringify output.
Kashitsuwa·7wShiki - Your notes.Your terminal.Actually yours.
shiki is a terminal-based note-taking app inspired by Yazi, featuring a three-pane interface that stays entirely in the terminal. Each notebook is a standalone git repository, giving every note automatic version history without any additional tooling. The UI is fully themeable, and sync, versioning, and organization are all handled natively through git rather than bolted-on proprietary systems.
The Polymathic Engineer·10wWhen to repeat yourself
DRY (Don't Repeat Yourself) is a foundational principle, but removing duplication always has a cost. Across team or service boundaries, the coordination overhead of shared components can outweigh the maintenance burden of duplicated code. Two pieces of code that look identical may represent different business concepts (incidental vs. inherent duplication) and should be left separate. When sharing code across services, a shared library introduces language and dependency coupling, while a microservice adds network latency and operational overhead. Inside a codebase, inheritance creates rigid coupling that breaks down when subclasses need to diverge, while composition offers flexibility at the cost of complexity. The key insight: merging duplicated code later is easy, but splitting a shared abstraction with many callers is hard. When in doubt, let the duplication live until the right abstraction emerges from real evidence.
Medium·7wWhy I Build Software Like I’m Going to Maintain It for 10 Years
A senior developer's philosophy on writing software for long-term maintainability. Key principles include prioritizing readability over cleverness, treating naming as documentation, writing comments that explain 'why' not 'what', choosing boring but appropriate architecture, respecting the cost of dependencies, investing in documentation and tests, and designing APIs that feel natural. The core mindset shift: write code for your future self who has forgotten all context, not for your present self who understands everything.
Joud Awad·10w57/60 Days System Design Questions
A system design challenge presents a high-traffic scenario with 50k writes/sec and 500k reads/sec on a Postgres setup with one primary and two async replicas. The problem: a payment confirmation flow reads stale data from a replica due to 80–300ms replication lag. Four options are presented to achieve read-after-write consistency without sacrificing write throughput: synchronous replication, semi-sync replication, routing payment reads to the primary, or adding a sleep delay after writes.
Hacker News·9wWhy developers are ditching GitHub for Codeberg and self-hosting alternatives
GitHub remains dominant by the numbers, but a growing number of open source projects are migrating away due to concerns over frequent downtime, Microsoft's ownership, AI training on code, and political direction. High-profile departures include Ghostty (a terminal emulator), Tenacity (an audio editor), the Dillo browser, and the Hare programming language. Alternatives gaining traction include Codeberg (powered by Forgejo), Sourcehut, Gitea, and self-hosted forges. The Software Freedom Conservancy also runs an active campaign encouraging developers to leave GitHub.
Nestjs Developers·6wDay 2/30 — Keep Controllers Thin
A short reminder about the single responsibility principle applied to controllers in backend frameworks like NestJS. Controllers should only handle HTTP concerns — accepting requests, reading context, delegating work, and returning responses. When a controller starts containing business logic like price calculation, transaction management, or email sending, it has grown beyond its intended role. The post encourages keeping controllers thin by delegating business logic to dedicated service layers.
Joud Awad·10w56/60 Days System Design Questions
Long-running background jobs break assumptions built for synchronous APIs. Using a video upload scenario (2–8 minutes, millions of users), four client notification strategies are compared: polling, webhooks, SSE/WebSocket, and synchronous wait. Beyond transport choice, four critical design problems are highlighted that teams typically get wrong: idempotency (safe retries), progress granularity (meaningful intermediate states), distinguishing timeout from failure (heartbeats/visibility timeouts), and deduplication (scoped dedup keys to prevent double-processing).
Matt Smith·8wI stopped destructuring everything
A developer reflects on moving away from reflexive destructuring in JavaScript. The core argument: destructuring optimizes for writing code, not reading it. Keeping objects intact (e.g., `project.status` instead of `status`) preserves context, especially in larger functions where variables lose their origin. The author still uses destructuring when it genuinely improves vocabulary or removes noise, but now asks whether removing the object makes code easier to understand or just shorter.
