# Concepts Published articles for Concepts. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Domain-Driven Design Clearly Explained DevFeed: [Domain-Driven Design Clearly Explained]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-09-12T12:52:28Z Content type: tutorial Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [Domain-driven design (DDD)](), [Code](), [systems]() Tags: [concepts](), [developers](), [domain](), [domain-driven-design](), [engineering](), [model](), [patterns]() ### AI overview An introduction to Domain-Driven Design (DDD), explaining how shared business language and bounded contexts help teams model complex products and keep code aligned with the domain. ### Source excerpt The mental model that makes DDD click. ## 6 Benefits of Sandbox Environments (and How Docker Sandboxes Delivers Them) DevFeed: [6 Benefits of Sandbox Environments (and How Docker Sandboxes Delivers Them)]() Original publisher: [Read original article]() Author: Kevin Wittek Published: 2026-09-08T23:05:55Z Content type: article Language: en Sources: [Docker]() Topics: [Docker](), [Authorization]() Tags: [agentic-ai](), [ai-agents](), [ai-ml](), [autonomous](), [concepts](), [docker-ai-governance](), [docker-sandboxes](), [linux](), [policy](), [products](), [sandbox](), [secrets]() ### AI overview The article explains how Docker Sandboxes isolate untrusted code and autonomous AI agents from host machines and external systems. It highlights runtime policy controls, credential handling, disposability, and microVM-based isolation. ### Source excerpt Learn about the key benefits of sandbox environments with Docker including isolation, definable controls, secrets credential handling, and more. ## YOLO Mode: Agent Autonomy Without the Guardrails DevFeed: [YOLO Mode: Agent Autonomy Without the Guardrails]() Original publisher: [Read original article]() Author: Srini Sekaran Published: 2026-09-03T18:00:00Z Content type: article Language: en Sources: [Docker]() Topics: [AI-assisted coding](), [Authorization](), [Command-line interface](), [cursor](), [GitHub Copilot CLI](), [Claude]() Tags: [agentic-ai](), [ai-agent](), [cli](), [concepts](), [cursor](), [docker-ai-governance](), [docker-sandboxes](), [products](), [sandbox](), [secrets](), [security]() ### AI overview The article defines YOLO mode as allowing AI coding agents to auto-approve actions without confirmation prompts. It argues that the key risk depends on the execution environment and recommends isolated, disposable sandboxes with scoped access and no real secrets. ### Source excerpt YOLO mode lets an AI agent run without asking permission. Learn what it is, why it's risky, and how to run it safely. ## GPU Concepts and Internals for AI Engineers DevFeed: [GPU Concepts and Internals for AI Engineers]() Original publisher: [Read original article]() Author: Dr. Ashish Bamania Published: 2026-08-27T12:16:32Z Content type: tutorial Language: en Sources: [Into AI]() Topics: [GPU](), [Artificial Intelligence]() Tags: [ai-engineer](), [concepts](), [gpu](), [guide](), [internals]() ### AI overview A practical guide to GPU internals and concepts relevant to AI engineers. ### Source excerpt A simple and practical guide to GPU internals that AI engineers actually need. ## animation-trigger DevFeed: [animation-trigger]() Original publisher: [Read original article]() Author: Saleh Mubashar Published: 2026-08-26T15:38:41Z Content type: article Language: en Sources: [CSS-Tricks]() Topics: [CSS](), [css animation](), [scroll-triggered animations](), [Playback](), [Document Object Model (DOM)](), [API](), [JavaScript]() Tags: [animation](), [api](), [concepts](), [css](), [css-animation](), [javascript](), [playback](), [scroll-triggered-animations]() ### AI overview An overview of the CSS animation-trigger property, which starts, pauses, reverses, or resets CSS animations in response to named timeline- or event-based triggers. The article explains its syntax, trigger scope, animation actions, and distinction from scroll-driven animations. ### Source excerpt The CSS animation-trigger property allows you to delay the start of a CSS animation until a specific trigger occurs. animation-trigger originally handwritten and published with love on CSS-Tricks. You should really get the newsletter as well. ## The platform engineering certification path: From Practitioner to Architect DevFeed: [The platform engineering certification path: From Practitioner to Architect]() Original publisher: [Read original article]() Author: Karolina Semiuk Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [internal developer platform](), [DevOps]() Tags: [and-best-practices](), [concepts](), [engineering](), [platform-engineering](), [practitioner](), [validation]() ### AI overview The article presents a vendor-neutral platform engineering certification path progressing from foundational concepts toward architect-level expertise. It explains that senior engineers and platform teams seek validation, shared language, and best practices, and distinguishes platform engineering competencies from tool-specific DevOps training. ### Source excerpt Explore the platform engineering certification path, from foundational concepts to architect-level expertise, designed for senior engineers and entire teams. ## Content Delivery Network (CDN) - A Deep Dive DevFeed: [Content Delivery Network (CDN) - A Deep Dive]() Original publisher: [Read original article]() Author: Neo Kim Published: 2026-07-02T20:18:06Z Content type: tutorial Language: en Sources: [System Design Newsletter]() Topics: [Network]() Tags: [concepts](), [deep-dive](), [introduction](), [network]() ### AI overview An introduction to content delivery networks and their core concepts. ### Source excerpt #159: A clear introduction to CDNs and their core concepts ## Kotlin Multiplatform in Production: Two Real-World Use Cases from Booking.com DevFeed: [Kotlin Multiplatform in Production: Two Real-World Use Cases from Booking.com]() Original publisher: [Read original article]() Author: Diego Gómez Olvera Published: 2026-06-05T15:09:18Z Content type: article Language: en Sources: [Booking.com Development - Medium]() Topics: [Kotlin Multiplatform](), [compose-multiplatform](), [experiments](), [A/B Testing](), [Android](), [iOS](), [Design system](), [Mobile](), [Development]() Tags: [a-b-testing](), [android](), [booking](), [bookingcom](), [compose](), [compose-multiplatform](), [concepts](), [consistency](), [data](), [development](), [engineering](), [experiment](), [experimentation](), [experiments](), [ios](), [java](), [jetpack-compose](), [kotlin](), [kotlin-multiplatform](), [mobile](), [multiplatform](), [objective-c]() ### AI overview This article describes two Booking.com engineering use cases for Kotlin Multiplatform and Compose Multiplatform: a shared experimentation library for consistent experiment assignments across Android and iOS, and hosting an Android design system in a web browser. ### Source excerpt Introduction For the majority of Booking.com travelers, mobile is the primary channel for researching, planning, and booking trips. Recent data shows that over 80% of travelers rely on a mobile app during the research phase, with more than half of all bookings occurring on mobile devices. Consequently, the Android and iOS platforms are critical to the company's product strategy; engineering choices made here have significant repercussions for the entire organisation. To maintain agility at this scale, two elements must function in unison: Strict decision validation: At any time, Booking.com manages over 1,000 simultaneous experiments across its product suite, with hundreds active on mobile. Every minor adjustment undergoes A/B testing via our proprietary experimentation library before reaching the user. A unified design system ensures product consistency and makes design goals transparent to all contributors, not just maintenance engineers. This article examines two specific engineering challenges solved using Kotlin Multiplatform (KMP) and Compose Multiplatform (CMP): Developing a shared experimentation library to ensure uniform experiment assignments across Android and iOS. Using Compose Multiplatform to host our Android design system in a web browser, bridging the gap between design concepts and implementation. While both cases use the same underlying technology, each provides unique insights into multiplatform development. Use case 1: shared experimentation library on Android and iOSThe problem with two implementations Historically, our internal experimentation library, responsible for managing experiment assignments, evaluations, and tracking on mobile, was maintained as two distinct codebases: a mix of Java and Kotlin for Android and Objective-C for iOS. While intended to be identical, managing two languages with fluctuating team resources inevitably led to logic drift. Discrepancies in event-tracking and experiment-fetching behaviours emerged, though they wer ## A Problem Framing Kernel DevFeed: [A Problem Framing Kernel]() Original publisher: [Read original article]() Author: Morteza Pourmohamadi Published: 2026-06-04T02:51:27Z Content type: opinion Language: en Sources: [UX Magazine]() Topics: [User experience (UX)](), [Artificial Intelligence]() Tags: [concepts](), [design-thinking](), [requirements](), [space](), [ux]() ### AI overview This commentary examines the essential structure of problem framing in design. It argues that effective framing begins by collecting relevant concepts, needs, requirements, stakeholders, constraints, assumptions, and unknowns, then connecting those elements to generate insight; it identifies the kernel as "collect, connect, commit." ### Source excerpt What you need before you have a problem worth solving A few weeks ago, I caught up with my good friend Lucas Mara, a thoughtful design leader. We were deep in a conversation about the value of design in the age of AI when he mentioned Richard Rumelt's classic, Good Strategy Bad Strategy. It had The post A Problem Framing Kernel appeared first on UX Magazine. ## 20 Networking Concepts Explained in 15 Minutes DevFeed: [20 Networking Concepts Explained in 15 Minutes]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-06-02T05:28:43Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [networking](), [Networks](), [domain](), [Internet](), [browser](), [HTTP]() Tags: [browser](), [concepts](), [dns](), [domain](), [http](), [https](), [ipv4](), [ipv6](), [mac-address](), [network](), [networking](), [postgresql](), [recursive-resolver](), [redis](), [ssh](), [wi-fi]() ### AI overview A tutorial introducing core networking concepts, including IP addressing, DNS resolution, ports, MAC addresses, and ARP, with examples involving browsers, routers, servers, SSH, HTTP, PostgreSQL, and Redis. ### Source excerpt Networking can feel overwhelming, but a small set of concepts carries most of the weight in interviews and real-world systems. ## Neural Networks Explained In Plain English DevFeed: [Neural Networks Explained In Plain English]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-04-21T04:01:25Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Neural Network](), [AI Engineering](), [Machine learning]() Tags: [ai-engineering](), [applications](), [concepts](), [function](), [mlp](), [neural-networks](), [neuron](), [understand]() ### AI overview A plain-English introduction to neural networks. It explains neurons or perceptrons, activation functions, weights and biases, and how stacking neurons into dense layers creates a multilayer perceptron (MLP) architecture used in AI systems. ### Source excerpt All popular AI systems that you see today are made up of basic computing units called Neurons or Perceptrons. These connect to form a network called a Neural network that performs various complex computations. ## Object Oriented Programming - The Key Terms DevFeed: [Object Oriented Programming - The Key Terms]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-03-24T08:38:43Z Content type: article Language: en Sources: [System Design Codex]() Topics: [Object-oriented programming (OOP)](), [Programming](), [Polymorphism](), [Inheritance](), [implementation](), [interface]() Tags: [abstraction](), [concepts](), [inheritance](), [maintainability](), [object-oriented](), [polymorphism](), [programming](), [security]() ### AI overview This tutorial introduces object-oriented programming through four principles: abstraction, encapsulation, inheritance, and polymorphism. It explains how abstraction hides implementation details, encapsulation controls access to data and methods, and inheritance supports reuse and hierarchical relationships. The supplied text begins its discussion of polymorphism but is truncated. ### Source excerpt The essential concepts ## New ways to learn math and science in ChatGPT DevFeed: [New ways to learn math and science in ChatGPT]() Original publisher: [Read original article]() Published: 2026-03-10T10:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [ChatGPT](), [math](), [Artificial Intelligence](), [real-time](), [Graphs]() Tags: [ai](), [chatgpt](), [concepts](), [explore](), [graphs](), [learning](), [math](), [product](), [real-time](), [science]() ### AI overview ChatGPT introduces interactive visual explanations for more than 70 core math and science concepts. Learners can adjust variables and manipulate formulas to see how changes affect graphs and outcomes in real time, making abstract ideas more tangible. ### Source excerpt ChatGPT introduces interactive visual explanations for math and science, helping students explore formulas, variables, and concepts in real time. ## 20 AI Concepts Explained in 20 Minutes DevFeed: [20 AI Concepts Explained in 20 Minutes]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-02-26T13:22:58Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Artificial Intelligence](), [Learning](), [Large Language Model](), [Neural Network]() Tags: [ai](), [concepts](), [language-models](), [learning](), [neural-network]() ### AI overview A beginner-friendly tutorial introducing foundational AI concepts, including neural networks, large language models, and transfer learning, with simplified explanations and examples. ### Source excerpt Learning AI can feel overwhelming. ## Getting started with ClickHouse? 13 mistakes and how to avoid them DevFeed: [Getting started with ClickHouse? 13 mistakes and how to avoid them]() Original publisher: [Read original article]() Author: Dale McDiarmid; Tom Schreiber; Geoff Genz Published: 2026-02-20T00:00:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [data](), [Cloud](), [Software]() Tags: [clickhouse](), [cloud](), [concepts](), [data](), [getting-started](), [how-to](), [logs](), [performance](), [post](), [scale](), [software](), [storage]() ### AI overview This getting-started guide examines 13 common mistakes made by new ClickHouse users, explaining why they occur and how to avoid them. It begins with excessive data parts, covering their impact on merges, storage, query performance, startup times, and replicated configurations. ### Source excerpt In this post, we highlight the most common 13 mistakes we see our new users encounter, why they occur and the correct approach. ## Stream of Consciousness Driven Development DevFeed: [Stream of Consciousness Driven Development]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2026-02-18T16:33:08Z Content type: opinion Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [Development](), [Specifications](), [Markdown]() Tags: [concepts](), [development](), [experience](), [markdown](), [pairing](), [specifications]() ### AI overview The author describes a pairing technique for conceptually complex specification work: write the problem, discussion, rejected approaches, proposed solution, and rationale in a Markdown file before changing the specification. This helps partners understand the reasoning and agree on an approach, though the author reports having tried it only once. ### Source excerpt This is something I just tried out last week but it seems to have enough potential to be worth showing unpolished. I was pairing with a client on writing a spec. I saw a problem with the spec, a convoluted way of fixing the spec. Instead of trying to verbally explain it, I started by creating a new markdown file: NameOfProblem.md Then I started typing. First the problem summary, then a detailed description, then the solution and why it worked. When my partner asked questions, I incorporated his question and our discussion of it into the flow. If we hit a dead end with the solution, we marked it out as a dead end. Eventually the file looked something like this: Current state of spec Problems caused by this Elaboration of problems What we tried that didn't work Proposed Solution Theory behind proposed solution How the solution works Expected changes Other problems this helps solve Problems this does *not* help with Only once this was done, my partner fully understood the chain of thought, and we agreed it represented the right approach, did we start making changes to the spec. How is this better than just making the change? The change was conceptually complex. A rough analogy: imagine pairing with a beginner who wrote an insertion sort, and you want to replace it with quicksort. You need to explain why the insertion sort is too slow, why the quicksort isn't slow, and how quicksort actually correctly sorts a list. This could involve tangents into computational complexity, big-o notation, recursion, etc. These are all concepts you have internalized, so the change is simple to you, but the solution uses concepts the beginner does not know. So it's conceptually complex to them. I wasn't pairing with a beginning programmer or even a beginning specifier. This was a client who could confidently write complex specs on their own. But they don't work on specifications full time like I do. Any time there's a relative gap in experience in a pair, there's solutions that are concep ## 12 OOP Concepts EVERY Developer Should Know DevFeed: [12 OOP Concepts EVERY Developer Should Know]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-02-12T04:27:26Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Object-oriented programming (OOP)](), [Programming](), [Code](), [interfaces](), [Polymorphism](), [App]() Tags: [class](), [classes](), [code](), [concepts](), [developer](), [interface](), [interfaces](), [object-oriented](), [oop](), [practical](), [programming](), [real-world]() ### AI overview An introductory tutorial on object-oriented programming explains how classes, objects, and interfaces organize state and behavior. It uses real-world examples such as users, orders, payments, and payment gateways, and notes that these concepts are relevant to low-level design interviews. ### Source excerpt Key Object-Oriented Programming Concepts ## Scheduling In Go : Part III - Concurrency DevFeed: [Scheduling In Go : Part III - Concurrency]() Original publisher: [Read original article]() Published: 2025-05-12T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Concurrency](), [Go Language](), [benchmarking](), [IO](), [Sorting]() Tags: [ardan-labs](), [benchmarks](), [blog](), [concepts](), [concurrency](), [go](), [go-programming](), [golang](), [io](), [parallelism](), [performance](), [programming](), [sorting](), [technical]() ### AI overview This third post in a series about the Go scheduler explains concurrency as out-of-order execution and distinguishes it from parallelism. It discusses how CPU-bound and I/O-bound workloads affect the decision to use concurrency, using practical examples and benchmarks to show that parallelism can improve CPU-bound performance while concurrency alone can benefit I/O-bound work. ### Source excerpt Although originally written in 2018, the following concepts remain essential for developers working with concurrency. This blogpost focuses on concurrency, distinguishing it from parallelism by defining it as "out of order" execution. It emphasizes the importance of understanding workload types--CPU bound (e.g., summing, sorting) and IO bound (e.g., file reading)--to assess when concurrency is appropriate. Through practical examples and benchmarks, it shows that parallelism boosts performance for CPU bound tasks, while concurrency alone benefits IO bound workloads. The post underscores that identifying workload type is key to applying concurrency effectively without added complexity. ## View the SQL basecamps before Trino Summit DevFeed: [View the SQL basecamps before Trino Summit]() Original publisher: [Read original article]() Author: Manfred Moser Published: 2024-11-21T00:00:00Z Content type: release Language: en Sources: [Trino Blog]() Topics: [SQL](), [data]() Tags: [concepts](), [data](), [sql](), [summit](), [training]() ### AI overview Two SQL basecamp training sessions recorded before Trino Summit are now available. The sessions cover core concepts of a Trino-powered lakehouse, data ingestion and maintenance, lakehouse usage, structural data types, and views. ### Source excerpt Trino Summit is inching closer fast, and we are busy with all the preparation. Nevertheless, we thought we bring you some more SQL and Trino-related training. The two live classes from our SQL basecamps before Trino Summit are now available for you all to enjoy, just in case you missed it. ## Assorted Git things DevFeed: [Assorted Git things]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2024-10-01T08:27:00Z Content type: article Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Git](), [Submodules](), [ide](), [passwords]() Tags: [concepts](), [git](), [ide](), [password](), [submodules](), [til]() ### AI overview A running collection of Git tips covering editor configuration, staging behavior, removing submodules, credential-helper interaction, and maintaining a fork. ### Source excerpt A running log of Git concepts I've learned since I started journaling ## Abstraction design: Introduction DevFeed: [Abstraction design: Introduction]() Original publisher: [Read original article]() Published: 2024-02-05T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [abstraction](), [Programming](), [Object-oriented programming (OOP)](), [interfaces](), [Functional programming]() Tags: [abstraction](), [concepts](), [core](), [function](), [interfaces](), [object-oriented](), [programming](), [workshop-learning-programming]() ### AI overview This introduction explains abstraction as a form of simplification that hides complexity by deciding what to expose and what to conceal. It discusses abstractions in object-oriented and functional programming, including interfaces, classes, functions, and higher-level operations, with examples involving Java and Kotlin. ### Source excerpt What is abstraction in programming and why is it so important. ## Object-Oriented Programming in iOS DevFeed: [Object-Oriented Programming in iOS]() Original publisher: [Read original article]() Published: 2023-10-17T00:00:00Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Object-oriented programming (OOP)](), [iOS](), [Programming](), [Application Development](), [Software Engineering]() Tags: [application-development](), [code](), [concepts](), [course](), [development](), [engineering](), [ios](), [learning](), [mobile](), [oop](), [programming](), [skills](), [software-engineering](), [techniques]() ### AI overview This learning path teaches Object-Oriented Programming in iOS development, including foundational and advanced OOP concepts and their integration with Protocol-Oriented Programming. It aims to help learners design and implement reusable, maintainable software for mobile application development. ### Source excerpt The Object-Oriented Programming (OOP) learning path offers a comprehensive exploration of software development principles and techniques. Covering three modules, learners will delve into foundational OOP concepts, advanced techniques, and their integration with Protocol-Oriented Programming (POP). By mastering both OOP and POP paradigms, participants will emerge ready to craft robust, adaptable software solutions that excel in the dynamic world of modern software engineering. ## Ultimate Go: Advanced Engineering Episode 9 DevFeed: [Ultimate Go: Advanced Engineering Episode 9]() Original publisher: [Read original article]() Published: 2022-12-20T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Go Language](), [Bitcoin](), [Ethereum]() Tags: [bitcoin](), [blockchain](), [blockchain-asset](), [build](), [building](), [code](), [concepts](), [engineering](), [ethereum](), [genesis](), [genesis-json](), [genesis-record](), [go](), [go-blockchain](), [implement](), [introduction](), [project](), [project-layout](), [reuse](), [standard-library]() ### AI overview This video tutorial covers the initial layout of a blockchain project in Go, including creating a genesis record and explaining its role. It also introduces fundamental blockchain verifications. ### Source excerpt Introduction In episode 8, Bill wanted to build a blockchain in Go and began to lay the groundwork for the project. Go is a good choice because its standard library has the necessary network and cryptographical functionality required to build a blockchain. Unlike the previous segment, Bill plans to use this blockchain to manage accounts and balances with hypothetical assets. Bill will reuse concepts from ethereum, bitcoin and the previous segment of the series to implement this blockchain. ## Four of a Kotlin Kind at I code Java 2022 conference DevFeed: [Four of a Kotlin Kind at I code Java 2022 conference]() Original publisher: [Read original article]() Published: 2022-10-14T08:30:41Z Content type: article Language: en Sources: [maiatoday]() Topics: [Kotlin](), [Code](), [Software]() Tags: [code](), [concepts](), [conference](), [declarative](), [functional](), [imperative](), [java](), [kotlin](), [object-oriented](), [pitfalls](), [talk](), [tips](), [traces]() ### AI overview The article introduces a talk about Kotlin's support for imperative, declarative, functional, and object-oriented programming. It highlights tips, guidelines, pitfalls, definitions, software history, and how Kotlin supports these concepts. ### Source excerpt I shared my talk titled Imperative, Declarative, Object oriented, functional: Four of a Kotlin Kind at the I code Java conference. The abstract: Is Kotlin a functional language? Yes, but... Is it object oriented? Yes, but... Looking at four concepts: imperative, declarative, functional and object oriented How does Kotlin make it easy to use either or all at the same time. This talk contains: Some useful Kotlin tips, some guidelines and pitfalls for the four concepts, traces of definitions and software history. After listening to this talk you will understand what these concepts are, what each is good for and how they are supported by the Kotlin language. You can see the talk here [Next page]()