# source of truth Published articles for source of truth. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Rise of the Knowledge Engineer DevFeed: [Rise of the Knowledge Engineer]() Original publisher: [Read original article]() Author: David Isquick Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [Artificial Intelligence](), [AI-assisted coding](), [Users]() Tags: [agents](), [ai](), [ai-trends](), [api](), [developers](), [documentation](), [knowledge-base](), [operational](), [source-of-truth](), [support](), [workflows]() ### AI overview The article examines the rise of the knowledge engineer as companies increasingly serve AI agents that read documentation, compare products, solve support problems, and perform tasks. It argues that organizations need operating systems and processes to keep knowledge accurate, accessible, consistent, and retrievable, because incorrect information can spread through generated code, support responses, and automated workflows. ### Source excerpt Agents are one of the largest audiences for company knowledge, accounting for 66% of measured web traffic across documentation powered by Mintlify. The emerging role responsible for keeping that knowledge accurate and retrievable is the knowledge engineer. ## Design tokens: The building blocks of a design system DevFeed: [Design tokens: The building blocks of a design system]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [Aha! Engineering Blog]() Topics: [Design system](), [ui](), [CSS](), [consistency]() Tags: [atomic](), [component](), [css](), [design](), [design-system](), [source-of-truth](), [structure](), [tokens](), [ui](), [variables]() ### AI overview This article explains how design tokens provide a shared language for visual design attributes in a scalable design system. It contrasts tokens with hard-coded values, describes primitive and semantic tokens, and discusses using the Design Tokens Community Group standard to connect design and engineering. ### Source excerpt Implementing a design system at scale is often less about the pixels and more about the language we use to describe them. As a Senior Software Engineer at Aha! I've spent a lot of time thinking about how we can build a UI that is not only beautiful, ## What are the best platforms for network automation? DevFeed: [What are the best platforms for network automation?]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-07-24T08:25:02Z Content type: article Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [Network](), [Automation](), [Ansible](), [Orchestration](), [awx](), [Low code]() Tags: [ansible](), [automation](), [awx](), [faq](), [low-code](), [nautobot](), [network](), [network-automation](), [orchestration](), [red-hat](), [source-of-truth]() ### AI overview The article lists Nautobot, Itential, Ansible, AWX, and Red Hat Ansible Automation Platform as network automation platforms. It states that they serve different purposes, including configuration, orchestration, source of truth and inventory, and enterprise low-code use cases. ### Source excerpt The best platforms for network automation include Nautobot, Itential, Ansible, AWX, Red Hat Ansible Automation Platform to name a few. Each one serves a different purpose including configuration and orchestration, source of truth and inventory and enterprise low code. Check out my dedicated post on network automation platforms ## From Intent to Reality: Driving pyATS Tests from NetBox Against a CML2 Fabric DevFeed: [From Intent to Reality: Driving pyATS Tests from NetBox Against a CML2 Fabric]() Original publisher: [Read original article]() Author: Brent Leekley Published: 2026-06-15T00:00:00Z Content type: tutorial Language: en Sources: [brent.leekley.me blog]() Topics: [NetBox](), [Network](), [Cisco](), [data](), [Structured-data]() Tags: [cisco-modeling-labs](), [cml](), [cml2](), [custom-fields](), [genie](), [ids](), [intent-based-networking](), [netbox](), [network](), [network-automation](), [network-testing](), [ospf](), [pyats](), [pynetbox](), [router-id](), [source-of-truth](), [spine-leaf](), [structured](), [testbed]() ### AI overview This tutorial shows how to store declared OSPF router-IDs in NetBox and use Cisco pyATS to compare them with the router-IDs on a live CML2 spine-leaf fabric. The comparison turns network intent validation into a pass-or-fail test. ### Source excerpt NetBox holds the intent (declared OSPF router-IDs), a CML2 spine-leaf is the network under test, and pyATS is the judge. Close the loop and prove the live network matches what you said it should be, with real pass and fail output. ## Reducing Single-Person Dependency Through Documentation and Onboarding DevFeed: [Reducing Single-Person Dependency Through Documentation and Onboarding]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2026-01-30T00:00:00Z Content type: opinion Language: en Sources: [Artur Dryomov]() Topics: [Documentation](), [Requirements](), [Code review](), [GitHub](), [GitLab]() Tags: [bus-factor](), [collaboration](), [docs](), [documentation](), [github](), [gitlab](), [onboarding](), [requirements](), [review](), [source-of-truth]() ### AI overview The article reflects on onboarding a new developer and argues that accessible documentation, product requirements documents, and architectural records can reduce reliance on tribal knowledge and make project history easier to understand. ### Source excerpt Onboarding new developers to a team is an opportunity for introspection. It's one thing to share tribal knowledge, and another to realize that the mere existence of such knowledge can be counterproductive. Recently, I had an opportunity to onboard a new developer to one of our projects. Fortunately, almost everything went right. In a couple of days, the developer was able to contribute minor changes to the project, within a couple of weeks, major ones. Of course, a good portion of this rapid involvement can be attributed to the developer, but I believe the approaches described below helped a lot. ## Crafting a Perfect Product Catalog DevFeed: [Crafting a Perfect Product Catalog]() Original publisher: [Read original article]() Author: Shashank Khatri Published: 2026-01-29T11:33:26Z Content type: article Language: en Sources: [Bazaarvoice]() Topics: [data](), [clients](), [trust](), [navigation]() Tags: [apis](), [categories](), [conversations-api](), [data](), [file](), [format](), [ids](), [integration](), [navigation](), [product](), [product-catalog](), [reviews](), [source-of-truth](), [ugc]() ### AI overview This Bazaarvoice post presents best practices for maintaining product catalogs used to manage and display user-generated content such as ratings and reviews. It covers precise product names, consistent category information, and naming conventions for product and category identifiers to support integration, content submission, navigation, and accurate review associations. ### Source excerpt Your product catalog is the definitive source of truth for your online presence, especially when managing User-Generated Content (UGC) like ratings and reviews. For Bazaarvoice clients, a meticulously maintained catalog is vital for seamless integration and flawless display. This post explores three key best practices--from precise product naming and consistent category data to optimal naming conventions--that will unlock the full potential of your UGC program, drive trust, and boost conversions. ## Use Test-Controlled Data as the Ground Truth for Web Page Tests DevFeed: [Use Test-Controlled Data as the Ground Truth for Web Page Tests]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2025-10-03T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Testing](), [Cypress](), [Web](), [Ground truth / benchmark quality](), [data]() Tags: [advice](), [cypress](), [data](), [network](), [process](), [source-of-truth](), [test](), [testing](), [web]() ### AI overview This tutorial explains why tests should not compare two values rendered on a web page as if either value were authoritative. It recommends stubbing the data or network response so the test controls the expected value, while allowing limited duplication when it improves clarity and maintainability. ### Source excerpt Imagine you are testing a web page showing the purchase receipt. ## When Your Source of Truth is Reality DevFeed: [When Your Source of Truth is Reality]() Original publisher: [Read original article]() Author: Dan Lew Published: 2025-07-01T13:00:26Z Content type: opinion Language: en Sources: [Dan Lew Blog]() Topics: [Databases](), [data]() Tags: [data](), [database-design](), [databases](), [source-of-truth]() ### AI overview This opinion article argues that databases tracking real-world entities can never be perfectly authoritative because reality changes and records may be incomplete or inaccurate. It uses a community orchestra roster and other examples to explain the limits of the single source of truth concept. ### Source excerpt Let me tell you a story about why one should be cautious with databases that track the real world. I play trombone in a local community orchestra. For the past two years, I've been the board secretary; part of my duties is keeping a roster of who is ## 4 Software Design Principles I Learned the Hard Way DevFeed: [4 Software Design Principles I Learned the Hard Way]() Original publisher: [Read original article]() Author: Engineer's Codex Published: 2024-04-22T19:03:53Z Content type: article Language: en Sources: [Engineer's Codex]() Topics: [Software Engineering](), [Architecture & Design](), [Software](), [Code]() Tags: [code](), [design](), [software-design](), [software-engineering](), [source-of-truth](), [synchronization]() ### AI overview An experienced software engineer shares design principles drawn from building and launching a large service. The article argues for maintaining one source of truth, deriving values instead of storing duplicate state when practical, and selectively repeating code rather than forcing unsuitable abstractions. It emphasizes that these principles require context and tradeoffs. ### Source excerpt If there's two sources of truth, one is probably wrong. And yes, please repeat yourself. ## The future of Keycloak Operator CRs DevFeed: [The future of Keycloak Operator CRs]() Original publisher: [Read original article]() Author: Václav Muzikář Published: 2022-09-02T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Quarkus](), [Cloud](), [Git]() Tags: [critical](), [declarative](), [deprecated](), [eol](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [operator](), [quarkus](), [rest-api](), [saml](), [source-of-truth](), [sso](), [ui]() ### AI overview The article describes Keycloak's new Operator, rewritten for the Quarkus distribution and available as a preview. It explains that Custom Resource Definitions for managing Keycloak resources are not yet available because supporting features, including file storage and read-only interfaces, are still being developed. The CRDs were expected to be added with support anticipated in Keycloak 21. ### Source excerpt A while back, we have announced a new Operator rewritten from scratch to provide the best experience for the Quarkus distribution. While the legacy Operator is now deprecated and will reach EOL with Keycloak 20, the new one is already available as a preview, see the installation guide. One of the most common concerns around the new Operator is the current lack of the CRDs for managing Keycloak resources, such as realm, users and clients, in a cloud-native way. One of the key aspects of the new Operator will be redesign of managing these Keycloak resources via CRs and git-ops. This new approach will leverage the new storage architecture and future immutability options, making the CRs the declarative single source of truth. In comparison to the legacy Operator, this will bring high robustness, reliability, and predictability to the whole solution. Before we would consider operator ready for leveraging CRs, we expect completing several features including but not limited to: File store (expected in Keycloak 20) to persist data in a file instead of DB. Read-only possibilities for administration REST API, UI Console and other interfaces. This is required for the new immutability concept which will be used to ensure any data coming from the CRs (and subsequently from the file store) are read-only from all interfaces. All of this is critical to proper CRs implementation, hence the new Operator is currently missing the CRDs for managing Keycloak resources. The missing CRDs will be added once Keycloak has the necessary support for it, which is currently expected in Keycloak 21. We have prepared a few options to alleviate the situation with missing CRDs in this repository.