Posts Tagged ‘DevOps’
TL;DR Coding is no longer the constraint. It’s now cheaper than ever to make software. But there are supply side constraints on innovation, and getting apps to market. Who dreams up something worth making? How do apps get in front of users? There’s also a demand side constraint on adoption – how do people learn […]
Filed under: code, technology | Leave a Comment
Tags: AI, attention, cloud, coding, demand, DevOps, economics, ideas, innovation, saas, supply, theory of constraints
TL;DR Supply-chain Levels for Software Artifacts (SLSA) attestations are a great way to show that you care about security, and they’re fairly trivial to add to delivery pipelines that produce a single binary or container image. But things get tricky with matrix jobs that build lots of things in parallel, as you then need to […]
Filed under: Dart, Docker, Gemini, howto | Leave a Comment
Tags: AI, ARM, artifact, attestation, CD, container, Cosign, Dart, DevOps, Docker, Gemini, GitHub Actions, image, json, matrix, security, signing, slsa
June 2020
As another month comes to an end, a quick digest of things that June brought… Black Lives Matter June seems to have been another one of those months full of “there are weeks where decades happen”. As a family we spent one of those weeks educating ourselves a little. Starting out with the BBC’s ‘Sitting […]
Filed under: monthly_update, Raspberry Pi, technology | Leave a Comment
Tags: Air Conditioning, AirPods, CogX, DevOps, DOES, Linux, MotionEye, Windows, Windows 10, WSL2
In Plain Sight
“The future is already here — it’s just not very evenly distributed.” – William Gibson This post is about a set of powerful management techniques that have each been around for over a decade, but that still haven’t yet diffused into everyday use, and that hence still appear novel to the uninitiated. Wardley Maps Simon […]
Filed under: culture | 2 Comments
Tags: DevOps, management, maps, SRE, Wardley, working backwards
The Constraint Unblocker
#2 of jobs that should exist but don’t in most IT departments (#1 was The Application Portfolio Manager). What’s a constraint? From Wikipedia: The theory of constraints (TOC)[1] is an overall management philosophy introduced by Eliyahu M. Goldratt in his 1984 book titled The Goal It’s the idea that in a manufacturing process there will […]
Filed under: technology | Leave a Comment
Tags: amazon, aws, constraint, DevOps, Goldratt, James Hamilton, The Goal, The Phoenix Project, theory of constraints, TOC, unblock
Accelerate
TL;DR Accelerate is now my top book recommendation for people looking for practical guidance on how to do DevOps. It’s a quick read, actionable, and data driven. Background I’ve previously recommended the following books for DevOps: The Phoenix Project – Gene Kim’s respin of The Goal is an approachable tale of how manufacturing practices can […]
Filed under: review | Leave a Comment
Tags: Accelerate, book, DevOps, review
Bionix – a primer
This is pretty much a repost of the original Bionics – a primer, but we decided to call it Bionix (with an X). TL;DR Greater automation is the future for the IT industry, and we’ve called DXC’s automation programme ‘Bionix’. It’s about being data driven with a flexible tool kit, rather than being all in […]
Filed under: DXC | 1 Comment
Tags: Bionix, DevOps, SRE
LessOps
JeffConf have posted the video from my talk there on LessOps (or should that be ‘LessOps), which is how I see operations working out in a world of ‘serverless’ cloud service: The full playlist is here, and I’ve also published the slides:
Filed under: cloud | Leave a Comment
Tags: DevOps, LessOps, NoOps, serverless
Marginal cost of making mistakes
In a note to my last post ‘Safety first‘ I promised more on this topic, so here goes… TL;DR As software learns from manufacturing by adopting the practices we’ve called DevOps we’ve got better at catching mistakes earlier and more often in our ‘production lines’ to reduce their cost; but what if the whole point […]
Filed under: code, culture, software | Leave a Comment
Tags: architecture, cost, design, DevOps, economics, mistakes, risk
Safety first
Google’s Project Aristotle spent a bunch of time trying to figure out what made some teams perform better than others, and in the end they identified psychological safety as the primary factor[1]. It’s why one of the guiding principles to Modern Agile is ‘Make Safety a Prerequisite’. The concept of safety comes up in Adrian […]
Filed under: culture | 2 Comments
Tags: DevOps, racing, safety
Chris Swan's Weblog 