News and Tech Update

Reactive autoscaling is a critical safety net . Demand rises, metrics spike, policies trigger, and capacity increases. But flash-crowd events, product drops, major campaigns, and limited-inventory moments do not ramp. They cliff. Users arrive at once, and reactive scaling is structurally late because “scale triggered” is only the start of the journey to usable capacity.   If your demand spike arrives faster than your system can warm up, reactive scaling will lag no matter how well you tune it. The fix is planning and verification: scale before the event and prove the system is ready before customers arrive.   This article outlines a practitioner approach: schedule-aware, tier-based predictive scaling using capacity targets and an executor that verifies readiness.   Why Reactive Scaling Loses Against Flash Crowds   Reactive scaling assumes:   Demand ramps gradually enough to be detected early.   Signals (CPU, request rate, latency) change soon enough to trigger action.   Pro...

GitHub’s AI assistant has been a fixture in developer IDEs for a few years now. But the company just made a significant move: It launched the GitHub Copilot app in technical preview, and this isn’t just another interface for writing code. The app is a GitHub-native desktop experience designed for agentic development — letting developers start from the work already in front of them, keep it isolated, steer it as it progresses, and land the change through pull request review. The key difference is that it runs entirely outside the IDE. A New Kind of Developer Workflow For years, developers have toggled between terminals, editors, and browsers to keep a single task moving. The GitHub Copilot app is built around the idea that most of that context already lives in GitHub — so why not start there? Work begins from the issues, pull requests, and prompts already in a repository. Each task runs in its own session, and developers get a single surface to steer, check, and ship the ...

For years, IT and DevOps teams have wrestled with the same stubborn problem: how do you automate workflows in systems that were never built for automation? Legacy apps, vendor portals, and proprietary line-of-business platforms rarely offer APIs. That means someone, usually a human, ends up clicking through screens, entering data, and completing transactions by hand. Microsoft has a direct answer to that problem. Computer use in Microsoft Copilot Studio is now generally available, with expanded availability rolling out to all commercial geographies in Microsoft Power Platform. What Computer-Using Agents Actually Do The simplest way to think about it: computer use gives an agent the same tools a person has — a browser, a screen, a keyboard, and the ability to read what’s on the page and take the next logical step. That’s a meaningful shift. Most automation tools rely on brittle, selector-based scripts that break the moment a UI changes. Instead, the computer uses a tool t...

DevOps.com is now providing a weekly DevOps jobs report through which opportunities for DevOps professionals will be highlighted as part of an effort to better serve our audience. Our goal in these challenging economic times is to make it just that much easier for DevOps professionals to advance their careers. Of course, the pool of available DevOps talent is still relatively constrained, so when one DevOps professional takes on a new role, it tends to create opportunities for others. The ten job postings shared this week are selected based on the company looking to hire, the vertical industry segment and naturally, the pay scale being offered. We’re also committed to providing additional insights into the state of the DevOps job market. In the meantime, for your consideration. Dice Booz Allen Hamilton Chantilly, VA DevOps Engineer $77,600 to $176,000 Lockheed Martin Corporation Herndon, VA DevOps Engineer $85,500 to $150,765 AeroVironment Annapolis, MD DevOps Engi...

When GitLab CEO Bill Staples announced “Act 2” a few days ago , most of the headlines focused on the obvious stuff. Layoffs. Restructuring. Geographic pullbacks. AI agents. Efficiency. The usual collection of terms that now seem mandatory whenever a software company announces its plans for the agentic era. But I think the real story is bigger than that. The real question is whether GitLab can reinvent itself for the next era of software development without losing the cultural infrastructure that made it one of the defining companies of the DevOps movement in the first place. That may sound dramatic, but for those of us who have watched GitLab since its earliest days, this is not just another software company making another AI pivot. GitLab was different. It represented something different. And judging by the reactions from customers, former employees and practitioners across the industry, people instinctively understand that something more significant is happening here. To understa...

Today’s business world operates in a state of constant change. What the customer wants to buy changes quickly, new competitors appear overnight, and cyber threats are changing faster than ever. In this world, the concept of “resilience,” the ability to adapt, to overcome, and to continue to create value for the enterprise despite the changes, has become a top-level imperative for cybersecurity and technology executives. DevOps, the cultural and technical movement to unify the software development and operations disciplines, has come of age as a key enabler of business resilience. Bridging the Dev and Ops Divide: A Culture of Resilience Before DevOps, many organizations were stuck in a cycle of slow releases and siloed teams. Developers would work in isolation for months before handing code off to QA and operations teams for deployment. This adversarial approach to software development hindered innovation within organizations such as Amazon, Netflix, and Google until they adopted a De...