can see this being a very popular service - The call is coming from inside the house.

Cheers

Interesting stat, in a well maintained codebase their is on average one security bug per 1000 lines of code. I wonder what the ratio is for code that isn't well maintained. Tbl code is a liability, reduce the code.

I was thinking before, a lot of the VC money came from Crypto and they got nothing better to spend it on, and likewise those Sovereign Wealth funds it's a rounding error to them

Today, every consultant claims to be an architect, prescribing solutions without question. "How do you know this works?" Unless you've battle-tested it in production, and learnt from feedback, your best practices and reference architectures are just armchair dogma.

The key difference this time is the tech is real, but we’re not the customers anymore, we’re the product being monetised to create the illusion of growth.

Not sure if slop or just sloppy

Reminds me of 'Black Mirror' episode Hated in the Nation (2016) - where Autonomous Drone Insects (ADIs) hunt down whoever gets the most #DeathTo hashtags in a day, turning social media mob hate into deadly real-world consequences

www.imdb.com/title/tt5709...

It's a bit like shrodingers cat, you don't want to be the one who opens that box

Yes, my takeaway don’t draw by hand or rely on icons. Generate immutable, metadata-driven diagrams from CI -store in git, accurate, timestamped, versioned. Use context-specific diagrams to take to meetings to start conversations and solve problems.

FioriDAST sounds interesting, simulates user interactions to surface hidden OData calls which cannot be reached with ZAP alone (eg Flp shell) , sounds like something that customers may want to use, I feel should be opensource

It did read like something easily avoided

I like the format of this one (sim to AWS COE) document customer impact, timeline, root cause via 5 Whys, list immediate fixes, define long-term actions with owners/dates, and track to closure for lasting prevention.

Lol blockchain/ crypto is crack (expensive habit, makes you paranoid, promises you'll get rich) and low-code is heroin (feels amazing at first, then you're chasing that initial high while everything falls apart and all your friends leave you)?

The AWS outage felt like a preview. We’re building on the shoulders of giants long gone. Foundations keep getting more complex while the number of people who actually understand them shrinks. One small DNS slip and suddenly there’s no one left who can put it back together quickly.