TLDR The Clean Architecture is a way of separating responsibilities and parts of functionality according to their proximity to the application domain. It is often referred to as a three-layer architecture, because the functionality in it is divided into layers. In this post we'll talk about what the clean architecture is in general and get familiar with such concepts as domain, use case and application layers. Then we'll discuss how this applies to the frontend and whether it's worth it at all.

TLDR Design patterns are descriptive, not prescriptive. They can guide you when facing a problem other developers have encountered many times before. They are not a blunt tool for jamming into every scenario. Patterns.dev aims to be a catalog of patterns (for increasing awareness) rather than a checklist (what you must do)

TLDR The volume of questions on StackOverflow has significantly declined since the release of ChatGPT in November 2022. This trend, which began before the pandemic, highlights how LLMs (large language models) provide quicker and more effective solutions for developers. Criticism of StackOverflow's moderation policies has also contributed to the downturn. The decrease in questions may lead to outdated content and a vicious cycle of reduced search engine traffic. StackOverflow's situation underscores the disruptive impact of GenAI on stable businesses. The future of coding Q&A data for LLMs remains uncertain.

Paperless-ngx is a document management system that transforms your physical documents into a searchable online archive so you can keep, well, less paper.

Paperless-ngx is the official successor to the original Paperless & Paperless-ng projects and is designed to distribute the responsibility of advancing and supporting the project among a team of people.

TLDR The post discusses the author's decision to move away from Google's ecosystem due to privacy concerns, the desire to explore innovative alternatives, and support for open source solutions. It outlines various Google services and suggests alternatives like ProtonMail for email, DuckDuckGo for search, and Jitsi Meet for video conferencing. Replacing Google's document suite, photos, videos, and maps is noted as more challenging.

TLDR Modern web applications rely on real-time data exchange for seamless user experiences. WebSocket and Socket.IO provide persistent, bidirectional communication channels, essential for functionalities such as chat systems, push notifications, and multiplayer games. While WebSocket offers minimal latency and efficient data transfer, Socket.IO enhances WebSocket with auto-reconnection and fallback mechanisms, making it ideal for applications requiring high reliability and real-time updates.

Signing documents digitally should be fast and easy and should be the best practice for every document signed worldwide. This is technically quite easy today, but it also introduces a new party to every signature: The signing tool providers. While this is not a problem in itself, it should make us think about how we want these providers of trust to work. Documenso aims to be the world's most trusted document-signing tool. This trust is built by empowering you to self-host Documenso and review how it works under the hood.

TLDR Guidance for writing clean code includes no code comments, deleting dead code, unit testing boundaries, using positive conditionals, adhering to standard guidelines, consistent naming, avoiding complexity, using exceptions instead of return codes, keeping methods small, and applying the Boy Scout rule to always leave the code cleaner than you found it.

TLDR This post provides an in-depth explanation of API design, focusing on the basics and best practices. It covers topics such as CRUD operations, communication protocols, REST, GraphQL, and more.

TLDR While working on a real-life project, the author encountered a TypeScript implementation that lacked flexibility. They improved the design using the Map pattern, which reduced redundancy and potential errors by allowing dynamic additions. Further, stricter controls were applied to ensure only predefined reactions can be added. This approach balances flexibility and control, enhancing code maintainability.

TLDR The post provides a comprehensive guide to building an analytical dashboard using Next.js, Flexmonster, and Highcharts. It includes step-by-step instructions on configuring these tools, creating charts, and setting up a functional user interface. Additionally, it explores real-world survey data on passenger flying etiquette to demonstrate the dashboard's capabilities.