# Diagram Published articles for Diagram. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Bending, Yanking, and Cartesian Squares in Double Categories DevFeed: [Bending, Yanking, and Cartesian Squares in Double Categories]() Original publisher: [Read original article]() Author: Bartosz Milewski Published: 2026-05-19T06:54:15Z Content type: article Language: en Sources: [Bartosz Milewski's Programming Cafe]() Topics: [Category Theory](), [Profunctor Equipment](), [String Diagrams]() Tags: [category-theory](), [diagram](), [double-categories](), [proarrow-equipment](), [profunctor-equipment](), [profunctors](), [string-diagrams]() ### AI overview This article explains how string-diagram manipulations in double categories and proarrow equipment support yanking identities and the spider lemma, then introduces Cartesian squares as a universal construction in category theory. ### Source excerpt Previously: Profunctor Equipment in Haskell. The major advantage of string diagrams is that they provide surprisingly natural language for complex diagram manipulations. The fact that two traditional diagrams are equal can be often described as a permission to bend, yank, or pinch strings in particular ways. They provide visual and often tactile clues to our [...] ## What Happens to an SQL Query? DevFeed: [What Happens to an SQL Query?]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-03-04T03:14:28Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [SQL](), [Databases](), [Parser](), [syntax]() Tags: [database](), [diagram](), [errors](), [execution](), [locks](), [rollback](), [sql](), [syntax]() ### AI overview This tutorial explains how an SQL query moves through a database. It covers transport and access checks, parsing and optimization into an execution plan, execution through the storage engine, and supporting components such as transactions, locks, buffering, and recovery. ### Source excerpt The Journey Through the DB ## Interactive versionable architecture diagrams DevFeed: [Interactive versionable architecture diagrams]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2023-06-09T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Graphs](), [SVG](), [HTML](), [Web Development]() Tags: [architecture](), [blogs](), [diagram](), [git](), [graphviz](), [how-to](), [html](), [svg](), [visualization]() ### AI overview A tutorial on generating interactive, versionable system architecture diagrams with Graphviz, exporting them as SVG, and embedding the SVG directly in HTML so diagram elements can link to the hosting page. ### Source excerpt Tired of building un-versionable, lifeless architecture diagrams? Wouldn't it be great if you could add your diagram to Git, embed it in your documentation, and have clickable elements? ## Five Threat Model Diagrams for Machine Learning DevFeed: [Five Threat Model Diagrams for Machine Learning]() Original publisher: [Read original article]() Author: Adam Published: 2023-04-13T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Machine Learning, Security Attacks](), [Machine Learning & Artificial Intelligence](), [Training AI Models](), [Data Quality](), [data]() Tags: [ai-and-cybersecurity](), [cybersecurity](), [data-quality](), [diagram](), [machine-learning](), [training-data]() ### AI overview This article presents five threat-model diagrams for machine learning systems. The diagrams distinguish threats to and from ML systems, illustrate data flows and responses, and examine how training-data sources and system-design decisions can create risks. The author emphasizes that the diagrams are illustrative rather than complete and notes uncertainty about the model of how Twitter content reached Microsoft's Tay. ### Source excerpt Some diagrams to help clarify machine learning threats ## Threat Modeling Google Cloud (Threat Model Thursday) DevFeed: [Threat Modeling Google Cloud (Threat Model Thursday)]() Original publisher: [Read original article]() Author: Adam Published: 2023-03-01T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Google Cloud Platform (GCP)](), [Security](), [Google](), [Architecture & Design]() Tags: [assets](), [cloud](), [cloud-platform](), [data](), [diagram](), [google](), [google-cloud](), [google-cloud-platform](), [processes](), [security]() ### AI overview The article reviews NCC's threat model for Google Cloud Platform, examining its methodology, diagrams, assets, boundaries, threat actors, attack goals, weaknesses, and potential threats. It offers constructive observations about the model's organization, readability, and use of STRIDE-related categories. ### Source excerpt NCC has released a threat model for Google Cloud Platform. What can it teach us? ## Breaking down Krypton DevFeed: [Breaking down Krypton]() Original publisher: [Read original article]() Author: Stanko Published: 2022-03-01T00:00:00Z Content type: article Language: en Sources: [Stanko Tadić]() Topics: [generative art](), [JavaScript](), [Tooling](), [browser]() Tags: [ascii](), [browser](), [diagram](), [generative-art](), [javascript](), [tooling]() ### AI overview This article breaks down how "Krypton," a generative artwork, was created. It discusses the author's JavaScript, p5.js, and custom tooling, including parameter controls, browser-history-based iteration, and the use of Voronoi diagrams to generate the drawing. ### Source excerpt This post was originally written for our internal technology newsletter at Work & Co. It is a little bit adapted for web, but the content is almost identical. About a year ago I made this plot. It is called "Krypton"Named by a dear friend and ex-colleague, and I'll try to break down how it was made. The wonderful thing about generative art is that code is just a tool. Thing that really matters is the actual artwork. In this specific case, code is straightforward and relatively simple. But it produces drawings that, in my opinion, look visually pleasing and have a nice sense of depth to them. Tooling # For all of my generative work, I use plain JavaScript, p5.js and a couple of custom-made tools. These tools are often crude, but they do exactly what I want so I don't mind. With each new project I keep adding more features and polishing them. At some point these tools may reach the point where they are presentable. If that happens I'll gladly share them with the world and open source everything. This is how the interface looks. I have an easy way to add controls for image parameters. These controls allow me to tweak drawings with a short feedback loop. Each time a parameter is changed, the image is redrawn and the parameter is reflected in the URL. This allows me to go through iterations using the browser history. To make navigation through the history easier, for each unique combination of parameters, I generate a random color and ASCII face. That is why my browser history looks like this :) Voronoi diagram # I use Voronoi diagrams a lot in my drawings. So much, that I'm sometimes trying to avoid them, to make sure I'm not limiting myself to a single algorithm. Voronoi diagram takes a collection of points, and then partitions a plane into polygons, where each polygon's edge is right in the middle of two points. It sounds like a lot, but if you study this image, it should become clearer. For a more detailed explanation you can check out the article on Wikipedia. Gener ## AWS IAM in layman's terms DevFeed: [AWS IAM in layman's terms]() Original publisher: [Read original article]() Author: info@goteleport.com (Shuo Yang) Published: 2021-06-16T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [AWS Identity and Access Management (IAM)](), [IAM](), [Access Control](), [Authorization](), [Development](), [Security](), [Infrastructure as code]() Tags: [access-control](), [aws-iam](), [development](), [diagram](), [figure](), [how-to](), [iam](), [infrastructure-as-code-iac](), [policy](), [security]() ### AI overview This tutorial explains AWS IAM roles, STS, identity pools, and IAM policy mechanisms. It focuses on separating access-control responsibilities between central security or platform teams and individual application development teams, including the interaction between permission boundaries and identity-based policies. ### Source excerpt Learn how to leverage the right AWS IAM policy mechanisms to build responsibility separation between a central platform team and individual development teams. ## Threat Model Thursday: Data Flow Diagrams DevFeed: [Threat Model Thursday: Data Flow Diagrams]() Original publisher: [Read original article]() Author: Adam Published: 2020-04-23T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Security](), [trust](), [Architecture & Design](), [data]() Tags: [academic](), [diagram](), [paper](), [security](), [software-engineering](), [trust]() ### AI overview The article discusses an academic paper on whether data flow diagrams are sufficient for security threat modeling. It reviews the paper's treatment of diagram strengths, weaknesses, effort tradeoffs, and three meanings of a trust boundary, then proposes a fourth meaning: separation of principals by a controlling mechanism. ### Source excerpt This week's threat model Thursday looks at an academic paper, Security Threat Modeling: Are Data Flow Diagrams Enough? by Laurens Sion and colleagues. ## Threat Model Thursdays: Crispin Cowan DevFeed: [Threat Model Thursdays: Crispin Cowan]() Original publisher: [Read original article]() Author: Adam Published: 2018-07-05T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Security](), [Vulnerabilities](), [Architecture & Design]() Tags: [diagram](), [discussion](), [security](), [trust](), [vulnerabilities]() ### AI overview The article reviews Crispin Cowan's threat-modeling approach, focusing on precise definitions of security principals, attack surfaces, trust boundaries, and security boundaries. It also discusses identifying system connections, assessing complexity, prioritizing mitigations, and documenting threat models. ### Source excerpt [no description provided] ## Threat Model Thursday: Synopsys DevFeed: [Threat Model Thursday: Synopsys]() Original publisher: [Read original article]() Author: Adam Published: 2018-03-22T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Development](), [trust](), [Internet]() Tags: [developer](), [development](), [diagram](), [internet](), [series]() ### AI overview This commentary launches a series examining published sample threat models. It reviews Synopsys's threat-model guidance, focusing on scoping, understanding the system and its components, and how consulting-oriented practices may differ from threat modeling integrated into development. ### Source excerpt [no description provided] ## Jonathan Marcil's Threat Modeling Toolkit talk DevFeed: [Jonathan Marcil's Threat Modeling Toolkit talk]() Original publisher: [Read original article]() Author: Adam Published: 2018-01-30T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [Application Security](), [Security](), [Architecture & Design](), [plantuml](), [version-control](), [trust]() Tags: [appsec](), [blog](), [diagram](), [github](), [plantuml](), [requirements](), [security](), [talk](), [trust](), [version-control]() ### AI overview A report on Jonathan Marcil's threat modeling toolkit talk, covering collaborative threat modeling, data flow diagrams, attack trees, controls checklists, and system models. The talk includes an Electrum example in which investigations driven by a system model found a real JSON-RPC vulnerability, and discusses using PlantUML and version control for attack trees. ### Source excerpt [no description provided] ## Data Flow Diagrams 3.0 DevFeed: [Data Flow Diagrams 3.0]() Original publisher: [Read original article]() Author: Adam Published: 2017-11-05T00:00:00Z Content type: tutorial Language: en Sources: [Shostack & Friends Blog]() Topics: [data](), [trust](), [context](), [Processes]() Tags: [context](), [data](), [diagram](), [flow](), [parallel](), [process](), [symbols](), [trust](), [version]() ### AI overview This article defines Data Flow Diagrams 3.0 as a named approach to threat-modeling diagrams. It explains its five symbols, trust boundaries, labeling rules, optional context diagrams, and guidance on color and arrow direction. ### Source excerpt [no description provided] ## pg\_staging's bird view DevFeed: [pg\_staging's bird view]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2009-12-08T11:04:00Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [Emacs](), [Git](), [file]() Tags: [command](), [diagram](), [emacs](), [git](), [repository]() ### AI overview A short post presents a bird's-eye diagram of how pgstaging is operated, created with ditaa and Emacs. The author committed the diagram's text source to a Git repository and used ImageMagick's crop command to remove excess white space without using a mouse. ### Source excerpt One of the most important feedback I got about the presentation of pgstaging were the lack of pictures, something like a bird-view of how you operate it. Well, thanks to ditaa and Emacs picture-mode here it is: Hope you enjoy, it should not be necessary to comment much if I got to the point! Of course I commited the text source file to the Git repository. The only problem I ran into is that ditaa defaults to ouputing a quite big right margin containing only white pixels, and that didn't fit well, visually, in this blog. So I had to resort to ImageMagik crop command in order to avoid any mouse usage in the production of this diagram.