Skip to content

emka.web.id

writing knowledge, recording civilization

Menu
  • Home
  • Tutorial
  • Search
Menu

AI Made Everything Faster, Including Bad Decisions

Posted on October 7, 2026

For years the standard playbook has been: find the holes as fast as you can, rank them by how bad they are, then patch the critical ones before someone actually exploits them. And yeah, that process has gotten better. Automated tools and bots now push fixes faster than most teams could manage by hand. The numbers show critical bugs are getting closed 59% quicker than they were at the peak in January 2024. More than half of them are cleaned up in a single day. On paper that looks like progress.

In reality? We’re still mopping the floor while the faucet keeps running. The sheer volume of new apps (and all the dependencies they drag in) is growing faster than our ability to clean up after them. So even though we fix things quicker, the total number of vulnerabilities keeps climbing. Classic “treat the symptom, ignore the cause” situation.

AI made everything faster, and it’s including the bad decisions

Now we’ve got AI that can spit out code and pull in libraries at a speed no human can match. That’s useful. It’s also a problem. Developers have always been lazy about dependencies — “whatever is popular or already in the package manager” is the usual approach. AI doesn’t fix that habit. It just makes it worse. It’ll happily recommend a library that hasn’t been touched in three years or already has known issues if that’s the quickest way to make the feature work.

The real cost shows up later as rework. You only discover the bad dependency after the code is written, tested, and sometimes already live. Then you’re ripping things out and putting safer versions back in. Pure waste. The safer option was usually sitting there from the beginning — someone just never showed it at the moment of decision.

Make the safe choice the easy one

The answer isn’t more heroic patching at the end of the pipeline. It’s making the secure option the path of least resistance when the dependency is first chosen. Think of it like food labels in a cafeteria: if one option has a clear “safe / maintained / no known critical issues” badge and the other doesn’t, most people will grab the safe one without needing a lecture.

Four things that actually need to happen

  1. Show the risk at selection time, not after the fact.
    When a developer (or an AI) is picking a library, the risk info has to be right there in the IDE or package manager. Waiting for the vulnerability scanner to run later is already too late.
  2. Hold AI to the same rules as humans.
    If your company has approved lists, license policies, or minimum maintenance standards, the AI tools have to respect them. Letting the model ignore policy because “it works” is how you end up with the exact same mess, just generated faster.
  3. Don’t just warn — give the safe path.
    A notification that says “this package has issues” is only half useful. Pair it with an already-vetted alternative or an automated upgrade path that’s been tested. Otherwise people just click through the warning and keep going.
  4. Measure what comes in, not only what goes out.
    Tracking how fast you close vulnerabilities is necessary but incomplete. If the rate of new high-severity issues entering the system keeps rising, your process is still broken upstream. You need both numbers.

None of this has to slow teams down. Done properly, it removes the expensive rework that currently eats time later in the cycle.

Every vulnerability you stop at the decision point saves far more effort than the fastest patch process ever will. We’ve spent years getting better at cleaning up. The next real improvement isn’t another scanner or another bot. It’s fixing the moment the bad dependency gets chosen in the first place.

AI is only going to keep accelerating how fast we write software. That just raises the cost of bad early decisions. So instead of getting better at mopping, maybe it’s finally time we turn the damn faucet off.

Terbaru

  • LibreDB Studio Explained
  • PHP 8.6 Is Officially Out: What’s New, What Breaks, and How We’re Upgrading
  • Rewriting Legacy Apps: 4 Data Migration Strategies That Actually Work
  • How to Install Clean Windows 11 Without Any Bloatware (Step-by-Step Guide)
  • IP Address Rate Limiting is Flawed—Here is the Right Way to Do It
  • Are Fedora 45 Stuck in Its Comfort Zone? A Short Review
  • Hacktober Recap 2026, A Month Full of Dangerous CVE: eMudhra, Gitlab, Brotli, PHP, NodeJS etc
  • 7 Skill Keamanan Jaringan yang Membuat Network Engineer Makin Dibutuhkan
  • How to Spin Up Disposable macOS and Linux VMs on Apple Silicon with TartVM
  • Belajar Cyber Security dari Nol hingga Siap Kerja, Ini Roadmap Lengkapnya
  • Running Windows 11 on Apple Silicon: UTM vs. Parallels Desktop vs. VMware Fusion
  • Testing PikaOS, a Rolling Debian Distribution Special for Gaming and Content Creation
  • Engineering the On-Premises AI Data Center: An In-Depth Technical Review of the HP ZGX Fury AI Station
  • Trying my new Favourite Task Manager, TMOG on Omarchy Linux
  • ASRock Industrial AI Box A395: Is This the Best Compact Strix Halo System for Local AI?
  • Redox OS: A Rust-Based Microkernel Operating System (And How It Differs from Linux)
  • Canonical Is Bringing Back Ubuntu Core Desktop — This Time With a Clearer Plan
  • systemd Officially Adds Support for Rust Components
  • Rocky Linux Creator Builds a Brand-New “Not Linux” Kernel in 11 Days Using AI
  • Building a local AI agent in Workshop on Ubuntu 26.10
  • Omarchy 4.5 RC: 5 New Apps That Actually Look Useful
  • Worth It! Switching from Fedora KDE to Kubuntu
  • I’m Happy Using ‘Herdr’, The Fastest Growing Devtool written in Rust
  • Testing Goose on Omarchy Linux (App & CLI): The Open-Source Solution for Daily Task Automation
  • GNOME Founder Attacks Omarchy Founder as “Lazy, Racist, Ignorant”
  • Why I Stopped Using Plain Command Line Docker and Use Portainer 3.0 To Make My Home Projects Fun Again
  • Why I Switched to a Proper Firewall Box with OPNSense for My Homelab Stuff
  • Fixing Windows Error 0x80070005 Hyper-V Export Access Denied Error the Right Way
  • Fixing Hyper V Export Errors and Building a Better Virtual Machine Setup (error 0x80070002, 0x80070005)
  • Fixing the Dreaded Windows Audio Service Stuck on Stopping Error
  • Canonical: Ubuntu coming soon to Snapdragon X2 Series platforms
  • Finally, wolfSSL adds post-quantum algorithms!
  • How to Run Gemma Embedding Models Using Docker
  • Deploy Nginx Rootful Container with Podman
  • How to Sandboxing Browser on Linux Desktop with Flatpak
  • Qwen 4 Max, Is it A Really New Frontier Model in 2026?
  • OpenCode Browse Explained: Automate Any Website WITHOUT APIs
  • Leaked Qwen 4 and GLM 5.5 Post-Training, Beating the 27B Models
  • Do you Agree? Anthropic Secretly Watermarks All Claude’s Text!
  • Some of New Gemini Notebook Update is CRAZY GOOD: Native Mobile Recording
  • Lagi rame cari Onthel Simulator Indonesia Mod APK, mending pakai yang resmi atau nekat coba versi mod?
  • Gak perlu screenshot manual lagi, Threads punya fitur Copy as Image buat bagiin postingan jadi gambar rapi
  • Lagi rame cari Mod Drag Bike 201m Sunmori versi 5.6, katanya bisa unlock PCX 160 dan uang tak terbatas, tapi aman mboten?
  • Kenapa Paul Gascoigne nangis gara-gara kartu kuning di semifinal Piala Dunia 1990? Ini ceritanya
  • Siapa Kombes Iman Imanuddin? Profil Perwira Polisi yang Namanya Lagi Rame di Kasus Dugaan Makar

©2026 emka.web.id | Design: Newspaperly WordPress Theme