This article investigates how the July 2024 CrowdStrike crash exposed the fragility of automated AI‑driven security systems and their global fallout. - https://t.co/4fWJP7PE3B #cybersecurity#ai
One piece of common wisdom that I've come to disagree with is "do the most complicated thing first." In a waterfall world, that's a risk-reduction strategy, but in an incremental development context, it's actually the opposite.
The fact that some problem is complicated often stems from its not being sufficiently broken down. An "if" statement in a user story, for example, tells me that it's actually two stories, one for the "if" branch and one for the "else." Complex problems are often packed with logic of that sort. So, that "complicated thing" is probably a large bag loaded with multiple tiny stories. It usually turns out that, once you've implemented the core of the core capability, many of those ancillary stories aren't worth implementing at all. When you put something simple into your user's hands and they're happy with that, adding additional complexity is just wasteful.
So, building that entire complicated thing is usually mostly waste.
Instead, break the complicated thing down into small, simple things, then build the most valuable of those first. Get feedback. If people say "That's great!" you're done. If they say, "That's great, but…," you have more work to do. Grab the next small thing and carry on.
I'll add that when I say the above, I'm sometimes met with "we can't break it down—anything smaller doesn't add value!" I've never found that to be the case. When we talk about delivering "value," we're talking about providing something that elicits a nod and a "that's better." Party hats and end-zone dances are not required or expected. You solve big problems by solving small ones, one at a time.
Much like humans, CPUs heal in their sleep.
CPUs are *technically* replaceable / wear items. They don’t last forever.
Yet, the moment stress is removed, transistor degradation (partially) reverses.
It's called Bias Temperature Instability (BTI) recovery:
¡SORTEO de Teclado Keychron K3!
Con luces RGB y con Switches Red o Brown.
¿Cómo participar?
→ Like y RT a este post
→ ¡Sígueme!
✓ Participación abierta a todo el mundo
✓ Resultado el viernes 6 de diciembre
✓ Envíos internacionales
People conditioned to tolerate spurious test failures ignore significant, real failures. If “some tests always fail,” are we sure it’s only the "bad ones"? Once we learn to ignore the tests, we have negated the value of having tests. https://t.co/xPn8yIxmfF
Adding queue semantics as an API over logs provides the cooperative consumption advantages of traditional queues while fixing some of the queue structure's disadvantages: lack of replay and the need for write amplification. Read more in @vanlightly's blog: https://t.co/BOYfQ8EAL9
that feeling when you realize that codefromthecrypt and adriancole who is the no.1 committer of Zipkin are actually the same person https://t.co/N5egqTJBvx
🚀 Today's the Day! 🚀
📢 The wait is finally over! We are thrilled to unveil Tetrate Service Express (TSE) - your ultimate #ServiceMesh solution for Amazon EKS. Register for the 30-day free trial: https://t.co/ECb91Qq9kE
#IstioOnAWS@awscloud
Sign Your Name to Europa Clipper's Message in a Bottle -> You're invited to #SendYourName to Jupiter's moon Europa by signing a poem by U.S. Poet Laureate Ada Limón that will travel aboard NASA's @EuropaClipper spacecraft https://t.co/BJd7E6QDDS
10K FOLLOWER GIVEAWAY 🎉🎈🎁
To celebrate 10K followers on Twitter, we're giving away 3x Raspberry Pi Foundation tote bags containing Raspberry Pi branded goodies 😍 Winners will be randomly selected on Friday, 19 May 2023.
To enter: Follow us, like & RT this tweet.
Good luck!
Short version, 0.15ms extra latency per request.
9% extra CPU when 100% sampling in the 1000 QPS payload.
Sending 4000 spans/s for analyzing service topology, metrics of service and URI, and more
We are unveiling a new product!
Integrated into Amazon #EKS, Tetrate Service Express(TSE) makes it easy for DevOps & DevSecOps teams using @awscloud to quickly see the ROI of an Istio-powered #servicemesh across their enterprise.
https://t.co/8cOSMsCp21
#kubernetes@IstioMesh