News For Dev-ops

During the development of Windows 8, we needed a name for "that thing we're creating." Not being a particularly clever bunch when it comes to code names, we just called it "the modern experience," to distinguish it from what we had in Windows 7, which was called "the classic experience." And then, as Microspeak demands, we started abbreviating like mad. The new shell was called the "modern shell" or "MoSh" for short. By comparison, the old shell was called the "classic shell", which some people started calling "ClaSh" for short. ( That name didn't stick .) When we couldn't come up with a name for a component of the modern experience, a common fallback was to stick the prefix " Mo " in front. The new Start menu derived from some earlier explorations known as the "Go page" (since it's the place you go when you want to do something). Its new code name was therefore "MoGo....

AWS HealthOmics now supports Nextflow version 26.04, enabling customers to take advantage of new Nextflow features and enhancements: record types, the strict syntax parser, workflow output summaries, and agent logging mode. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs at scale with fully managed bioinformatics workflows. The strict syntax parser, now enabled by default in Nextflow v26.04, helps customers save compute time and costs by enforcing strict linting, consistent block structures, and unambiguous scoping, catching issues during pipeline initialization rather than hours into workflows. Record types allow workflow developers to write workflows with meaningful data names rather than keeping track of order of tuple elements, making workflows more readable, and less error-prone. Workflow output summary in JSON format simplifies integration with downstream tooling. Agent logging mode provides ...

Amazon Simple Email Service (Amazon SES) now supports tenant-level suppression lists, allowing email senders to isolate bounces and complaints per tenant. Previously, all tenants in an account shared a single suppression list, meaning one tenant's email issues caused emails for other tenants to be suppressed. With this feature, each tenant maintains a separate suppression list, ensuring that bounces and complaints affect only the tenant that generated them. This capability benefits any sender managing distinct email streams from a single SES account. Key use cases include SaaS providers sending on behalf of multiple customers, enterprises separating transactional and marketing mail across business units, agencies managing campaigns for different brands, or any application where a complaint from one sending program shouldn't suppress delivery for another.  You can configure suppression behavior using two settings: suppression scope (TENANT or ACCOUNT) and suppressed reasons ...

Amazon Connect Customer Assistant is now integrated within the UI builder, enabling contact center managers to create and modify views using natural language. Managers describe what they need, such as "Create a feedback form with rating and comment fields," and the assistant generates the corresponding UI components for review before publishing. This reduces the time and expertise needed to build Views for Step-by-Step Guides and Workspace pages by up to 70%. Managers can use conversational prompts to create views, configure layouts with conditional UIs, set component properties, and apply styling without manual work. The assistant recommends components, explains options, and troubleshoots issues to accelerate builds.  Post Updated on May 28, 2026 at 02:51PM

Modern AI systems have transformed software engineering, but their impact in silicon development has been limited. The primary constraint is that silicon engineering depends on assembling and reasoning over context that is distributed across many systems. Specifications, logs, regressions, waveforms, and prior debug history all contribute to understanding a problem, yet they are rarely accessible within a single workflow. Early applications of AI in this space focused on code generation and isolated tasks. These approaches proved useful for scripting and tooling, but had little effect on core design and verification work. The underlying issue is that most engineering effort is spent reconstructing context before meaningful reasoning can begin. When that context remains fragmented, AI systems operate on partial information and cannot participate in the full problem-solving process. This reflects a fundamental difference in how progress is made. Software workflows can rely on rapid i...

BUILD 2026 begins on Tuesday, June 2, and there will be tons of exciting announcements from the Microsoft Agent Framework team, Microsoft Foundry, and all things Microsoft AI. If you're traveling to San Francisco for BUILD, be sure to stop by the Microsoft Foundry booths to chat with folks from the Agent Framework team - there'll be stickers! If you can't make it to SF, you can still register online and check out the great sessions: Register for Microsoft Build Looking for sessions with Microsoft Agent Framework to watch online? Start with these breakout sessions. Times are shown in Pacific time; check the session page for the latest schedule. Session Date/time Speaker(s) Description Claw and agent harness in Microsoft Foundry (BRK243) Wed, June 3, 11:30 AM–12:15 PM PT Glenn Condron, Amanda Foster, Shawn Henry Go deep on multi-agent systems, Claw agent patterns, hosted agents architecture, triggers, state management, and file access. From prototype...