iiinova — where your digital self keeps evolving

You absolutely should! I am, of course, extremely unbiased, but I think it’s a very sound decision

Logistics: Date: Thursday, 8th October Time: 18:00-21:00 Location: ING Cedar, Amsterdam Vibes: immaculate, not coded Insights: spicy and organic Hazels outfit: fire, as always

160

Observability Engineering: What's Next? · Luma

Hey you, do you like o11y? Do you wanna know more about what’s next? What @lizthegrey.com and I are excited about? What’s comes to mind when we think about the challenges companies face? Do you just want a shiny signed copy of the new observability book? (It’s ok, we won’t judge) Come hang out!

luma.com

Hello fellow SREs, Following the summer break we're back with a strong line-up! Together with Honeycomb we are happy to bring you Liz Fong-Jones and Hazel…

1144

Hazel Weakly @hazelweakly.me · 24/09/2026

I am not trying anywhere near hard enough to up my game when it comes to cooking at home

0130

Why yes I resemble every single one of these statements *sobs in data architect*

youtu.be

Interview with Big Data engineer in 2026.

YouTube video by Kai Lentit

1183

Hazel Weakly @hazelweakly.me · 24/09/2026

The conference circuit is not ready for me to turn it into the met gala even more than I already am. I would be a M E N A C E

Hazel Weakly @hazelweakly.me · 24/09/2026

If I ever win the lottery, there will be signs, and one of those signs will be “why do all of hazels dresses and outfits somehow fit perfectly no matter how many flips and acrobatics she does??”

1210

Reposted by Hazel Weakly

Julia M. Rohrer @dingdingpeng.the100.ci · 23/09/2026

I’m a simple girl, I see a paper with an excellent title, I repost.

1223

Reposted by Hazel Weakly

Blacksky Algorithms @blackskyweb.xyz · 23/09/2026

Acorn is one piece of a larger effort to build community infrastructure on the open social web. If your community needs a place to gather, you can start building one now. acorn.blacksky.community

acorn.blacksky.community

Acorn — a platform your community owns

Custom feeds, your own moderation rules, member badges, and a branded client — on infrastructure your community controls.

0658

Hazel Weakly @hazelweakly.me · 23/09/2026

Smh cant believe people are already forgetting about my favourite: delulu

0101

Hazel Weakly @hazelweakly.me · 22/09/2026

Sometimes I didn’t even get to work up a proper frothing rage until nearly tea time and then there wasn’t sufficient time to cool down before headed home. Absolutely inhumane working conditions

020

Reposted by Hazel Weakly

Cat Hicks @grimalkina.bsky.social · 22/09/2026

"Threat has teeth, psychologically-speaking. It dampens our problem-solving, erodes trust, and makes it hard for us to find real collaboration." New at Fight for the Human: on the software identity crisis www.fightforthehuman.com/what-helps-a...

fightforthehuman.com

What helps an identity crisis?

This piece is something special and different on Fight for the Human. And honestly, as a fan of collaborative thinking, distributed cognition, and the notion that innovation is most likely sparked in ...

2113

Reposted by Hazel Weakly

John Timmer @jtimmer.bsky.social · 22/09/2026

Ok, this "there are two separate brains" thing appears to be making the rounds, and I want to be absolutely clear: this is a press office overhyping some perfectly reasonable science that won't come as a surprise to most developmental biologists.

32754238

Hazel Weakly @hazelweakly.me · 21/09/2026

I love you so much ❤️

110

Hazel Weakly @hazelweakly.me · 19/09/2026

If it’s there and can be licked, it will be Actually never mind, whether or not something “can” be licked has zero bearing over whether kiddo will lick it. They will defy physics if necessary, it’s fine

Hazel Weakly @hazelweakly.me · 19/09/2026

Ahhh yes yes this is way too relatable 😅 I grew up in, uhh, quite the bubble I had to pop and get myself out of

110

Hazel Weakly @hazelweakly.me · 19/09/2026

If those were any skinnier they’d be yoga pants 😭

000

Reposted by Hazel Weakly

Ian Coldwater 🧊🚫 @lookitup.baby · 17/09/2026

I for one think it’s critically important to national security for us to beat China at high speed rail. We must invest in this race immediately

734759

Hazel Weakly @hazelweakly.me · 18/09/2026

I’m still (un)reasonably upset at sh vs dash vs bash vs (the outdated as fuck version of bash you get on macOS by default) Whyyyyy

220

Space Cadet Pinball by ksylvestre

Ever randomly get a deep flashback to an earlier time and crave something randomly? Anyways I was reminded that 3D Pinball Space Cadet existed today and, naturally, someone put it on a website ksylvestre.itch.io/space-cadet-... (Theres many versions now, even!)

ksylvestre.itch.io

Play in your browser

0160

AuthZEN Working Group - OpenID Foundation

There’s several others floating around doing great work, and policy engines are making tremendously progress lately. I’m most excited about cedar and the temporal extension for cedar that aws built openid.net/wg/authzen/ (specifically openid.net/specs/author...) snd SPIFFE are also connected, here

openid.net

AuthZEN Working Group - Overview AuthZEN will focus on specific areas of interoperability by documenting common authorization patterns, define standard mechanisms, protocols and formats for communicat...

Remote ATtestation ProcedureS (rats)

Absolutely! It’s easier to link to the working groups in question as there are a lot of documents going on: Remote Attestation (RA): datatracker.ietf.org/group/rats/ Behavioural Evidence: datatracker.ietf.org/group/scitt/ RA + TLS: datatracker.ietf.org/group/seat/ related is confidential computing

datatracker.ietf.org

200

Fully agree! It’s been my life for over half my career now and it’s been a consistent need

That’s the plan! The goal isn’t to magically make the overhead go away, but i think we can make it manageable. more importantly, im hoping to make the work able to be factored out and spread across different teams, organisations, and enterprises. Stretch goal is to span industries and OSS :)

It’s absolutely unreal. It feels like it was stalled for a decade and then just popped up overnight. It’s been really cool to follow the progress and I’m going to start trying to get more formally involved quite soon (as part of this)

Imagine: dynamic procedures, processes, and actions that are (by construction) attested, evidenced, transparent, and trustworthy In other words… Dynamic? No problem. Legible? Absolutely. Reusable? Of course. Regulation got tweaked? Seamless adaptation I’m idealistic, but I’m also optimistic

250

In the last year, all the moving parts seem to have come together just enough to make this a bit less absurd to attempt. But some of the standards are drafts, there are unsolved questions, and how to put it all together remains unknown Naturally, solving that unknown is exactly what I’m attempting

320

Solving this in the industry requires several specific and unusual things that all must be computationally verifiable, constructable, and composable Even worse, they need to be standardised and easily implemented at every layer, all the way down to hardware, all the way up to code on the client

Now, people have tried to solve this before, many times. It’s never really been successful (to my knowledge) because the required building blocks haven’t been in place to make this possible (Unless you pull an AWS and rewrite everything from the hardware up and vertically integrate it all together)

Automating the rest (legibility, transparency, certification, …), as it turns out, is the overwhelming majority of the pain: proving that you fulfil an obligation, proving you can’t bypass the automation, providing the evidence to auditors, along with measurements and testing plans…, and so on PAIN

Which brings us back to why I’m building this platform and designing it the way I am. It was originally a traditional policy engine, with an event system, tightly integrated into internal platforms. Very useful! But that only solves the scaling issue with implementation, not with legibility

Hopefully, the above helps explain why regulated industries move so slowly. It’s also an incredible testament to the power of automation: despite the exorbitant cost, it’s still worth it But it’s a very bitter price to pay! I hate paying it, and I don’t think the cost is inevitable or unavoidablel

Regardless, resolving the “having a property” vs “proving you have it” regulation/legibility paradox is a major unsolved problem in resilience engineering and software engineering I would argue it’s one of the most important unsolved problems of our era, and is woefully underinvested in

As an aside: This is not an anti regulation thread. But you need to understand the price you pay when you build a society that requires internationally trusted institutions for *every* supply chain

As a consequence, the more regulated a property is, the harder it is to achieve. Security? Resilience? Reliability? Performance? Trustworthiness? Those are properties. So, essentially by definition, regulating them makes them harder to achieve. It’s an inextricable paradox of legibility

Which is a major reason why regulated companies don’t get nice things Highly resilient systems are complex by nature, resist categorification, and are illegible. Operating them requires dynamic management systems whose complexity exceeds the system they manage But regulation requires legibility!

(For the more academically inclined, automating regulatory obligations and the supporting infrastructure is typically not reusable for the same reason that mathematical proofs don’t compose It scales poorly for the same reason. Implementing proofs is tedious, nuanced, laborious, and fragile)

*ahem* Pulling back a bit… The cost of doing “one thing” is extraordinarily high, and the cost of automating it is even higher, mostly because that automation does not scale and the implementation is typically not reusable in any capacity

If you’ve ever wondered why “all the smart people” automate everything on their full stack multi cluster gitops everything-as-code agentic harness driven hype machines, yet regulated enterprises spend 100x more to go 100x slower on fax machines, paperwork, and mainframes…. Well, now you know

The CRA, for example, will cost many regulated enterprises millions. Almost all of it will be spent pointing to existing implementations and saying “already done” Millions, hundreds of people, untold hours, on what is effectively a no-op (Luckily the CRA is well written or it would be far worse)

That has the effect of making it so that a single word change in an international regulation can result in either manual: changing a few paragraphs in a few documents, and maybe a few new documents automated: complete rewrite, building new platforms, multi year migrations, and re-orgs

Naturally that actively disincentivises reuse, on top of reinforcing the notion that dynamic is bad and should be avoided at all costs The result: Copy and paste everything! Make every process static! Nothing is dynamic anywhere! Fully draw out the RACI chart! Single pane of glass! Centralisation!