Analysis of Microsoft's Secure Future Initiative report, emphasizing trust as a core architectural dimension and the risks of timing debt in hybrid infrastructure.
Explains how to automate Azure Lighthouse delegation at the management group level using Azure Policy for scalable, consistent multi-tenant management.
Author seeks advice from experienced software buyers for a new 'Observability Governance' section in the upcoming second edition of 'Observability Engineering'.
A practical guide to managing Azure Policy using PowerShell for automation, repeatability, and governance in existing Azure environments.
Explains how to implement access control and security for Apache Iceberg tables at the file, engine, and catalog levels.
A critical opinion piece arguing for the removal of Matt Mullenweg from WordPress leadership due to recent actions and conflicts of interest.
Explains Azure Resource Locks, their types (CanNotDelete/ReadOnly), and how to apply them via the Azure Portal to prevent accidental deletion or modification.
Explores the interconnected principles of trust, ethics, transparency, and accountability in the development and deployment of Artificial Intelligence systems.
A guide to securing Azure DevOps pipelines using approvals, environments, and Azure Key Vault to prevent unauthorized or malicious changes.
Guide to using Azure Policy to audit and automatically apply CanNotDelete resource locks on Azure Resource Groups based on specific tags for governance.
Learn how AWS services like CloudWatch, CloudFormation, Config, and CloudTrail help implement governance, compliance, and audit lifecycles.
Explores how governance in open source projects can be manipulated, drawing parallels to political gerrymandering, using examples like Apache Cassandra.
Explores the concept of 'governance on demand' for open source projects, suggesting formal structures be established only when conflict arises.
A project to map and analyze the governance models of various open source projects, creating a machine-readable resource for comparison and learning.
A developer shares seven key lessons on open source governance, from being conscious about structure to maintaining community kindness.
Explains why applying closed-source, meeting-heavy workflows to open source projects leads to failure and advocates for asynchronous, transparent collaboration.
