# structure Structure is an aggregate data type whose fields or members hold contained data items, and whose specification defines their number, type, name, and order. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Nail the Narrative DevFeed: [Nail the Narrative]() Original publisher: [Read original article]() Author: Martin Fowler (martin@martinfowler.com) Published: 2026-09-15T15:11:00Z Content type: opinion Language: en Sources: [Martin Fowler]() Topics: [structure](), [Software]() Tags: [design](), [presentation](), [speaking](), [structure](), [writing]() ### AI overview The article argues that presenters should develop a clear narrative before opening slide software. It recommends defining the central idea and audience, shaping a storyline, and creating a lightweight storyboard before designing slides. ### Source excerpt Sumeet Gayathri Moghe finds many folks building presentations get tangled in building slides without a coherent narrative. He advises distilling the big idea, visualizing the audience, and building a structured storyline. more... ## History of SpaceX: The Patient-Private Capital-Formation Leg and the Manufacture of Patience DevFeed: [History of SpaceX: The Patient-Private Capital-Formation Leg and the Manufacture of Patience]() Original publisher: [Read original article]() Author: Brendan Sechter Published: 2026-08-03T09:00:00Z Content type: opinion Language: en Sources: [Brendan A R Sechter's Development Blog]() Topics: [structure](), [Google](), [Development]() Tags: [aerospace](), [article](), [business](), [company](), [google](), [history]() ### AI overview This analytical article examines how private-capital instruments financed SpaceX's development despite venture-fund time constraints. It focuses on investor entries, funding rounds, tender offers that provided liquidity without an exit, investor time horizons, and dilution management, while comparing the structure with Iridium and OneWeb. ### Source excerpt This article is the tenth in the History of SpaceX series and the second of three treating the capital-formation legs that the series opener introduced. The patient-private leg concerns the private capital that financed the development the government leg did not, on terms that surrendered equity and did not surrender the mission. The article's organizing claim is that patience is not a temperament that investors possess but a structural property that instruments manufacture, and that the instruments are identifiable, describable, and largely absent from the commentary that attributes the outcome to investor conviction. The binding constraint on private capital in the venture form is the fund-life clock, which obliges a fund to return capital to its limited partners on a schedule that has no relation to the development horizon of any portfolio company. The article walks the fund-life constraint and the duration mismatch it creates, the August 2008 Founders Fund entry at the moment of maximum distress, the 2009 Draper Fisher Jurvetson entry, the January 2015 Google and Fidelity round motivated by a business line that did not yet exist, the round and valuation sequence across the 2015 through drafting-date period, the semi-annual tender-offer mechanism that gives liquidity without exit and that the article treats as the decisive structural innovation, the composition of the investor base and the horizon heterogeneity across it, and the dilution management that preserved the control configuration the Governance article A287 analyzes. The article contrasts the configuration against the Iridium capital structure, in which a debt-financed constellation faced a fixed obligation schedule that no development delay could accommodate, and against the OneWeb funding withdrawal, in which a nominally patient investor proved otherwise. The article treats the contemporary defense-technology venture wave and the Anduril and Palantir comparisons as the downstream consequence. The arti ## TBM 434: How Maps Can Hide Problems DevFeed: [TBM 434: How Maps Can Hide Problems]() Original publisher: [Read original article]() Author: John Cutler Published: 2026-08-01T09:13:07Z Content type: opinion Language: en Sources: [The Beautiful Mess]() Topics: [context](), [structure]() Tags: [design](), [mapping](), [maps](), [organizations](), [ownership](), [problems](), [product](), [reporting](), [silos](), [structure](), [technology]() ### AI overview The article argues that organizational maps can conceal incoherence when strategy, structure, technology, incentives, goals, ownership, teams, and funding do not align. It contrasts coherent organizations, where context transfers across map layers, with incoherent organizations, where people must repeatedly reorient and translate. ### Source excerpt If what you are mapping is incoherent, don't fall in love with the map (or your personal ability to navigate with it). ## Name that Ware, July 2026 DevFeed: [Name that Ware, July 2026]() Original publisher: [Read original article]() Author: bunnie Published: 2026-07-30T14:52:35Z Content type: opinion Language: en Sources: [bunnie's blog]() Topics: [SOC](), [structure]() Tags: [2026](), [image](), [name-that-ware](), [soc](), [structure]() ### AI overview A July 2026 "Name that Ware" puzzle asks readers to identify a conserved design pattern in the lower-left area of a die-shot excerpt from an SoC and explain why the structures are organized that way. The document does not provide the answer. ### Source excerpt The Ware for July 2026 is shown below. I've got silicon on the brain, so I'm going to give a die shot another go at name that ware. Hopefully this one is a bit easier than the last one. This excerpt is a design pattern I look for and find on almost every SoC. It's [...] ## The PM's Guide to Governance with Eric Ries, author of The Lean Startup DevFeed: [The PM's Guide to Governance with Eric Ries, author of The Lean Startup]() Original publisher: [Read original article]() Author: Aakash Gupta Published: 2026-07-20T22:11:52Z Content type: article Language: en Sources: [Product Growth]() Topics: [structure](), [trust](), [anthropic](), [Claude](), [OpenAI]() Tags: [anthropic](), [case-study](), [claude](), [governance](), [guide](), [openai]() ### AI overview A discussion with Eric Ries examines governance and organizational structures intended to help companies remain resilient and avoid governance failures. The article also covers Ries's use of AI tools, including Claude, in writing Incorruptible. ### Source excerpt The Lean Startup creator on why Anthropic holds and OpenAI cracked, and how to structure yours ## Tannakian reconstruction DevFeed: [Tannakian reconstruction]() Original publisher: [Read original article]() Author: Bartosz Milewski Published: 2026-07-14T10:51:53Z Content type: tutorial Language: en Sources: [Bartosz Milewski's Programming Cafe]() Topics: [structure]() Tags: [category-theory](), [fiber-functor](), [tannakian-reconstruction]() ### AI overview An explanatory article introduces Tannakian reconstruction through an analogy of superimposed photographs, then describes how functors, fiber functors, natural transformations, and ends can recover source-category morphisms. ### Source excerpt Two friends, Alice and Bob, live in the same city, but on the opposite sides of a wide river. Every night, Bob looks at the lights on the other side and tries to guess, which one belongs to Alice. They come up with a clever arrangement: Alice will turn on her lights for 10 minutes [...] ## Too big to draw, but yet drawable DevFeed: [Too big to draw, but yet drawable]() Original publisher: [Read original article]() Author: Yehonathan Sharvit Published: 2026-07-06T09:00:00Z Content type: article Language: en Sources: [Klipse]() Topics: [ordering](), [structure]() Tags: [aboulafia](), [caustics](), [generative](), [math](), [permutation](), [permutations](), [random](), [ranking](), [recursion](), [visualization]() ### AI overview The third article in a series explains how Aboulafia's tserouf orders all permutations of a word and visualizes them by placing the permutations around a circle and connecting each word to its reversal. Because the full permutation space becomes too large to draw, the article samples chords and shows that they form recurring caustic curves visible at multiple scales. ### Source excerpt Aboulafia's Tserouf - Part 3 of 4 <- Previous: An elegant formulation, inspired by Bill Gates - Next: A wheel, the same forwards and backwards -> ## A 13th-Century Enumeration Algorithm, Ignored for 700 Years DevFeed: [A 13th-Century Enumeration Algorithm, Ignored for 700 Years]() Original publisher: [Read original article]() Author: Yehonathan Sharvit Published: 2026-07-06T07:00:00Z Content type: article Language: en Sources: [Klipse]() Topics: [Algorithm](), [ordering](), [structure]() Tags: [aboulafia](), [algorithm](), [kabbalah](), [math](), [order](), [ordering](), [permutations]() ### AI overview The article examines a systematic method for enumerating permutations described by the 13th-century Kabbalist Abraham Aboulafia in his account of Tserouf. It explains rules for ordering three-letter permutations and a rotation-based method for extending the ordering to longer words. ### Source excerpt Aboulafia's Tserouf - Part 1 of 4 Next: An elegant formulation, inspired by Bill Gates -> ## Why Technical Program Managers Matter as AI Reshapes Engineering Teams DevFeed: [Why Technical Program Managers Matter as AI Reshapes Engineering Teams]() Original publisher: [Read original article]() Author: Dean Hume Published: 2026-06-29T10:27:25Z Content type: opinion Language: en Sources: [Dean Hume]() Topics: [structure](), [Artificial Intelligence](), [Tech Lead](), [Software]() Tags: [ai](), [article](), [engineering-management](), [game-development](), [software](), [teams](), [tech-lead](), [technical-leadership](), [technical-program-manager]() ### AI overview The article argues that as AI reshapes engineering organizations and teams become smaller, Technical Program Managers can coordinate dependencies, cross-functional delivery risks, and roadmap-to-capacity alignment across multiple teams. ### Source excerpt As AI shrinks engineering teams and the EM role splits in two, the Technical Program Manager could be the most overlooked answer hiding in plain sight. ## YAGNI Is About the Cost of Speculative Structure, Not Code DevFeed: [YAGNI Is About the Cost of Speculative Structure, Not Code]() Original publisher: [Read original article]() Author: Kent Beck Published: 2026-06-25T12:59:56Z Content type: opinion Language: en Sources: [Software Design: Tidy First?]() Topics: [structure](), [Code](), [Optimization]() Tags: [code](), [structure]() ### AI overview The article argues that YAGNI is not primarily about saving the effort or expense of writing code. It is about avoiding speculative structure built before the required feature is understood, because premature structure limits future options and may later need to be worked around or removed. Waiting is presented as a timing decision rather than laziness or a rejection of design. ### Source excerpt If you think YAGNI is about saving effort, cheap generation should retire it. It doesn't. Here's why. ## Same-Day Model Integration: ESMC + ESMFold2 in Sheaf v0.11 DevFeed: [Same-Day Model Integration: ESMC + ESMFold2 in Sheaf v0.11]() Original publisher: [Read original article]() Published: 2026-05-27T00:00:00Z Content type: article Language: en Sources: [Alex Korbonits]() Topics: [Large Language Model](), [structure](), [Pydantic](), [backends](), [unit tests](), [Serverless]() Tags: [backend](), [claude-code](), [code](), [language](), [model](), [pypi](), [release](), [serverless](), [structure](), [tests]() ### AI overview The article explains how Sheaf v0.11 integrated ESMC and ESMFold2 on the same day they were released. It attributes the rapid integration to existing typed serving contracts and infrastructure, while describing verification, testing, H100 smoke testing, release work, and documentation. ### Source excerpt Chan Zuckerberg Biohub released a new protein language model and structure predictor this morning. Sheaf v0.11 shipped with both, same day. The story is less about hustle and more about what a typed serving contract buys you when a new model lands. ## Stop Writing RFCs Like Mystery Novels: Why the Best Design Docs Start with the Conclusion DevFeed: [Stop Writing RFCs Like Mystery Novels: Why the Best Design Docs Start with the Conclusion]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-05-17T00:00:00Z Content type: opinion Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Documentation](), [Requirements](), [Latency](), [Network](), [Back end](), [structure]() Tags: [architecture](), [backend](), [communication](), [conclusion](), [context](), [database](), [docs](), [documentation](), [how-to](), [latency](), [network](), [rfc](), [systems-design](), [writing]() ### AI overview The article argues that RFCs and architecture documents should begin with the conclusion and proposed architecture. It says burying key design decisions in background material overloads reviewers' working memory, encourages superficial approval, and can hide important network and latency risks. ### Source excerpt Reviewers pipeline like CPUs. Hide the proposed architecture on page seven and they load context with no index to file it under, saturate working memory, then skim and rubber-stamp. Invert the structure: conclusion, architecture diagram, hardware and latency impact, then background and rejected alternatives last, so reviewers spend their attention interrogating your network boundaries instead of solving a literary puzzle. ## Organization Groups: Structure Your Organizations with Hierarchical Group Management DevFeed: [Organization Groups: Structure Your Organizations with Hierarchical Group Management]() Original publisher: [Read original article]() Author: Vlasta Ramik Published: 2026-04-29T00:00:00Z Content type: tutorial Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [structure](), [Authentication](), [OpenID connect (OIDC)](), [saml]() Tags: [authentication](), [b2b](), [idm](), [kerberos](), [keycloak](), [ldap](), [oidc](), [openid-connect](), [saml](), [sso](), [structure]() ### AI overview Keycloak 26.6.0 introduces Organization Groups, enabling isolated hierarchical groups within each organization. The article explains how to create and reorganize group hierarchies, assign users through identity-provider mappers, and include organization group memberships in OIDC tokens and SAML assertions. ### Source excerpt Introduced in Keycloak 26.6.0, Organization Groups bring hierarchical group management to the Organizations feature. While Organizations already let you model Business-to-Business (B2B) relationships where external companies, partners, or departments each manage their own users, Organization Groups take this further by letting you organize members within each organization into logical teams, departments, or any structure that fits your needs. Why Organization Groups? Before Organization Groups, structuring members within an organization required workarounds using realm-level groups, which are shared across the entire realm. This creates problems in multi-tenant scenarios: if Organization A and Organization B both need an "Engineering" group, they'd collide at the realm level. Organization Groups solve this by giving each organization its own isolated group hierarchy. Organization A's /Engineering/Backend and Organization B's /Engineering/Backend are completely separate groups with their own members, attributes, and identifiers. No naming conflicts, no cross-organization leakage. Creating a Group Hierarchy Groups can be nested to mirror real-world organizational structures: /Engineering /Engineering/Backend /Engineering/Frontend /Sales /Sales/APAC /Sales/EMEA /Sales/LATAM /Sales/NA Creating groups is straightforward: navigate to your organization, click the Groups tab, and click Create group. To build hierarchies, select a parent group before creating a child group, or use Move to to reorganize existing groups. Automatic Group Assignment via Identity Providers One of the most powerful capabilities is automatic group assignment during federated authentication. When an identity provider is linked to an organization, two mapper types are available: Hardcoded Group assigns every user authenticating through the IdP to a specific organization group. Useful for scenarios like "everyone from this corporate IdP goes into the Engineering team." Advanced Claim to Group maps use ## Agent Memory Patterns DevFeed: [Agent Memory Patterns]() Original publisher: [Read original article]() Published: 2026-04-27T00:00:00Z Content type: tutorial Language: en Sources: [Tim Kellogg]() Topics: [systems](), [file](), [data](), [structure](), [Caching]() Tags: [agents](), [blocks](), [files](), [guide](), [how-to](), [memory](), [patterns](), [skills]() ### AI overview This guide explains three common forms of mutable memory for agents: files, memory blocks, and skills. It describes how files can store data and knowledge, while memory blocks provide learnable prompt content for behavior, preferences, identity, and character. ### Source excerpt A short HOW TO guide for agent memory systems. Especially the difference between blocks, files and skills. ## I Built the Knowledge Graph of Machine Learning DevFeed: [I Built the Knowledge Graph of Machine Learning]() Original publisher: [Read original article]() Author: Tivadar Danka Published: 2026-04-19T07:46:57Z Content type: article Language: en Sources: [The Palindrome]() Topics: [Machine Learning & Artificial Intelligence](), [structure]() Tags: [knowledge-graph](), [machine-learning]() ### AI overview The article explores the structure of machine learning and presents a knowledge graph of the field. ### Source excerpt Exploring the structure of machine learning ## Anatomy of a Room DevFeed: [Anatomy of a Room]() Original publisher: [Read original article]() Published: 2026-03-23T00:00:00Z Content type: article Language: en Sources: [Robin Ward]() Topics: [3D](), [blender](), [layout](), [structure]() Tags: [3d](), [blender](), [game](), [layout](), [structure]() ### AI overview The article explains how the team designed rooms for The Incident at Galley House, an adaptation of the text-based game Type Help. It covers creating a believable floor plan, modeling the house and rooms in Blender, preparing art briefs with references and game-specific requirements, and producing illustrations from 3D scenes. ### Source excerpt Background Our next game, The Incident at Galley House, is an adaptation of a text-based game called Type Help. It takes place at Galley House, a dwelling in the English countryside, during a dinner party where things go sideways. Galley House is divided into many rooms, and the core gameplay involves following characters from room to room, listening in on their conversations, learning their motives, and eventually piecing together a mysterious incident. ## Write-Then-Meet Framework for Technical Reviews DevFeed: [Write-Then-Meet Framework for Technical Reviews]() Original publisher: [Read original article]() Author: Sidwyn Koh Published: 2026-01-10T14:16:44Z Content type: tutorial Language: en Sources: [Path to Staff]() Topics: [meetings](), [structure]() Tags: [communication](), [how-to](), [meetings](), [structure](), [technical]() ### AI overview A practical framework for technical reviews: write a focused document, collect reviewer alignment before the meeting, send the document as a pre-read, and then meet to reach a decision. ### Source excerpt The write-then-meet framework for running great technical reviews ## YARV's Internal Stack and Your Ruby Stack DevFeed: [YARV's Internal Stack and Your Ruby Stack]() Original publisher: [Read original article]() Author: Pat Shaughnessy Published: 2025-11-10T00:00:00Z Content type: article Language: en Sources: [Pat Shaughnessy]() Topics: [Ruby](), [Code](), [structure]() Tags: [code](), [ruby](), [structure](), [updating-ruby-under-a-microscope]() ### AI overview This article explains how YARV, Ruby's stack-oriented virtual machine, uses an internal stack and a second stack of rb_control_frame_t structures to track Ruby program call frames. ### Source excerpt I've started working on a new edition of Ruby Under a Microscope that covers Ruby 3.x. I'm working on this in my spare time, so it will take a while. Leave a comment or drop me a line and I'll email you when it's finished. The content of Chap ## Designing a hierarchical Authorisation system DevFeed: [Designing a hierarchical Authorisation system]() Original publisher: [Read original article]() Author: Authorisation Published: 2025-09-20T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Actor](), [object](), [structure](), [service](), [properties]() Tags: [actor](), [apis](), [billing](), [finance](), [object](), [recursion](), [service](), [structure]() ### AI overview This article explains how to design a hierarchical authorization system for Goiter. It contrasts a flat mapping of users, objects, and actions with a hierarchical model in which groups can have multiple parents and inherit rules. The article notes that recursive parent lookup can reduce rule bloat, while assuming a maximum recursion depth of 10. ### Source excerpt . [Designing a Hierarchical Authorisation System](designing-a-hierarchical-authorisation-system-cover... ## Rethinking Leadership in B2B SaaS: Lessons from Self-Managing Organizations DevFeed: [Rethinking Leadership in B2B SaaS: Lessons from Self-Managing Organizations]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2025-06-27T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Software as a service](), [scaling](), [structure](), [trust]() Tags: [b2b](), [collaboration](), [culture-leadership-decision-making-delegation-organizational-design](), [founders](), [leadership](), [saas](), [scaling](), [self-organizing](), [teams](), [trust]() ### AI overview An opinion article applies lessons from self-managing organizations such as Buurtzorg and Viisi to B2B SaaS teams. It argues that trust can be supported by clear roles, peer accountability, and shared expectations, and that role-based structures may help teams experiment and operate with less founder involvement. ### Source excerpt Rethinking Leadership in B2B SaaS: Lessons from Self-Managing Organizations Two months ago, I joined the Corporate Rebels Masterclass - a hands-on exploration of how pioneering companies like Buurtzorg, Haier, Viisi, and others approach leadership, structure, and collaboration. These aren't companies tinkering at the edges. They've built entire systems that challenge our default assumptions about how work should be organized. ## How Cursor Indexes Codebases Fast DevFeed: [How Cursor Indexes Codebases Fast]() Original publisher: [Read original article]() Author: Engineer's Codex Published: 2025-05-10T16:28:09Z Content type: article Language: en Sources: [Engineer's Codex]() Topics: [cursor](), [Software Engineering](), [Code](), [hash](), [Embeddings](), [structure](), [file](), [implementation]() Tags: [code](), [cursor](), [embeddings](), [hash](), [index](), [indexing](), [software-engineering]() ### AI overview This article explains how Cursor indexes codebases using Merkle trees. It describes local code chunking, hash-tree construction and synchronization with Cursor's server, followed by embedding generation through OpenAI's embedding API or a custom embedding model. ### Source excerpt Merkle Trees in the real world ## Simplicity speaks louder than Complexity DevFeed: [Simplicity speaks louder than Complexity]() Original publisher: [Read original article]() Published: 2025-03-08T00:00:00Z Content type: opinion Language: en Sources: [Mutt0-ds Notes]() Topics: [implementation](), [API](), [structure](), [data-engineering]() Tags: [api](), [architecture](), [complexity](), [data-engineering](), [documentation](), [implementation](), [presentation](), [prototyping]() ### AI overview The author describes preparing a technical presentation about StoryTeller, a financial reporting product with an API for generating personalized portfolio reports. The article argues that complex products should initially be explained from the customer's perspective, focusing on structure, interaction, and common errors rather than every technical or mathematical detail. ### Source excerpt A few days ago, I had my first technical presentation at my new company. I joined InvestSuite 3 months ago and it was finally time to... ## System Design Interview Framework DevFeed: [System Design Interview Framework]() Original publisher: [Read original article]() Author: Evan King Published: 2024-11-19T21:39:41Z Content type: tutorial Language: en Sources: [Evan King]() Topics: [Requirements](), [structure](), [systems](), [Framework](), [client]() Tags: [approach](), [framework](), [interview](), [requirements](), [structure](), [system-design-interview](), [systems]() ### AI overview A practical framework for system design interviews that emphasizes delivering a working system. It recommends spending about five minutes clarifying and prioritizing functional and non-functional requirements, with examples involving Twitter and a cache. ### Source excerpt From the co-founder of www.hellointerview.com The easiest way to sabotage your chances of getting an offer in your system design interview is to fail to deliver a working system. This is the most common reason that mid-level candidates fail these interviews. While a firm structure to your approach is important and your interviewer is not trained specifically to assess you on your delivery (often this gets bucketed into "communication"), in practice we've seen many candidates that perform significantly better by following a structure which both keeps them from getting stuck and ensures they deliver a working system. Requirements (~5 minutes) The goal of the requirements section is to get a clear understanding of the system that you are being asked to design. To do this, we suggest you break your requirements into two sections. 1) Functional Requirements Functional requirements are your "Users/Clients should be able to..." statements. These are the core features of your system and should be the first thing you discuss with your interviewer. Oftentimes this is a back and fourth with your interviewer. Ask targeted questions as if you were talking to a client, customer, or product manager ("does the system need to do X?", "what would happen if Y?") to arrive at a prioritized list of core features. For example, if you were designing a system like Twitter, you might have the following functional requirements: Users should be able to post tweets Users should be able to follow other users Users should be able to see tweets from users they follow A cache meanwhile might have requirements like: Clients should be able to insert items Clients should be able to set expirations Clients should be able to read items Keep your requirements targeted! The main objective in the remaining part of the interview is to develop a system that meets the requirements you've identified -- so it's crucial to be strategic in your prioritization. Many of these systems have hundreds of features, but it ## Organizational Tension Processing - Driving Change in Self-Organizing Companies DevFeed: [Organizational Tension Processing - Driving Change in Self-Organizing Companies]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2024-10-05T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [structure](), [Processes]() Tags: [business-culture-employee-happiness-high-purpose-environments-leadership-developer-productivity](), [change](), [hierarchy](), [organizational](), [organizations](), [processes](), [product-development](), [self-organizing](), [structure]() ### AI overview The article explains that self-organizing companies are not structureless or chaotic despite having no traditional people hierarchy. It discusses using a tension-based proposal process to adjust structures, processes, and goals while enabling employees to surface and implement ideas and support faster organizational change. ### Source excerpt Organizational Tension Processing - Driving Change in Self-Organizing Companies Newcomers to self-organization often mistake the lack of a people-hierarchy for complete chaos. The term "flat" can be misleading, as it suggests that self-organizing companies lack any structure. In reality, this is far from the case. [Next page]()