How user feedback helps with stability

Feature flags are powerful. However, when poorly managed, they create “ghost errors.” ➡️ To avoid them: Remove old flags, Track their activation, Test all states. 👉 Simple, yet rarely implemented. 👉 Discover our complete article https://lnkd.in/dRXc-UPK

https://lnkd.in/ghVrp8qp "If Rust can have memory safety vulnerabilities, then what’s the point?" "Our historical data for C and C++ shows a density of closer to 1,000 memory safety vulnerabilities per MLOC. Our Rust code is currently tracking at a density orders of magnitude lower: a more than 1000x reduction." "unsafe{} doesn't actually disable all or even most of Rust’s safety checks (a common misconception)." this one is triggering to me when I hear "unsafe turns off borrow checker". It is worth reminding, though, that not everything needs to be rewritten in Rust, and that it won't fix bad design or coding practices. Such a decision should not come out of opinion alone; there must be data to support or reject hypotheses and claims. And the gains must outweigh the costs I personally love #rust, look forward to its continued success and to work both with and on it in the future.

Most people think when we say “Have you tried turning it off and on again?” we’re just being funny… or worse, that we don’t know what we’re doing. Here’s what really happens when you restart a device: When your system runs for too long without a proper reboot, it starts collecting “junk” which are temporary files, memory leaks, stuck background apps, driver conflicts, and even minor software bugs. Then all those tiny problems pile up until suddenly… your laptop starts freezing, your browser crashes, or your Wi-Fi “mysteriously” stops working. So restarting clears all that. It wipes the RAM, closes hanging processes, resets your system drivers, and re-establishes fresh connections to hardware and networks. In other words, it gives your computer a proper reset instead of trying to make it keep running on fumes. So when we tell clients to “turn it off and on again,” it’s not because we don’t know what we’re doing. It’s because we do and experience has taught us that 8 out of 10 problems simply need the system to start fresh. Sometimes, the smartest fix really is the simplest one.

A mistyped hostname? A DNS failure? A misconfigured loop between pull zones? Debugging 502s is a bummer when the smoking gun could be one of a dozen causes, and your downtime clock is ticking. If you’re flying blind, that is. Bunny users deserve better, which is why we just launched origin error monitoring, available now on all plans at no extra cost! → Browse and filter origin errors in the dashboard to pinpoint connection or availability issues. → Or pull logs via API into your systems. This also lets you store them long-term on your end. → Includes both origin-side and rare internal errors, with context like region, edge server, and more. Find out more in the blog (link in comments) ⤵️

Good observability means knowing why your website might not load, and with bunny.net’s new origin error monitoring, that visibility is now built in and free for everyone. 🐇✨ No more guesswork, just clear insights.

No more mystery stream incidents 👻 We just increased incident granularity from 5 minutes to 1 minute. Now when consumption fails, you'll see exactly when and where it happened. Faster root cause analysis. Shorter recovery windows. From this week's changelog — link in comments.

Did you know that fetch() can reject errors? Network errors or AbortSignals cause errors, so you never get a Response object and need to handle these separately. That's annoying so I created Safe Fetch, a wrapper that always returns a Response: https://lnkd.in/gXJfmdHs

A $100M Post-Mortem: The Smart Contract Flaw Behind the Balancer Hack (And How to Audit-Proof Your Protocol) — by CyberDudeBivash Read the full report on - https://lnkd.in/eAQzFpxa

🚫 Facing a 502 Bad Gateway error? Learn the four most common causes of this error and how to fix each one 🔗https://bit.ly/3JUoGda

Being in IT, you kinda expect the weird stuff to happen at 2 a.m. right? But what about the seemingly routine update or the DNS hiccup that everyone misses until services go dark? This article outlines four practical steps you and your team can use to shift from reacting to owning the failure chain. Worth a look. https://bit.ly/3X0WhVK