Stop
We track 19 posts about Stop from 18 engineering blogs. Most active: Auth0, Clickhouse, Cloudflare. Latest post: Oct 9, 2026.
Companies writing about Stop
Recent posts
Vue 3 Composition API: Stop Watcher Memory Leaks in Composables (opens on the source site)
How to manage watcher lifecycles and cleanup in Vue 3 composables, preventing memory leaks when watchers are created outside synchronous setup. Continue reading Vue 3 Composition API: Stop Watcher Memory Leaks in Composables on SitePoint.
How to Stop an AI Agent from Destroying Your Laravel App (opens on the source site)
A practical post on hardening Laravel projects against destructive AI agent behavior. It walks through the PocketOS incident and shows concrete safeguards like deny rules, credential isolation, and production guardrails. Read more
Stop Using Java When Kotlin Exists (opens on the source site)
Despite its many flaws, Java is a fantastic language for a variety of reasons. It’s portable, runs on every device and hosting provider, and is easy to learn. It even has pretty good performance in many aspects due to its just-in-time compiler (which has been recently updated!). On top of that, it’s also incredibly popular. […] The post Stop Using Java When Kotlin Exists appeared first on Atomic Spin.
Adaptive application security for the AI era: how Cloudflare connects code, traffic, and intelligence to stop attacks (opens on the source site)
Cloudflare introduces an adaptive security framework connecting risk discovery, agent governance, runtime protection, and AI-powered response in a continuous learning loop.
If we do not stop to help each other, what do we become? (opens on the source site)
Yesterday, I received this email as a response to You Can't Vibe Code Love. It's such a remarkable and powerful statement that I asked permission to share it here, in its entirety, with personal information redacted:Hey Jeff,Hope you and your family are doing well.
Stop Building MFA from Scratch (And What to Do Instead) (opens on the source site)
Auth0 ·
Learn about the hidden costs of building multi-factor authentication (MFA) from scratch and how Auth0 streamlines the implementation process.
Why You're Getting 429s in Production Using Auth0 and How to Stop Them (opens on the source site)
Auth0 ·
Getting Auth0 429 status code errors in production? They almost always trace back to APIs rate limit. Here are the two causes and how to fix them.
Stop wasting GPU allocation in Kubernetes with GPU-pruner (opens on the source site)
Red Hat ·
In all Kubernetes platforms, idle GPU waste is one of the toughest capacity issues to resolve. You may have seen it yourself: GPUs allocated by other users apparently run for days, doing pretty much nothing. Kubernetes shows that the pods are still running, and the usage bill is still accumulating due to that allocation, but Data Center GPU Manager NVIDIA metrics reveal close to zero engine activity for hours. The post Stop wasting GPU allocation in Kubernetes with GPU-pruner appeared first on Red Hat Developer.
What else runs on your Postgres server, and how do we stop it from taking the database down? (opens on the source site)
ClickHouse Managed Postgres uses runtime budgets, cgroup limits, and disk-full session exemptions to keep supporting services from compromising database availability.
Stop burning tokens on code review (opens on the source site)
I've been experimenting with different approaches to build a system where humans and agents can ship fast safely. Think I've found something that works – custom linters.
Can't Stop, Won't Stop (opens on the source site)
Let's say you have a long-ish Cypress test and you know a place where it might fail. You want to stop / skip the test commands.
Stop The Sprawl Snyk Secrets Now Generally Available (opens on the source site)
Snyk ·
Snyk Secrets is now generally available, bringing contextual ML detection, secure-at-commit prevention, and unified secrets governance to the Snyk AI Security Platform.
Don’t stop early: Case-folding source code at memory speed (opens on the source site)
GitHub ·
How a branch-free loop and byte-space arithmetic let GitHub case-fold every byte of code search at >45 GiB/s on a single core. The post Don’t stop early: Case-folding source code at memory speed appeared first on The GitHub Blog.
Stop writing rules in AGENTS.md: use agent hooks and nano-staged instead (opens on the source site)
Move LLM safeguards out of AGENTS.md: how agent hooks plus nano-staged run linters on changed files only, cut tokens, and tighten the agent's feedback loop
Stop Defaulting to "use client": A Practical Mental Model for React Server Component Architecture (opens on the source site)
How thinking in server-first component boundaries can simplify data flow and reduce client JavaScript in Next.js applications.When I first started working with the Next.js App Router, I kept running into the same situation.Components would suddenly break — usually after adding a hook or a click handler. The fix felt obvious: add "use client".But after doing this a few times, I realised something: I was slowly turning my application back into a traditional client-side React app.Which defeats the whole point of React Server Components.The real challenge isn’t learning how to use Client and…
My 2 Cents: I'll gladly spend them to stop staring at test logs (opens on the source site)
Trivago ·
The problem Does 99.8% represent a good success rate in end-to-end test automation of a web application? What about 99.9%? Maybe yes, but when you have a test suite that has up to 1,000 scenarios, it means often having one or two failing tests, due to the well known issue of test flakiness. Maybe even more than that, when the environment has a bad day. Our preview and stage systems have high availability, but they are obviously not as reliable and performant as production systems, as for example many services might have some increased latency in their responses. So when you trigger your…
Unleashing the Magic of Zendesk Datastore Management: Your One-Stop Self-Service Hub! (opens on the source site)
Zendesk ·
You may be new to this series; and if so welcome! If so, I encourage you to start at the beginning of our datastore journey and see the blog post “Unlocking Efficiency: A New Era for Datastore Provisioning”.Already up to date in our series? MAGICAL — then let’s continue with a quick re-cap.Where are we?We have introduced you to a multitude of aspects all pertaining to how we make the provisioning and utilisation of datastores quick, no-fuss and simple — as simple as clicking your fingers or making a wish.By continuing our theme of MAGIC, we enabled engineers at Zendesk to:Make a wish (detail…
Please stop externalizing your costs directly into my face (opens on the source site)
This blog post is expressing personal experiences and opinions and doesn’t reflect any official policies of SourceHut.Over the past few months, instead of working on our priorities at SourceHut, I have spent anywhere from 20-100% of my time in any given week mitigating hyper-aggressive LLM crawlers at scale. This isn’t the first time SourceHut has been at the wrong end of some malicious bullshit or paid someone else’s externalized costs – every couple of years someone invents a new way of ruining my day.Four years ago, we decided to require payment to use our CI services because it was being…
Stop using encrypted email (opens on the source site)
Latacora ·
Email is unsafe and cannot be made safe. The tools we have today to encrypt email are badly flawed. Even if those flaws were fixed, email would remain unsafe. Its problems cannot plausibly be mitigated. Avoid encrypted email. Technologists hate this argument. Few of them specialize in cryptography or privacy, but all of them are interested in it, and many of them tinker with encrypted email tools. Most email encryption on the Internet is performative, done as a status signal or show of solidarity. Ordinary people don’t exchange email messages that any powerful adversary would bother to read,…
Related topics
This page is generated automatically from the engineering blogs we follow. Every post links to its source, where it was published. See all sources.