# Other Published articles for Other. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## GNOME 51 Released With Improved Frame Scheduling, Many App Improvements DevFeed: [GNOME 51 Released With Improved Frame Scheduling, Many App Improvements]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-16T16:25:21Z Content type: news Language: en Sources: [Phoronix]() Topics: [releases](), [Wayland](), [Release notes](), [Software](), [ui](), [legacy](), [Nvidia]() Tags: [desktop](), [desktop-linux](), [driver](), [experience](), [faster](), [improvements](), [legacy](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [notes](), [nvidia](), [offline](), [open-source-graphics](), [other](), [phoronix](), [phoronix-test-suite](), [protocols](), [release](), [release-notes](), [settings](), [software](), [time](), [ubuntu](), [ubuntu-benchmarks](), [ubuntu-hardware](), [ui](), [wayland](), [workstation]() ### AI overview GNOME 51 has been released with improved frame scheduling and desktop responsiveness, new Wayland protocol support, removal of legacy NVIDIA EGLStreams driver support, and updates to several GNOME applications and settings. ### Source excerpt Right on schedule and in time for appearing in the likes of Ubuntu 26.10 and Fedora Workstation 45, the GNOME 51 desktop is officially released... ## Why do Microsoft job levels start in the high 50's instead of starting at a sane number like 1? DevFeed: [Why do Microsoft job levels start in the high 50's instead of starting at a sane number like 1?]() Original publisher: [Read original article]() Author: Raymond Chen Published: 2026-09-15T14:00:00Z Content type: opinion Language: en Sources: [Raymond Chen]() Topics: [Job](), [Microsoft]() Tags: [job](), [microsoft](), [old-new-thing](), [other]() ### AI overview The article explains why Microsoft's job levels start in the high 50s. Microsoft renumbered its career levels after dividing broad levels into smaller steps, avoiding confusion between old and new level numbers. ### Source excerpt It used to start at 1, but that was the old system. The post Why do Microsoft job levels start in the high 50's instead of starting at a sane number like 1? appeared first on The Old New Thing. ## Why didn't ReadDirectoryChangesW provide a way to correlate the two sides of a rename operation? DevFeed: [Why didn't ReadDirectoryChangesW provide a way to correlate the two sides of a rename operation?]() Original publisher: [Read original article]() Author: Raymond Chen Published: 2026-09-14T14:00:00Z Content type: article Language: en Sources: [Raymond Chen]() Topics: [Filesystems](), [systems]() Tags: [concurrent](), [events](), [files](), [ids](), [implementation](), [information](), [old-new-thing](), [other](), [post](), [systems]() ### AI overview The article explains why ReadDirectoryChangesW did not explicitly provide a mechanism for correlating the two events generated by a file rename. It suggests that the events were expected to occur consecutively, but that assumption was never documented and could fail when concurrent renames or disk activity interleave events. File IDs provide the information needed to correlate the two sides reliably. ### Source excerpt Perhaps it wasn't necessary, or perhaps it didn't occur to them that this a problem. The post Why didn't ReadDirectoryChangesW provide a way to correlate the two sides of a rename operation? appeared first on The Old New Thing. ## Why is the x86 undefined instruction called ud2? Why 2? DevFeed: [Why is the x86 undefined instruction called ud2? Why 2?]() Original publisher: [Read original article]() Author: Raymond Chen Published: 2026-09-10T14:00:00Z Content type: article Language: en Sources: [Raymond Chen]() Topics: [x86](), [Assembly](), [Compiler](), [Exception](), [intel]() Tags: [compiler](), [exception](), [intel](), [old-new-thing](), [other](), [processor](), [x86]() ### AI overview The article explains why the x86 undefined instruction is called ud2. It describes how software used byte sequences that reliably raised an invalid opcode exception, how Intel later provided a standardized instruction, and how compiler output can use it to mark unreachable code and cause a deliberate crash. ### Source excerpt It came after ud0 and ud1. The post Why is the x86 undefined instruction called ud2? Why 2? appeared first on The Old New Thing. ## Beyond the Merge: Enforcing Policy Before the Terraform Apply DevFeed: [Beyond the Merge: Enforcing Policy Before the Terraform Apply]() Original publisher: [Read original article]() Author: Sachin Agarwal Published: 2026-09-03T17:25:32Z Content type: article Language: en Sources: [Nirmata]() Topics: [iac-security](), [Terraform](), [Security](), [Kyverno](), [Tooling]() Tags: [ci](), [cloud-security](), [code-security](), [infrastructure-as-code](), [kyverno](), [other](), [policy-as-code](), [pull-request](), [scanner](), [security](), [shift-left](), [terraform]() ### AI overview The article describes using Nirmata Control and its nctl CLI to evaluate Terraform plans against policy-as-code rules before deployment. It presents pre-apply CI checks for detecting infrastructure misconfigurations, including unrestricted ingress, missing S3 public-access blocking, wildcard IAM resources, and missing VPC deployment. ### Source excerpt Run Terraform security scanning on the plan, not the live account. nctl checks 4 critical misconfigs in CI, with exceptions scoped to one resource. ## Microspeak: Funded / unfunded DevFeed: [Microspeak: Funded / unfunded]() Original publisher: [Read original article]() Author: Raymond Chen Published: 2026-09-01T14:00:00Z Content type: article Language: en Sources: [Raymond Chen]() Topics: [Software](), [Microsoft]() Tags: [developer](), [engineering](), [funding](), [microspeak](), [old-new-thing](), [other]() ### AI overview This article explains Microsoft's use of "funding" as shorthand for having enough people available to work on a feature. It distinguishes funded, partially funded, and unfunded features, and describes how staffing gaps can delay releases without meaning a feature has been canceled. ### Source excerpt People are our most valuable asset. The post Microspeak: Funded / unfunded appeared first on The Old New Thing. ## Building Trust in AI DevOps: Validating the Harness Knowledge Graph DevFeed: [Building Trust in AI DevOps: Validating the Harness Knowledge Graph]() Original publisher: [Read original article]() Author: Vikram Sahu Published: 2026-08-31T18:37:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [DevOps](), [Testing](), [Graphs](), [Artificial Intelligence](), [Software]() Tags: [ai](), [ai-evals](), [api](), [automated](), [data](), [devops](), [evals](), [graph](), [knowledge-graph](), [lifecycle](), [operational](), [other](), [pipeline](), [schema](), [sdlc](), [security](), [services](), [software](), [software-delivery](), [validation]() ### AI overview This article explains how Harness validates answers from its SDLC Knowledge Graph. Its multi-layered approach combines AI evaluations, schema traversal, API checks, direct product verification, production data, and shift-left testing to improve reliability. ### Source excerpt Discover our multi-layered validation approach combining AI evals to ensure reliable AI-powered software delivery insights. | Blog ## Closing the Governance Gap in Nutanix Kubernetes Platform Environments DevFeed: [Closing the Governance Gap in Nutanix Kubernetes Platform Environments]() Original publisher: [Read original article]() Author: Sachin Agarwal Published: 2026-08-24T18:04:51Z Content type: article Language: en Sources: [Nirmata]() Topics: [Kyverno](), [nutanix](), [Kubernetes](), [Platform Engineering]() Tags: [build](), [compliance](), [governance](), [kubernetes](), [kyverno](), [nutanix](), [other](), [platform-engineering](), [upgrades]() ### AI overview Nirmata Enterprise for Kyverno is certified to run on Nutanix Kubernetes Platform through the Nutanix Cloud Platform. The article explains how installing it from the NKP Partner Catalog integrates policy governance, enforcement, and upgrades into the platform without a separate pipeline. ### Source excerpt Kyverno on Nutanix Kubernetes Platform is now certified. Install Nirmata Enterprise for Kyverno from the NKP Partner Catalog, no separate pipeline. ## Introducing the Remediator Agent: Turning Kyverno Policy Violations into Pull Requests, Automatically. DevFeed: [Introducing the Remediator Agent: Turning Kyverno Policy Violations into Pull Requests, Automatically.]() Original publisher: [Read original article]() Author: Akhil Chandran Published: 2026-08-14T11:29:37Z Content type: article Language: en Sources: [Nirmata]() Topics: [Kyverno](), [GitOps](), [Kubernetes](), [pull-requests](), [argocd](), [flux]() Tags: [agent](), [ai](), [argocd](), [flux](), [gitops](), [kubernetes](), [kyverno](), [other](), [pull-requests]() ### AI overview Nirmata's Remediator Agent is designed to automate remediation of Kyverno policy violations within an existing GitOps workflow. It traces violations to their Git sources, proposes deterministic or LLM-generated fixes, commits changes, opens pull requests for review, and relies on ArgoCD or Flux CD to sync approved changes back to Kubernetes. ### Source excerpt Kyverno detects Kubernetes policy violations. Nirmata's Remediator Agent turns them into reviewed pull requests within your existing GitOps workflow. ## Kubo 0.42.0 release: on-demand CID announcements, partial CAR import and export, and reprovide changes DevFeed: [Kubo 0.42.0 release: on-demand CID announcements, partial CAR import and export, and reprovide changes]() Original publisher: [Read original article]() Author: Ipfs Published: 2026-06-08T00:00:00Z Content type: release Language: en Sources: [IPFS]() Topics: [releases](), [version](), [export](), [import](), [migration](), [Routing (disambiguation)]() Tags: [block](), [export](), [gateway](), [import](), [kubo](), [migration](), [other](), [release-notes](), [releases](), [retries](), [routing](), [store](), [terminal](), [version]() ### AI overview Kubo 0.42.0 adds on-demand CID announcements, supports streaming CIDs from standard input, and introduces partial CAR export and import. It also changes providing semantics, fixes pin operations blocked by reprovide cycles, and improves migration retries for older repositories. ### Source excerpt Just released: Kubo 0.42.0! ## Are TypeScript backend frameworks ready for AI agents? DevFeed: [Are TypeScript backend frameworks ready for AI agents?]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-05-20T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Benchmark](), [TypeScript](), [Claude Code](), [backends](), [Express](), [Fastify](), [Nest]() Tags: [ai-coding](), [backends](), [benchmark](), [claude-code](), [express](), [other](), [typescript]() ### AI overview The article reports a three-run benchmark of Claude Code building TypeScript backends with Encore, Express, Fastify, Hono, and NestJS. Although all frameworks passed the first-run tests, only Encore's output met the authors' production-readiness rubric at that stage. ### Source excerpt We set out to run one benchmark across five TypeScript backend frameworks. Reading the diffs sent us into two more runs, and the picture changed each time. ## Introducing Replik8s, a Modern Security Tool for Kubernetes DevFeed: [Introducing Replik8s, a Modern Security Tool for Kubernetes]() Original publisher: [Read original article]() Published: 2025-09-22T16:00:00Z Content type: release Language: en Sources: [Latacora]() Topics: [Kubernetes](), [Security](), [Kubernetes clusters](), [Open Source](), [Incident response](), [AI Agent]() Tags: [ai-agent](), [incident](), [incident-response](), [kubectl](), [kubernetes](), [kubernetes-clusters](), [mcp](), [other](), [security](), [security-tools](), [trivy]() ### AI overview Latacora introduces Replik8s, an open-source Kubernetes tool that snapshots cluster data, serves historical snapshots through a mirror API, supports kubectl and Trivy workflows, and provides query-based analysis for auditing and investigation. ### Source excerpt Introduction # Security tools are often designed to highlight specific issues by consuming APIs and applying predefined logic. Each tool implements its own data structures, storage formats, and evaluation logic. While effective in narrow contexts, this approach creates challenges for teams managing a diverse toolset. Moreover, most tools are optimized to fetch only the data needed for specific findings, limiting their utility in broader contexts such as incident response or historical analysis. ## Announcing Supabase on JSR DevFeed: [Announcing Supabase on JSR]() Original publisher: [Read original article]() Author: Bobbie Soedirgo; Thor Schaeff Published: 2024-07-16T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [JavaScript](), [TypeScript](), [Deno](), [Authentication](), [Web]() Tags: [announce](), [announcement](), [authentication](), [client-library](), [database](), [dependencies](), [developer](), [developer-experience](), [documentation](), [import](), [javascript](), [npm](), [open-source](), [other](), [provenance](), [published](), [real-time](), [registry](), [source](), [storage]() ### AI overview Supabase announces that its JavaScript client library is available on JSR, an open source JavaScript registry. The article describes JSR support for TypeScript source publishing, generated documentation and type definitions, provenance attestation, and npm-like package managers, then outlines installation and use of the client across JavaScript environments. ### Source excerpt Supabase is now available on the open source JavaScript Registry (JSR). ## This Week at Zed Industries: #7 DevFeed: [This Week at Zed Industries: #7]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2023-06-16T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Development](), [Open Source](), [ide](), [Artificial Intelligence](), [dashboards](), [Elixir](), [Cloudflare](), [OpenAI](), [Vercel](), [datadog]() Tags: [ai](), [code](), [development](), [elixir](), [open-source](), [other]() ### AI overview A weekly update from Zed Industries covering plans to open-source Zed on Zed, project-specific settings in v0.90.1, Elixir development improvements, assistant-panel work, inlay hints, analytics tooling, and an unresolved reporting bug involving Cloudflare Workers, OpenAI, Vercel logging, and DataDog. ### Source excerpt We're open-sourcing Zed on Zed and adding an AI-powered assistant panel! ## How to fix the invalid JDK problem on Electric Eel DevFeed: [How to fix the invalid JDK problem on Electric Eel]() Original publisher: [Read original article]() Published: 2023-01-20T00:00:00Z Content type: tutorial Language: en Sources: [Arkadiusz Chmura]() Topics: [Android Studio](), [Android](), [Gradle]() Tags: [android](), [android-studio](), [gradle](), [how-to](), [jdk](), [location](), [other](), [problems](), [terminal](), [updating]() ### AI overview This tutorial explains how to fix an invalid JDK configuration after updating Android Studio to Electric Eel. It recommends checking the project's Gradle JDK setting and updating the environment variable if it still points to the old embedded JDK location. ### Source excerpt When updating Android Studio to Electric Eel, the location of the embedded JDK is changing. ## Medical Device Threat Modeling Boot Camp DevFeed: [Medical Device Threat Modeling Boot Camp]() Original publisher: [Read original article]() Author: Adam Published: 2022-11-01T00:00:00Z Content type: news Language: en Sources: [Shostack & Friends Blog]() Topics: [Bootcamp]() Tags: [boot](), [community](), [medical-devices](), [other](), [partnership](), [training]() ### AI overview The article announces that two Medical Device Threat Modeling Bootcamps are returning. It says the programs are delivered in partnership with the Medical Device Innovation Consortium and provide intensive training, with the next session scheduled for December 12-16. ### Source excerpt Oh my gosh, the boot camps are back! ## Encrypt Your Sensitive Information Before Storing It - Encrypting with Mozilla SOPS and AGE DevFeed: [Encrypt Your Sensitive Information Before Storing It - Encrypting with Mozilla SOPS and AGE]() Original publisher: [Read original article]() Author: Techno Tim Published: 2022-10-01T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Encryption](), [Git](), [.env](), [JSON](), [Kubernetes](), [YAML](), [kubectl](), [Amazon Web Services](), [Azure]() Tags: [aws](), [azure](), [encryption](), [env-file-security](), [format](), [git](), [homelab](), [kubectl](), [kubernetes](), [other](), [passwords](), [secrets](), [tokens]() ### AI overview A tutorial on encrypting secrets before committing them to Git repositories using Mozilla SOPS and age. It covers supported file formats, key creation, encryption and decryption workflows, Kubernetes secrets, environment files, VS Code integration, and Flux-based GitOps workflows. ### Source excerpt Committing secrets to your Git Repo can expose information like passwords, access tokens, and other types of sensitive information.Some might think that committing secrets to a private Git Repo is OK, but I am here to tell you it's not.If you're going to commit secrets to a git repo, private or public, you should encrypt them first using Mozilla SOPS (Secret Operations) and AGE.SOPS is an edito... ## A Junior Software Developer's Journey at Codename One DevFeed: [A Junior Software Developer's Journey at Codename One]() Original publisher: [Read original article]() Author: Sergey Gerashenko Published: 2020-12-07T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Java](), [Programming](), [Kotlin](), [Mobile]() Tags: [cross-platform](), [developer](), [development](), [java](), [journey](), [junior](), [kotlin](), [other](), [software-developer]() ### AI overview A junior software developer describes joining Codename One, learning Java, adapting to UI development, and working on the Kitchen Sink cross-platform demo application before learning Kotlin. ### Source excerpt Hello Codename One community, my name is Sergey Gerashenko. I'm a junior software developer at Codename One. My journey here began 3 months ago when I passed my first interview at Codename One and my first task was to learn Java within 2 weeks. Learning Java I knew a few programming languages like Python, C and C++ but was unfamiliar with Java or managed languages beforehand. Learning a completely new language in just two weeks seemed like an impossible task at first because it took me around five months to learn C++. ## Modules Part 02: Projects, Dependencies and Gopls DevFeed: [Modules Part 02: Projects, Dependencies and Gopls]() Original publisher: [Read original article]() Published: 2019-12-02T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [modules](), [Dependency management](), [Go Language](), [vs-code](), [Protocol (disambiguation)]() Tags: [ardan-labs](), [blog](), [dependencies](), [dependency-management](), [go](), [go-programming](), [golang](), [modules](), [other](), [programming](), [protocol](), [vs-code]() ### AI overview This tutorial explains how Go modules support dependency management and editor integration through gopls, a language server implementing the Language Server Protocol. It introduces the workflow for adding and removing project dependencies and describes the local module cache. ### Source excerpt Series Index Why and What Projects, Dependencies and Gopls Minimal Version Selection Mirrors, Checksums and Athens Gopls Improvements Vendoring Introduction Modules is the system integrated into Go to provide support for dependency management. This means modules touch just about anything related to working with source code, including editor support. To provide editors with support for modules (and for other reasons), the Go team built a service named gopls which implements the language server protocol (LSP). LSP was originally developed by Microsoft for VS Code and has become an open standard. The idea of the protocol is to provide editors with support for language features such as auto complete, go to definition, and find all references. ## Writing a one-time script in Rails DevFeed: [Writing a one-time script in Rails]() Original publisher: [Read original article]() Author: Justin Weiss Published: 2017-02-14T06:08:51Z Content type: tutorial Language: en Sources: [Justin Weiss]() Topics: [Rails](), [Script](), [data](), [migration](), [import](), [CSV](), [Database]() Tags: [capistrano](), [csv](), [data](), [database](), [heroku](), [import](), [job](), [migration](), [other](), [rails](), [rake](), [scheduler](), [script](), [sidekiq](), [structure]() ### AI overview This Rails tutorial explains how to handle one-time data tasks, comparing database migrations with rake tasks and scheduled background jobs. It recommends rake tasks for code that must be tested locally and run in production, while noting when migrations are appropriate and what risks model changes can create. ### Source excerpt Have you ever wanted to import a bunch of data into your app from a CSV file? Or maybe you need to fix badly encoded characters in some of your customer reviews. Or you changed your mind about how you wanted to store data in Redis, and had to move everything from the old format to the new one. At Avvo, we called these "ad-hoc tasks." As in, you probably only need to run them once. So what's the best way to handle an ad-hoc task in Rails? Write a database migration A migration works well if you need to change the structure of the data in your database. It tracks whether the task was run, it carries over changes to other environments - it's what migrations were built for. It's also what you're probably already using them for. If you're changing data at the same time, a migration might work well. But there are some things to watch out for. Calling something like Permissions.create(...) in your migration can cause you trouble. If the model has changed, your migration might break, because your model might not be available when the migration runs. Or your model might have changed between the time you wrote the migration and when it ran. There are ways to get around this, but they're error-prone and can fail in weird ways. Migrations are also less useful if your task doesn't involve ActiveRecord. These aren't deal-breakers. But I tend not to import or change much data in migrations. There are better options. Write a rake task You have a task. You probably only want to run it once. And you want to be able to test it on your machine and run it in production. Rake tasks work really well for this. Rails can even generate rake tasks for you: $ be rails g task locations import create lib/tasks/locations.rake This creates a file for you to stash your code into: lib/tasks/locations.rakenamespace :locations do desc "TODO" task import: :environment do end end Inside that task block, you can use all your models and the rest of the code in your Rails app. It's easy to import and chang