# modules Published articles for modules. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Starting Android at Khan Academy DevFeed: [Starting Android at Khan Academy]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-02-29T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Android](), [android-development](), [Development](), [Library](), [modules](), [ci](), [Mocking]() Tags: [android](), [android-development](), [development](), [engineering](), [libraries](), [mobile](), [mocking](), [module](), [modules](), [news](), [open-source](), [picasso](), [play-store](), [pre-commit](), [retrofit](), [test](), [tests]() ### AI overview Khan Academy describes its first Android app, launched in August 2015, and the engineering practices used to build it. The team adopted established Android and open-source libraries, separated Android-independent core code from the app module, and used fast JVM tests and continuous integration. ### Source excerpt By Ben Komalo The journey of a thousand miles... In March, 2015--almost 1 year ago to the day--we ... Read more ## Micron Shows off 512GB DDR5 RDIMM: 12TB per Dual-Socket Server at 9,200 MT/s, Volume Production in 2H 2027 DevFeed: [Micron Shows off 512GB DDR5 RDIMM: 12TB per Dual-Socket Server at 9,200 MT/s, Volume Production in 2H 2027]() Original publisher: [Read original article]() Author: Brian Beeler Published: 2026-09-15T20:18:17Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [ddr5](), [servers](), [intel](), [cpu]() Tags: [capacity](), [ddr5](), [enterprise](), [generation](), [intel](), [memory](), [modules](), [performance](), [production](), [release](), [server](), [speed](), [volume]() ### AI overview Micron demonstrated a 512GB DDR5 RDIMM rated for up to 9,200 MT/s. The module can provide 12TB of memory in a 24-slot dual-socket server, with volume production scheduled for the second half of 2027. AMD and Intel are validating it for next-generation server platforms. ### Source excerpt Micron has demonstrated a 512GB DDR5 RDIMM running on multiple server platforms, which it calls the world's first module at that capacity, and says AMD and Intel are both validating it for their next-generation server platforms. The module is rated for speeds up to 9,200 MT/s, and in a 24-slot dual-socket server it puts 12TB The post Micron Shows off 512GB DDR5 RDIMM: 12TB per Dual-Socket Server at 9,200 MT/s, Volume Production in 2H 2027 appeared first on StorageReview.com. ## jetc.dev Newsletter Issue #328 DevFeed: [jetc.dev Newsletter Issue #328]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-25T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Jetpack Compose](), [modules](), [API]() Tags: [api](), [batching](), [exceptions](), [images](), [jetpack-compose](), [modules](), [newsletter](), [published](), [videos]() ### AI overview Newsletter Issue #328 covers Jetpack Compose development topics, including API modules and composables, lazy-container lifecycle exceptions, recomposition and state-change batching, and selecting and copying text from images and videos. ### Source excerpt API modules and composables! LazyColumn() exceptions! 'Select and copy text' for images and videos! ## Review a Koin upgrade as a graph change, not a version bump DevFeed: [Review a Koin upgrade as a graph change, not a version bump]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Dependency injection](), [upgrade](), [modules](), [test](), [Compose]() Tags: [android](), [compose](), [dependency-injection](), [modules](), [test](), [upgrade]() ### AI overview This tutorial explains how to review a Koin dependency-injection upgrade as an architecture change rather than a simple version bump. It recommends recording the existing dependency graph, modules, warnings, startup results, and verification output; upgrading mechanisms separately; checking all startup variants; and maintaining tested rollback procedures. ### Source excerpt Dependency-injection upgrades can change more than API names. Verification behavior, annotation processing, Compose packages, compiler integration, and deprecations can all alter how the graph is built. Treat the upgrade as an architecture change with a defined before-and-after record. Freeze the current graph Before changing versions, save the dependency lock or resolved graph, the list of DI modules, startup smoke-test results, and verification-test output. Record warnings that already exist so a new warning is not confused with old noise. ## Nix-grove: Configuration framework for flake-parts DevFeed: [Nix-grove: Configuration framework for flake-parts]() Original publisher: [Read original article]() Author: bitbloxhub Published: 2026-08-08T18:32:05Z Content type: comparison Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [configuration](), [modules](), [Framework]() Tags: [announcements](), [configuration](), [framework](), [modules]() ### AI overview A forum discussion introduces Nix-grove, a configuration framework for flake-parts. It describes using the Nix module system to define typed classes and instances, project them into module systems, and override individual results instead of relying primarily on an import=enable pattern. ### Source excerpt AI USAGE: I used ChatGPT (GPT-5.6-Sol) to assist with design and planning, and Pi with GPT-5.6-Luna via openai-codex to help with implementation github.com GitHub - bitbloxhub/nix-grove: Configuration framework for flake-parts: define... Configuration framework for flake-parts: define typed classes and instances, project them into Nix module systems, and override individual results. Sort of an "alternative" to the Dendritic pattern. Still is about importing a bunch of flake-parts modules, but uses the module system for more, instead of import=enable. 6 posts - 3 participants Read full topic ## Emulating Terraform on Pulumi's Engine DevFeed: [Emulating Terraform on Pulumi's Engine]() Original publisher: [Read original article]() Author: Ian Wahbe Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Pulumi]() Topics: [Terraform](), [opentofu](), [terraform provider](), [configuration]() Tags: [engineering](), [hcl](), [modules](), [opentofu](), [protocol](), [providers](), [pulumi](), [terraform](), [terraform-provider](), [translation]() ### AI overview This article explains how Pulumi's HCL interpreter maps Terraform configuration, resources, providers, and modules onto the Pulumi engine. It reports that the implementation works with 96% of Pulumi's top Terraform modules and describes how Pulumi's terraform-provider relays between Pulumi and Terraform provider protocols. ### Source excerpt The core promise of Pulumi's HCL support is that you can bring your existing Terraform configuration and modules, and pulumi will run them. If it works in OpenTofu and doesn't work in Pulumi, we would like to fix that. Given that goal, our HCL interpreter needs to take HCL as input and emit instructions to the Pulumi engine that semantically match how tofu would interpret the same input. This is made harder by the fact that Pulumi and OpenTofu have fundamentally different engine semantics and provider ecosystems. This blog post will explore how we have implemented that mapping well enough to get 96%1 of our top Terraform modules working on Pulumi. We'll briefly walk through how Pulumi's HCL interpreter handles Terraform's resource semantics, providers, and modules. It will also call out where Pulumi's HCL support lets you do things that Terraform and OpenTofu will not allow. Providers Both Pulumi and Terraform have providers, but they don't have the same providers. While there are providers that Terraform does not have, Pulumi can always resolve a Terraform provider using Pulumi's confusingly named terraform-provider provider.2 This is the same provider that lets you consume Any Terraform Provider in another Pulumi program with pulumi package add terraform-provider .... The terraform-provider provider acts as a relay: it speaks Pulumi's protocol to the Pulumi engine, and speaks Terraform's provider protocol to the Terraform provider it stands up. Because Pulumi HCL needs to work with all Pulumi providers and because terraform-provider lets Pulumi HCL speak to Terraform providers via the Pulumi protocol, Pulumi HCL actually only speaks Pulumi protocols directly: flowchart LR subgraph n2Entry[" "] n2["terraform-provider"] end subgraph providerBox["Pulumi Provider"] direction TD n2Entry n3["Terraform Provider"] end n0["Pulumi HCL"] <--> n1["Pulumi Engine"] n1 <--> n2Entry n2 <--> n3 n2@{ shape: rect} n3@{ shape: rect} n0@{ shape: rect} n1@{ shape: rect} style n2Entry f ## A guided tour of Terraform state, hosted modules, and HCL in Pulumi DevFeed: [A guided tour of Terraform state, hosted modules, and HCL in Pulumi]() Original publisher: [Read original article]() Author: Christian Nunciato Published: 2026-08-04T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [Terraform](), [opentofu](), [Amazon S3](), [Command-line interface](), [Cloud](), [GitHub](), [Template]() Tags: [amazon-s3](), [aws](), [cli](), [github](), [hcl](), [how-to](), [infrastructure-as-code](), [modules](), [opentofu](), [pulumi-cloud](), [registry](), [s3](), [terraform](), [tutorials]() ### AI overview A hands-on walkthrough shows how to move a Terraform project that provisions an Amazon S3 bucket into Pulumi Cloud. It covers Pulumi Cloud as a Terraform state backend, hosted Terraform modules, and HCL authoring support, with references to OpenTofu and AWS. ### Source excerpt Today's big release contains a whole new set of features designed for seamless interoperability with the Terraform and OpenTofu ecosystems, and there's a lot there -- so much that it can be tough to get your head around all of it. But it generally falls into three major categories: Support for Pulumi Cloud as a Terraform state backend, including remote execution with human approvals A Terraform module registry in Pulumi Cloud that lets you publish, document, and share your modules even across language boundaries First-class support for HCL as an authoring language in the Pulumi engine To make this release a little easier to appreciate holistically, I've put together a quick end-to-end walkthrough that doesn't quite cover everything, but does cover the big stuff, and should give you a sense of how it all comes together. We'll start with a simple Terraform project that you'll deploy to AWS, and then one step at a time, bring it into Pulumi Cloud and kick the tires on each of these new features as we go. It'll take a bit, but all you'll need are a free Pulumi account and the ability to deploy an S3 bucket to AWS. We've got a bunch to cover, so let's jump right in. Start with a Terraform project Our tour begins with a tiny Terraform project that provisions a single Amazon S3 bucket using a locally defined module that we'll publish later. The project is available on GitHub as a template, and the easiest way to use it is with the GitHub CLI: $ gh repo create my-tf-project \ --template cnunciato/simple-tf-template \ --public \ --clone && cd my-tf-project We'll use the local Terraform backend to start. Set your AWS credentials (preferably with environment variables), then deploy the project with Terraform or OpenTofu. (This walkthrough uses the terraform CLI, but you can swap in tofu if that's your preference.) $ terraform init && terraform apply ... Apply complete! Resources: 2 added, 0 changed, 0 destroyed. Outputs: bucket_arn = "arn:aws:s3:::my-tf-project-bucket-14d19ece" ## Make scalable routing system for your Flutter Apps DevFeed: [Make scalable routing system for your Flutter Apps]() Original publisher: [Read original article]() Author: Kanan Yusubov Published: 2026-07-29T15:25:43Z Content type: tutorial Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Routing (disambiguation)](), [navigation](), [modules](), [Dependency injection](), [Usability]() Tags: [clean-architecture](), [dependency-injection](), [flutter](), [go-router](), [modular-router](), [modules](), [navigation](), [router](), [routing](), [routing-system](), [usability]() ### AI overview This tutorial describes a scalable, decoupled routing system for Flutter apps. It explains a wrapper built on go_router that adds typed route arguments, native and path parameters, cross-module modularization, nested routes, presentation modes, and type-safe route guards. ### Source excerpt Recently, I've been working on migrating our app's routing system. We previously used auto_route, but eventually realized its tightly coupled nature made it incredibly difficult to scale across independent modules. Furthermore, its heavy reliance on code generation became a bottleneck for our workflow. To resolve this, we decided to architect a clean, scalable, and highly decoupled routing system. Our new solution is a powerful wrapper built on top of go_router. It abstracts away the raw string navigation and supercharges the router with custom features to maximize usability and type safety. In this blog post, I will walk you through the core benefits of this new routing system, covering the following key topics: Unified Routing Protocol (AppRouteInfo) Strictly Typed Route Arguments Native & Path Parameters Support Cross-Module Modularization (AppModuleRouter) Hierarchical Back stack & Sub-Routes (Nested Route Definitions, Decoupled Cross-Module Navigation) Dynamic Presentation Modes (e.g., Native, ModalSheet, NoTransition) Guard Interceptor Mechanism (Type-Safe Redirects, Global Interceptors) Note: This blog will show the general usage and problems it solved. For more detailed code, you can check the following link: https://github.com/thisisyusub/scalable-routing-system-demoArchitectural Structure of Routing System Here is how the demo application is structured to achieve a fully decoupled, scalable routing system: scalable_routing_system_demo (main app): The entry point of the application responsible for wiring up all services, dependency injection, and global route configurations. app_routes: Houses all route definitions, parameters, routing protocols, and models to ensure fully type-safe navigation. This is decoupled from the core routing package to separate app-specific business needs from generic routing mechanics. routing_system (core router): A generic, domain-agnostic router package that has zero knowledge of the app's specific routes. It exclusively provid ## Profunctor Optics DevFeed: [Profunctor Optics]() Original publisher: [Read original article]() Author: Bartosz Milewski Published: 2026-07-19T11:39:02Z Content type: article Language: en Sources: [Bartosz Milewski's Programming Cafe]() Topics: [Haskell](), [Programming language](), [Programming](), [modules]() Tags: [category-theory](), [haskell](), [language](), [lens](), [mapping](), [modules](), [optics](), [profunctors](), [programming-language](), [tambara-modules]() ### AI overview This article explains profunctor optics through Tannakian reconstruction. It presents optics as a category, describes lenses and their composition in Haskell, and introduces Tambara modules as a representation that simplifies optic composition. ### Source excerpt You may think of Tannakian Reconstruction as an example of redundant encoding. It lets you replace a simple hom-set with a much more complex end that is taken over an entire functor category. Why would anyone want to do it? The answer is simple: composition! Morphisms on the left compose according to the rules of [...] ## A Gradle Module Structure for Clear Boundaries, Faster Builds, and Test Coverage DevFeed: [A Gradle Module Structure for Clear Boundaries, Faster Builds, and Test Coverage]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2026-07-15T13:38:11Z Content type: article Language: en Sources: [Blogs on Ryan Harter]() Topics: [Gradle](), [build times](), [modules](), [test-coverage](), [Android Gradle Plugin](), [Kotlin]() Tags: [android-gradle-plugin](), [build](), [build-times](), [gradle](), [kotlin](), [modules](), [test-coverage]() ### AI overview The article describes a Gradle module convention that separates each feature's public API from its implementation. The author says this structure reduced build times and coupling between features while helping enforce test coverage, with Android Gradle Plugin support making a separate test-fixtures module unnecessary. ### Source excerpt Flattening my Dependency Graph Jesse Wilson Jesse explores a Gradle module structure that he likes. Read now ➡ I liked this not-so-recent post from Jesse Wilson, which outlines a Gradle module convention that prioritizes clear public/private boundaries to support encapsulation and build speed. The approach, adapted from one presented by Ralf Wondratschek, also happens to closely resemble one that I helped institute at Dropbox shortly after I joined four and a half years ago. ## Tambara Equipment DevFeed: [Tambara Equipment]() Original publisher: [Read original article]() Author: Bartosz Milewski Published: 2026-07-11T08:13:34Z Content type: article Language: en Sources: [Bartosz Milewski's Programming Cafe]() Topics: [modules](), [Haskell](), [Code]() Tags: [category-theory](), [code](), [double-categories](), [double-category](), [haskell](), [modules](), [optics](), [proarrow-equipment](), [profunctors](), [structure](), [tambara-modules](), [tannakian-reconstruction](), [theory](), [transformation]() ### AI overview This article explains Tambara modules through category theory and illustrates the concepts with Haskell code. It discusses their relationship to profunctors, monoidal actions, double categories, proarrow equipment, and Tannakian reconstruction. ### Source excerpt I was originally attracted to category theory when trying to understand Haskell optics. I was puzzled by the van Laarhoven's functor representations and Kmett's use of Tambara modules. By playing Tetris with the Yoneda lemma I was able to make some progress, attacking more and more esoteric topics. With a group of researcher and students [...] ## NixOS 26.05 released DevFeed: [NixOS 26.05 released]() Original publisher: [Read original article]() Author: NixOS Published: 2026-05-30T07:00:00Z Content type: release Language: en Sources: [NixOS Announcements]() Topics: [Nix](), [Linux](), [releases](), [Release notes](), [systemd](), [configuration](), [modules](), [deprecated](), [Package manager]() Tags: [2026](), [accessibility](), [configuration](), [deprecated](), [end-of-life](), [gcc](), [linux](), [llvm](), [macos](), [modules](), [nix](), [nixos](), [release](), [release-notes](), [systemd](), [x86-64]() ### AI overview NixOS 26.05, named "Yarara," is publicly available as a new Linux distribution release. The announcement covers package, module, configuration, systemd initrd, platform-support, GNOME, and compiler changes, along with support timelines for NixOS 26.05 and the previous 25.11 release. ### Source excerpt Hey everyone, we are yayayayaka and jopejoe1, the release managers of the newest release of NixOS. We are very proud to announce the public availability of NixOS 26.05 "Yarara". NixOS is a Linux distribution. Its underlying package repository Nixpkgs can also be used on other Linux systems and macOS with the Nix package manager. This release will receive bugfixes and security updates for seven months (up until 2026-12-31). The old release 25.11 "Xantusia" is now officially deprecated and will reach its end-of-life and stop receiving security updates after 2026-06-30. NixOS Release Notes Highlights New Modules Backward Incompatibilities Other Notable Changes Nixpkgs Release Notes Highlights Backward Incompatibilities Other Notable Changes Nixpkgs Library Upgrade Instructions ISO Image Downloads The 26.05 release was made possible due to the efforts of 2842 contributors, who authored 59703 commits since the previous release. Highlights Our vast and routinely maintained set of packages has also been updated. This release of Nixpkgs Added 20442 new packages Updated 20641 existing packages Removed 17532 outdated packages, in an effort to keep the package set maintainable and secure. In addition to packages from Nixpkgs, the NixOS Linux distribution also features composable configuration modules and integration tests for distributed systems. This release of NixOS Added 85 new modules and 1547 configuration options Removed 25 outdated modules and 355 configuration options. systemd stage 1 Stage 1 (a.k.a. initrd) is now based on systemd by default, and the old scripted implementation is deprecated and scheduled for removal in 26.11. Deprecation of x86_64-darwin This will be the last release of Nixpkgs to support x86_64-darwin. Platform support will be maintained and binaries built until Nixpkgs 26.05 goes out of support at the end of 2026. For 26.11, due to Apple's deprecation of the platform and limited build infrastructure and developer time, we will no longer build packa ## Compose Unstyled 2.0 introduces a foundation for building Compose component libraries DevFeed: [Compose Unstyled 2.0 introduces a foundation for building Compose component libraries]() Original publisher: [Read original article]() Author: Alex Styl Published: 2026-05-14T00:00:00Z Content type: release Language: en Sources: [Composables - Concise, no-fluff video tutorials for Android developers]() Topics: [Compose](), [Design system](), [modules](), [Accessibility]() Tags: [accessibility](), [component](), [compose](), [design-system](), [modules](), [release]() ### AI overview Compose Unstyled 2.0 is presented as a foundation for building custom Compose component libraries. The release introduces composable component APIs, redesigned Dropdown and Tooltip APIs, separate modules, and a fully unstyled core with deprecated APIs removed. ### Source excerpt Compose Unstyled 2.0 is a new foundation for building your own Compose component library. ## Inside the New ESP-Brookesia v0.7 Architecture DevFeed: [Inside the New ESP-Brookesia v0.7 Architecture]() Original publisher: [Read original article]() Author: John Lee Published: 2026-05-04T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [Framework](), [AI Agent](), [Development](), [MCP](), [Large Language Model]() Tags: [ai-agent](), [aiot](), [architecture](), [blog](), [components](), [esp-brookesia](), [framework](), [hmi](), [llms](), [mcp](), [modules](), [orchestration](), [product-development]() ### AI overview This article introduces the redesigned ESP-Brookesia v0.7 architecture for building AIoT interaction products. It describes the framework's layered structure, including hardware abstraction, device services, AI Agent and AI Expression modules, and application layers. It also explains how Function Calling and MCP connect LLMs with device-side functionality. ### Source excerpt This article introduces the redesigned ESP-Brookesia v0.7 architecture, from Utils, HAL, and General Service to AI Agent and AI Expression. It explains how these modules fit together and highlights two examples that help you quickly understand how to build AIoT interaction products on top of the framework. ## Modernizing the Command Line: Heroku CLI v11 DevFeed: [Modernizing the Command Line: Heroku CLI v11]() Original publisher: [Read original article]() Author: Eric Black Published: 2026-03-19T22:29:49Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Command-line interface](), [ECMAScript](), [modules](), [migration](), [maintenance](), [Usability]() Tags: [cli](), [command-line](), [heroku](), [javascript](), [legacy](), [maintainability](), [migration](), [modules](), [monorepo](), [news](), [node-js](), [npm](), [performance](), [release](), [upgrade](), [usability]() ### AI overview Heroku CLI v11 is available with a migration to ECMAScript Modules and oclif v4. The release also changes the build system from Yarn to npm, removes the monorepo structure, improves command execution and manifest caching, and adds semantic colors and theme support. ### Source excerpt Heroku CLI v11 is now available. This release represents the most significant architectural overhaul in years, completing our migration to ECMAScript Modules (ESM) and oclif v4. This modernization brings faster performance, a new semantic color system, and aligns the CLI with modern JavaScript standards. While v11 introduces breaking changes to legacy namespaces, the benefits are [...] The post Modernizing the Command Line: Heroku CLI v11 appeared first on Heroku. ## pg\_plan\_advice: Plan Stability and User Planner Control for PostgreSQL? DevFeed: [pg\_plan\_advice: Plan Stability and User Planner Control for PostgreSQL?]() Original publisher: [Read original article]() Author: Robert Haas (noreply@blogger.com) Published: 2026-03-04T17:55:00Z Content type: opinion Language: en Sources: [Robert Haas]() Topics: [PostgreSQL](), [JOIN](), [modules](), [Query (disambiguation)]() Tags: [join](), [modules](), [plan](), [planner](), [postgresql](), [query](), [test]() ### AI overview The article presents a proposed PostgreSQL 19 patch set introducing the pg_plan_advice, pg_collect_advice, and pg_stash_advice contrib modules. It demonstrates how pg_plan_advice can generate plan advice strings, preserve selected planner decisions, or vary advice to produce a different join plan. ### Source excerpt I'm proposing a very ambitious patch set for PostgreSQL 19. Only time will tell whether it ends up in the release, but I can't resist using this space to give you a short demonstration of what it can do. The patch set introduces three new contrib modules, currently called pg_plan_advice, pg_collect_advice, and pg_stash_advice. Read more " ## 7 steps in a Legacy Modernization Project DevFeed: [7 steps in a Legacy Modernization Project]() Original publisher: [Read original article]() Author: Federico Tomassetti Published: 2026-02-25T06:55:00Z Content type: tutorial Language: en Sources: [Federico Tomassetti]() Topics: [Agile](), [Code quality](), [Code](), [modules]() Tags: [automated](), [business-value](), [code-quality](), [legacy-modernization](), [modernization](), [modules](), [project](), [rpg](), [technical]() ### AI overview This tutorial outlines seven steps for modernizing an RPG-based ERP/MRP system: assess the legacy landscape, define a roadmap, secure buy-in and budget, build the right team and partnerships, execute iterative value-driven increments, manage change, and measure and adapt the modernization effort. ### Source excerpt Embarking on an RPG-based ERP/MRP system modernization is undeniably complex. But it's also highly rewarding when aligned with your business's long-term success. By addressing both the technical and strategic facets, you turn an aging system from a liability into a competitive asset. Let's outline the 7 steps in a legacy modernization project: Step 1: Assess [...] The post 7 steps in a Legacy Modernization Project appeared first on Federico Tomassetti. ## Inspecting the Source of Go Modules DevFeed: [Inspecting the Source of Go Modules]() Original publisher: [Read original article]() Author: Filippo Valsorda Published: 2026-02-12T13:48:03Z Content type: article Language: en Sources: [Filippo Valsorda]() Topics: [Go Language](), [modules](), [integrity](), [Security](), [GitHub](), [Code]() Tags: [cryptographic](), [github](), [go](), [integrity](), [modules](), [security](), [tooling](), [transparency-log](), [verification](), [verify]() ### AI overview The article explains how the Go Checksum Database verifies module source and helps protect against altered tags and targeted versions. It argues that viewing code directly on GitHub can bypass this verification, using a malicious BoltDB module incident as an example, and recommends fetching source with Go tooling for review. ### Source excerpt Code hosts like GitHub don't necessarily show the correct source of Go modules. pkg.geomys.dev is a new convenient viewer for module source. ## From Dagger to Metro DevFeed: [From Dagger to Metro]() Original publisher: [Read original article]() Author: Andrius Semionovas Published: 2026-02-12T00:00:00Z Content type: article Language: en Sources: [Vinted]() Topics: [Dependency injection](), [Android](), [migration](), [Kotlin](), [Dagger](), [interoperability](), [Compiler](), [modules](), [Gradle]() Tags: [android](), [compatibility](), [compilation](), [dagger](), [dependency-injection](), [gradle](), [interoperability](), [kotlin](), [migration](), [modules]() ### AI overview Vinted's Android developers describe their migration from Dagger and related dependency-injection tools to Metro. The article covers their large, modular codebase, Anvil's maintenance status and K2 migration pressure, and Metro's interoperability with Dagger, Anvil, and kotlin-inject. ### Source excerpt Metro - modern and kotlin injection framework created by Zac Sweers. And we, Android developers at Vinted, officially and fully migrated to it! It was quite a bumpy ride for our huge codebase. Our story begins... ## Flattening my Dependency Graph DevFeed: [Flattening my Dependency Graph]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2026-02-03T05:28:50Z Content type: opinion Language: en Sources: [Public Object]() Topics: [Kotlin](), [Persistence](), [Dependency injection](), [PostgreSQL](), [Ktor]() Tags: [dependency-injection](), [kotlin](), [ktor](), [modules](), [persistence](), [postgresql]() ### AI overview The author describes structuring a Kotlin server's dependency graph using a three-module pattern for each feature: public API, implementation, and dependency-injection wiring. The approach aims to support parallel builds, reduce unnecessary rebuilds, and keep dependencies manageable. ### Source excerpt Rounds has a Kotlin server that integrates a few things: PostgreSQL persistence via SQLDelight (hosted on PlanetScale!) WebAuthn4J for Passkeys kotlinx.html for dynamic web pages Ktor for HTTP binding The service uses six database tables. The business domain tables are Game and GameEvent. Support for auth, sessions, and collaborative ## IPLD 2025 Review: From Monoliths to Modules DevFeed: [IPLD 2025 Review: From Monoliths to Modules]() Original publisher: [Read original article]() Author: Volker Mische Published: 2026-01-19T00:00:00Z Content type: article Language: en Sources: [IPFS]() Topics: [Rust](), [modules](), [migration](), [IPFS](), [AT Protocol](), [deprecated]() Tags: [deprecated](), [ipfs](), [migration](), [modules](), [object-object](), [protocol](), [rust]() ### AI overview The article reviews progress in the IPLD ecosystem during 2025 and previews work for 2026. It describes the Rust IPLD implementation's migration to separate crates, its deprecation, improved performance for Python DAG-CBOR and Bluesky custom feeds, and a migration path to Serde-based crates. ### Source excerpt The year that brought us modular Rust libraries, faster DAG-CBOR, stable multiformats, and a simpler on-ramp with DASL. ## go.sum Is Not a Lockfile DevFeed: [go.sum Is Not a Lockfile]() Original publisher: [Read original article]() Author: Filippo Valsorda Published: 2026-01-05T20:06:30Z Content type: article Language: en Sources: [Filippo Valsorda]() Topics: [Go Language](), [modules](), [Security](), [supply chain attacks]() Tags: [dependencies](), [go](), [golang](), [modules](), [security](), [supply-chain-attacks]() ### AI overview The article explains that Go's go.sum is a local cache of cryptographic hashes for the Go Checksum Database, not a lockfile and not part of version resolution. It contrasts go.sum with go.mod, which lists the precise dependency versions used to build the main module and its tests. ### Source excerpt In Go, go.mod acts as both manifest and lockfile. There is never a reason to look at go.sum. ## Creating an Arduino Library for ESP32 DevFeed: [Creating an Arduino Library for ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2025-12-15T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Arduino](), [ESP32](), [Library](), [Development](), [Code](), [C++](), [ide](), [Programming](), [API]() Tags: [arduino](), [arduino-ide](), [beginner](), [blog](), [c-plus-plus](), [class](), [classes](), [code](), [development](), [esp32](), [getting-started](), [guide](), [how-to](), [ide](), [libraries](), [library](), [maintainability](), [modular](), [modularity](), [modules](), [programming](), [structure](), [tutorial]() ### AI overview A step-by-step guide to creating, structuring, and publishing custom Arduino libraries for ESP32. It explains library benefits and structure, prerequisites, and implementation through a minimal "Hello World" example. ### Source excerpt Learn how to create, structure, and publish Arduino libraries for ESP32. This step-by-step guide covers everything from understanding a library structure to submitting your library to the Arduino Library Manager. ## Python in Visual Studio Code - November 2025 Release DevFeed: [Python in Visual Studio Code - November 2025 Release]() Original publisher: [Read original article]() Author: Luciana Abud Published: 2025-11-13T18:41:50Z Content type: release Language: en Sources: [Microsoft Python Engineering]() Topics: [Python](), [Visual Studio Code](), [GitHub Copilot](), [debug](), [modules]() Tags: [copilot](), [debugger](), [developers](), [features](), [github-copilot](), [improvements](), [modules](), [python](), [release](), [visual-studio-code]() ### AI overview The November 2025 release of the Python extension for Visual Studio Code adds Copilot Hover Summaries support for inserting AI-generated documentation as docstrings, localized hover summaries, a Pylance Code Action for converting wildcard imports to explicit imports, and debugger support for multiple project interpreters through the Python Environments Extension. ### Source excerpt The November 2025 release brings new Pylance features including improvements to Copilot Hover Summaries and a Code Action to convert wildcard imports to explicit imports. Keep on reading to learn more! The post Python in Visual Studio Code - November 2025 Release appeared first on Microsoft for Python Developers Blog. [Next page]()