# The Result Published articles for The Result. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## OAuth token refresh has a race condition. Fix it with a conditional write, not a distributed lock. DevFeed: [OAuth token refresh has a race condition. Fix it with a conditional write, not a distributed lock.]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-31T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [OAuth](), [race-condition](), [Authorization](), [Auth0](), [Redis]() Tags: [auth0](), [authorization](), [concurrent](), [oauth](), [race-condition](), [redis](), [the-result]() ### AI overview This article explains how concurrent OAuth token refreshes can cause two distinct failures: stale tokens from lost updates and user disconnection when refresh-token rotation treats concurrent reuse as replay. It recommends layered defenses, including conditional writes, and explains why a Redis lock does not address both problems. ### Source excerpt Concurrent refreshes don't just fail. They can disconnect the user entirely. Here are four layers of defense, cheapest first, and why the Redis lock everyone reaches for isn't the one keeping you safe. ## Quantum advantage through trusted quantum computation DevFeed: [Quantum advantage through trusted quantum computation]() Original publisher: [Read original article]() Published: 2026-07-30T10:00:00Z Content type: article Language: en Sources: [IBM Research]() Topics: [Quantum Computing](), [Simulation](), [Benchmark]() Tags: [news](), [process](), [quantum](), [quantum-algorithms](), [quantum-computing](), [quantum-error-correction-mitigation](), [quantum-research](), [reporting](), [science](), [techniques](), [the-result](), [validation](), [verification]() ### AI overview IBM reports three papers demonstrating quantum advantage with built-in validation, including validated error-mitigation techniques and methods for certifying classically hard quantum computations. The article explains how these approaches aim to establish trustworthy results when exact classical verification is unavailable. ### Source excerpt Demonstration shows trusted quantum computation in regimes where classical methods fail. ## How We Built a Zero-Downtime Database Migration Service at Wix DevFeed: [How We Built a Zero-Downtime Database Migration Service at Wix]() Original publisher: [Read original article]() Author: Wix Engineering Published: 2026-05-14T07:19:17Z Content type: article Language: en Sources: [Wix Engineering]() Topics: [Databases](), [migration](), [Data Infrastructure](), [MySQL](), [Scalability]() Tags: [amazon-msk](), [data-infrastructure](), [database](), [database-migration](), [databases](), [db-topology](), [debezium-connector](), [good-tools-doesn-t-fit](), [how-db-mover-works](), [infrastructure](), [migration](), [mysql](), [scalability](), [summary-6-key-focal-points](), [the-challenge](), [the-python-service](), [the-result]() ### AI overview Wix describes DB Mover, an internal service for transparent, zero-downtime database migrations between shared and dedicated MySQL clusters. The article explains the operational risks of shared clusters, migration requirements, and the topology managed by Wix's Data Infrastructure team. ### Source excerpt The Challenge At Wix, multiple applications share the same DB cluster. The reasons vary: consolidating apps from the same domain, grouping several small apps that don't justify a dedicated cluster, or simply optimizing cost and operational overhead. However, this setup comes with a significant risk: every application on the cluster has the potential to impact all the others. One real example: we had a critical service related to user authentication sharing a DB cluster with several other... ## What Happened When We Treated AI Like an Engineering Teammate DevFeed: [What Happened When We Treated AI Like an Engineering Teammate]() Original publisher: [Read original article]() Author: Global Technology Published: 2026-04-28T13:23:51Z Content type: opinion Language: en Sources: [McDonald's Technical Blog - Medium]() Topics: [Artificial Intelligence](), [AI Engineering](), [maintenance](), [Security](), [Cloud](), [test-coverage](), [Documentation](), [Framework]() Tags: [agent](), [ai](), [ai-agent](), [ai-engineering](), [autonomous](), [cloud](), [development](), [documentation](), [maintenance](), [platform-engineering](), [security](), [software-engineering](), [test-coverage](), [the-result](), [velocity]() ### AI overview The Restaurant Topology Management team used an AI-powered, agent-based engineering assistant within its development workflows to handle repetitive maintenance work, including configuration updates, security patches, framework modernization, test coverage, and documentation. The article reports 20% faster sprint velocity, security updates completed twice as fast, and modernization delivered up to 10 times faster. ### Source excerpt How an AI engineering assistant boosted sprint velocity by 20% and modernized services up to 10x faster. by: Sumedha Shenoy, Director, Engineering Tech Lead, and Kamal Jackson, Sr Manager, Engineering Tech Lead Quick Bytes: A growing backlog of essential but repetitive "glue work" was slowing the Restaurant Topology Management (RTM) team's ability to modernize and deliver new features By treating an AI engineering assistant as an autonomous teammate -- not a chatbot -- the team offloaded end-to-end maintenance tasks at scale The result was 20% faster sprint velocity, security updates completed twice as fast, and modernization work delivered up to 10x quicker without sacrificing quality In fast-moving software environments, critical but repetitive "glue work" like configuration updates, security patches, and documentation often compete with time that could be spent delivering new features. For the Restaurant Topology Management (RTM) team -- who build and maintain the cloud-based platform that enables markets to create and deploy consistent restaurant device configurations -- this maintenance workload had grown quietly over time and began to limit the team's ability to innovate. To regain momentum and address mounting operational debt, the team turned to an AI-powered, agent-based engineering assistant embedded into our standard development workflows, capable of handling complex, repetitive tasks. The challenge: The "un-fun" backlog Before piloting the AI assistant, the RTM team was managing maintenance tasks that had persisted across multiple sprints: Security updates: Enhancing automated scanning workflows to maintain a strong security posture Framework modernization: Updating services to align with the team's current application framework Test coverage improvements: Strengthening unit test consistency across services Documentation updates: Refreshing internal service documentation to support smoother onboarding and troubleshooting This maintenance work was important b ## The Result Monad DevFeed: [The Result Monad]() Original publisher: [Read original article]() Published: 2020-05-15T17:31:46Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Kotlin](), [Library](), [Error Handling](), [Exception](), [Android](), [Programming]() Tags: [algorithms](), [android](), [blog](), [career](), [compose](), [development](), [engineering](), [error-handling](), [exception](), [finance](), [functional](), [growth](), [java](), [jetpack](), [kotlin](), [library](), [monad](), [money](), [opinions](), [programming](), [software](), [startups](), [the-result](), [thoughts](), [training](), [tutorial]() ### AI overview This tutorial explains why the Cuvva Android team adopted the kotlin-result library, how Result-based error handling works, and what problems it addresses. It introduces the monad concept and discusses Kotlin's unchecked exceptions in comparison with Java's checked exceptions. ### Source excerpt Recently I've come to really appreciate the kotlin-result library as we've integrated it more and more deeply into the Cuvva Android stack. In this post, I'll explain why we needed it, how it works and what problems it solves, and show some examples of how we use it at the end. A great many people have tried and failed to explain what a monad is, and this is my attempt at being added to the list. ## Creating a simple Kotlin Multiplatform project based on moko-template DevFeed: [Creating a simple Kotlin Multiplatform project based on moko-template]() Original publisher: [Read original article]() Author: IceRock Development Published: 2019-11-08T19:52:31Z Content type: tutorial Language: en Sources: [Stories by IceRock Development on Medium]() Topics: [Kotlin Multiplatform](), [Template](), [Mobile](), [Android](), [iOS](), [Android Studio](), [cocoapods](), [Gradle](), [Binance]() Tags: [android](), [android-studio](), [api](), [build](), [building](), [cocoapods](), [files](), [github](), [gradle](), [ios](), [kotlin](), [kotlin-multiplatform](), [mobile](), [mobile-development](), [multiplatform](), [project](), [repository](), [the-result]() ### AI overview A tutorial for creating a simple Kotlin Multiplatform application for Android and iOS from the moko-template. It covers the required tools, the template's shared library and modules, cloning the generated repository, testing builds, and setting application identifiers, names, and icons. The example application uses the GIPHY API to display GIF files with native Android and iOS interfaces. ### Source excerpt 1. Intro In this lesson we will cover developing small application for iOS and Android using Kotlin Multiplatform based on moko-template. Tools We will need: Android Studio 3.4.0+ (do not use 3.5.1 version, cause there is a bug is breaking MPP project); Xcode 10.3+; Xcode Command Line Tools (xcode-select --install); CocoaPods (sudo gem install cocoapods); JDK -- требуется для запуска gradle из Xcode build phase. The Result As the result of GiphyApp lessons you will get an application to view gif files using GIPHY API. UI of this application will be completely native, player of gif files will make using native libraries glide for Android and SwiftyGif for iOS. 2. Create the project based on moko-template For creation we will use project template from moko-template. The project template already has preconfigured builds of iOS and Andoroid application with shared library and you will save the time to integrate shared library to iOS project on iOS platform, to configure Kotlin Multiplatform modules and dependencies (using mobile-multiplatform-gradle-plugin you can make configuraion is simplier). The project template has a sample of several features as well as. Use this template To use this template you have to go on GitHub репозиторий шаблона moko-template and press a green button Use this template. As the result, you create a new repository according to the last commit of master branch of moko-template project. After succefull creation you should clone this rep: git clone . 3. Test build To be sure that start state is correct, will run the both applications. To do this: on Android: open root repository directory in Android Studio, wait while Gradle Sync will finish, and run android-app as regular application. on iOS: install project's CocoaPods (in directory ios-app run a command pod install, and after this open ios-app/ios-app.xcworkspace in Xcode and press Run for running application. Building of Kotlin/Native can take a time (it will start automatica