Two thousand feet of half-inch PEX already slept six to eight feet under Craftsman Chris’s yard when his first homemade cooling plan came up short. Four parallel five-hundred-foot slinky loops and a Taco 009 pump pushed water through a heat exchanger in the furnace plenum, yet the dirt had baked in the sun after excavation and the loop stayed warmer than he needed. Direct ground water barely cooled the house. He needed a machine that could pull heat out of indoor air and dump it into that soil instead of into hot summer wind.

Chris ended up with a 14,000 BTU LG Dual Inverter window unit that he fished from a dumpster. After cleaning the coils with Simple Green and a fin brush, and then washing them with soapy water, he was able to free up the condenser fan without touching any of the copper piping. He then moved the outdoor coil roughly 90 degrees without damaging a single copper line, ensuring that the refrigerant remained sealed. A little of scrap sheet metal and a MIG welder came in helpful for creating a water jacket around the coil, and to make it all work, he rigged up the ground-loop water to feed in at the top, surround the condenser, and exit at the bottom into the underground PEX tubing.

Sale

JISULIFE Handheld Fan Pro1S – Next-Gen Airflow: Up to 40H Runtime

• Brushless Motor – Super Power: The combination of a three-phase brushless motor and a 5000mAh battery significantly improves the wind speed, power…
• Scroll Switch – Customizable Wind Speed: This small fan adopts a scroll switch design, and the wind speed can be adjusted steplessly. The portable fan…
• Fashionable Design – Metal Body: The body of this handheld fan is made with advanced oxidation technology, giving it a metal-like texture. Its smooth…

Keeping the sealed circuit intact was important since he never cut any tubing or vented the refrigerant, thus the compressor and valves continued to function properly. Of course, new problems arose anyhow. For one reason, oil might accumulate at the new low point of the spun coil, starving the compressor. Then there was the issue of uninsulated aluminum on the water jacket absorbing extra heat, as well as air bubbles requiring a long time to purge. I suppose the final nail in the coffin was that the safety plug on the original power cord wouldn’t reset, so he had to temporarily replace the power cord end. Nonetheless, none of these concerns prevented him from running the test.

The control system for the device remained fairly rough, almost as beat up as the tank. He set together an old programmable logic controller and a linear actuator to hit the stock power button whenever the thermostat signaled for cooling. Not exactly a beautiful interface, but rather a production remnant that looks like it belongs on a plant floor and is being used to click a single button on a thermostat. The water flow rate through the jacket was around 3.3 gallons per minute, utilizing the same Taco pump that already serves the loops.

The first true run produced somewhat better results than the previous plenum-only setup. The air leaving the unit was between 49 and 54 degrees. He detected a temperature split of 26.5 degrees, which is fairly good. Water entering and leaving the underground loops varied by barely 3 to 5 degrees, but the jacket itself typically reached the upper 70s or low 80s. As an extra benefit, the cool air was actually making its way upstairs into the main living area. The next topic on the agenda is whether a single window unit and 2,000 feet of piping in the backyard can keep the entire house cool all summer.
[Source]

from the embarrassing-capitulation dept

Earlier this week we noted how California Democrats fecklessly folded to Paramount’s demands and settled the 12-state antitrust lawsuit against Paramount’s $111 billion merger with Warner Bros. We also noted how the conditions affixed to the deal are largely pathetic, and generally consist of a lot of performative fluff Paramount itself recommended and California AG Rob Bonta had previously laughed off.

But Bonta is thinking politically about not just Paramount’s lobbying influence, but any future relationships with potential presidential candidate Gavin Newsom or potential future California governor Xavier Becerra (both of whom rushed to pushing for settlement).

None of the conditions meaningfully protect consumers, labor, and markets from what’s coming, but they clearly spent a lot of time designing conditions that let them pretend otherwise.

That includes a purported “independent CBS and CNN oversight board” that’s supposed to prevent Larry Ellison from degrading CNN and CBS’ editorial mission even further. That’s something Paramount itself first floated last August, largely because it knows it will be able to safely ignore it (just as Rupert Murdoch did when he struck a similar deal after the acquisition of the Wall Street Journal).

And sure enough; as details leak out it’s clear the board is largely decorative. Insiders have already noted how the “independent” board will consist of journalists that have at least ten years experience in journalism, but they’ll be hand picked by Paramount:

“According to the terms of the settlement, the board must be established within 180 days of the closing of the deal. It will be composed of five current or former journalists with at least 10 years of experience each and will be appointed by the board of the company for three-year terms.”

That’s just profoundly embarrassing. There’s absolutely zero chance that Paramount is going to appoint the kind of folks capable of pointing out that Ellison, and underlings like Bari Weiss, are actively working to convert CNN and CBS into corporation and oligarch-friendly agitprop. And there’s really nothing preventing Paramount from tap-dancing around the requirements.

I’m sure, like a stopped clock, this board will occasionally and initially make a useful decision to give the impression it’s a real entity. But historically this stuff is designed to prevent real oversight, particularly by government. Former and current insiders at the network simply aren’t impressed:

“There is no way that is going to work,” former CNN anchor Jim Acosta said. “They will start to fire anchors and certain folks to send a message, and the rest will either have to fall in line or leave. This was a colossal mistake.”

CNN and CBS were already pockmarked with a lot of weak-kneed corporation-friendly journalism. Now that Ellison’s involved, both will indisputably begin to look more and more like other right wing propaganda outlets like the New York Post and Fox News.

These kinds of conditions are designed to make it look like responsible people are doing something about media consolidation — without actually doing anything about media consolidation. You protect consumers, labor, and markets by actively enforcing antitrust law; not by endlessly designing half-cooked half-measures that state regulators then fail to consistently enforce.

What’s extra embarrassing is that Democrats like Bonta, Karen Bass, and Newsom had an opportunity here to demonstrate that Democrats had backbone and actually care about subjects like media reform, media consolidation, and the rise of right wing propaganda and disinformation.

Instead they immediately buckled to Ellison’s threat that he’d move Paramount out of California, and are now patting themselves on the back for “saving jobs” — when the end outcome of these deals is always thousands of layoffs as the bigger company offloads merger debt to labor and consumers.

One nice thing about antitrust: if U.S. politicians were to actually enforce the law, we’d have markets more heavily peppered with the kind of small and mid-sized companies that lack the scale and political influence to threaten government when it tries to enforce the law.

Throughout this whole process Paramount (and by proxy a consolidated press) have made it sound like the 12 states were engaged in “radical leftism” simply by enforcing existing antitrust law. It’s important to remember how little Newsom, Bonta, Bass, and Becerra cared about standing up to corporate power the next time you’re in the voting booth.

Filed Under: consolidation, corruption, david ellison, gavin newsom, hollywood, larry ellison, mergers, movies, oversight board, rob bonta, tv

Companies: cbs, cnn, paramount, warner bros.

Disney+ and Hulu subscribers are about to pay more for their streaming services as Disney rolls out another round of price hikes.

The increases affect both ad-supported and ad-free subscriptions, although customers who subscribe to the ad-supported Disney+ and Hulu bundle will see no change. The largest increases are coming to the standalone ad-free plans, which will each cost an additional $2.50 per month, a roughly 13% increase.

Subscribers could begin receiving notifications about the price increases as early as Wednesday. The new prices are as follows:

• Disney+ without ads: $21.49, up $2.50
• Hulu without ads: $21.49, Up $2.50
• Disney+ and Hulu without ads: $21.99, up $2
• Disney+ with ads: $12.49, up $0.50
• Hulu with ads: $12.49, up $0.50
• Disney+ and Hulu with ads: $12.99, unchanged

The ad-supported Disney+ and Hulu bundle is the only plan exempt from this next batch of price increases. At $12.99 per month, it costs just 50 cents more than subscribing to either service individually with ads.

AppleInsider has some deals for new Disney+ bundle subscribers. Deals include Disney+ and Hulu for $11.99 for the first six months, or a Disney+, Hulu, and HBO Max plan starting at $19.99 per month.

Tom Clancy’s The Division and The Division 2 are two of my favorite online and co-op games of all time; I still play The Division 2 most months (at least) and have done so since launch.

The second game still has a committed player base and is a game that keeps on going and keeps on giving for fans who play regularly and those who come back occasionally.

NYU Tandon assistant professor Nana Obayashi and Ph.D. student Daniil Filimonov built WorMa so one undulating machine could inspect a coastline, a flooded street, or a wetland without extra limbs or a second gait. WorMa blends “worm” and “mass,” and that mash-up is the entire plan. Five 3D-printed segments form a body about 50 centimeters long and a little over one kilogram. Four servos at the joints send a traveling wave down the length. Silicone pads under the belly give directional grip on dirt or pavement. Foam disks along the sides keep the robot from sinking once it enters water. An ESP32 runs the servos and the pump.

Nearly 350 grams of water, or 28% of the robot’s total weight, are suspended in two latex balloon reservoirs located inside the robot’s head and tail. They are linked by a piece of silicone tubing, allowing the water to be transferred back and forth. In the robot’s center, a 12-volt peristaltic pump stirs the water, slowly transporting it from one end to another. It takes little under 110 seconds for the pump to completely drain one reservoir and refill another. By shifting the water around, the robot can change where its weight is, on the ground or in the water, while still maintaining its wavelike movement. The water in the head reservoir adds weight to the robot’s front end, strengthening its grip on the ground. The water at the tail end lessens the weight at the front, causing the robot to move differently on the surface.

Sale

ELEGOO UNO R3 Smart Robot Car Kit V4 with Camera, Compatible with Arduino

• BUILD, CODE & DRIVE YOUR OWN ROBOT CAR: Turn coding, electronics and engineering into a working programmable robot car you can assemble, program and…
• EXPLORE FPV, LINE TRACKING & OBSTACLE AVOIDANCE: Control the robot with the ELEGOO app or IR remote, view live FPV video through the onboard camera…
• BEGINNER-FRIENDLY BUILD WITH GUIDED WIRING: Keyed XH2.54 connectors help reduce wiring mistakes, while the illustrated tutorial and example programs…

When you take the robot up a 19.5-degree incline, the only setup that can gain enough grip at the front to haul the entire thing up is the head-heavy one. That front weight also reduced transportation costs by more than a third as compared to other weight placements, but other layouts simply couldn’t obtain enough bite at the nose to climb over the slope’s lip. Jumping a 15cm step is simple and only requires a quick pumping sequence. When WorMa approaches a step with water at the front, the front end grabs it and pulls it up; the water then flows to the back, allowing the lightened front to rise up and grab the edge. Water returns to the head so the robot can haul the rest of its body over. A fixed mass distribution failed even a four-centimeter step.

Things flip on their head in the pool. WorMa swims 26% faster and 52% more efficiently with water in its tail. It is moving at 9.6 cms per second at one point, yet returning to dry land requires the exact opposite movement. The water must shift back to the front, allowing the leading pads to grab and lift the robot out of the water. If you do this with a hefty tail or an even weight split, it will remain stuck at the waterline.

Tying all of this together, the robot can move on flat ground, navigate a step, climb a slope, and swim in water, all while moving 300 grams of water at each stage. An operator can still determine when to move the water. If this type of robot is ever going to roam a real shoreline on its own, upgrading to quicker pumps and an inbuilt system that allows it to rebalance in real time seems like a logical next step.
[Source]

If you want to learn how to code, but in your own time and without it costing an arm and a leg, here are some useful resources.

In 2026, despite the rising popularity of vibe coding, there are a multitude of STEM-based careers that require employees to have strong, traditional coding skills. You may want to improve yours or even begin from scratch, but if you find that standard courses are costly or too time consuming, it can be a deterrent.

But fret not, because there are plenty of opportunities to develop coding, skills be it with personal or professional goals in mind – and they don’t have to drain your time or your finances. 

So, if you want to build on your programming skills, but aren’t sure where to go, the following six resources could be exactly what you are looking for. 

Codewars

Codewars is a site for the students and professionals who want to broaden their skills, but who also want to have a little fun along the way.

The platform aims to help learners “achieve mastery through challenge” via training with peers on code kata – small coding exercises – that continuously challenges. Users can sharpen their skills, go up in the ranks though the challenge board, engage with a broad community of fellow learners and receive instant feedback to determine if progress is being made.

You can even create your own challenges and questions and put them to the wider community. The creators aptly refer to the site as a coding dojo and whether you are a student or sensei, there is definitely something to be gleaned from Codewars. 

Exercism

UK-based Exercism describes itself as a platform focused on “building a place where anyone can learn and master programming for free, without ever feeling lost or stupid”. Students of all abilities can learn how to code in 83 different languages via articles, videos and project work, with the goal being to have fun and progress, without stress or competition.

The platform also offers a wide community of peers with which to collaborate and build friendships, as well as a wide network of mentors to guide the learning process. 

FreeCodeCamp

FreeCodeCamp is exactly what it sounds like. This free platform is a resource through which students can learn how to code via a collection of podcasts, videos, articles and interactive lessons.

The available curriculum is expansive, can be engaged with via a number of different spoken languages and comes with a free certificate of completion. There are available learning options for beginners all the way through to advanced students and engagement is solely at the discretion of the user.

LeetCode

If you are a professional or a recent graduate preparing for a job interview that will likely demand robust coding skills, LeetCode is the ideal resource to test yourself in advance. The free-to-use platform supports 14 popular coding languages and enables users to debug and write their own online projects.

Students can test their coding knowledge by answering some of the more than 4,300 questions available. Users can also engage with a wide community of peers, participate in contests, challenge themselves and earn rewards.

If you have some skills but are looking to hone them, with future career opportunities in mind, this is definitely the place for you. For those who want a broader experience, there is also a premium paid feature. 

The Odin Project

The Odin Project, which is a free open-source learning platform, is an ideal site for a student or professional looking to advance their coding skills. The goal is to empower students to embark upon a career that requires coding, particularly those looking to become developers, though it is open to anyone who wishes to use it. 

The platform offers a hands-on introduction to all of the essential tools you’ll need to build real, working websites and also offers information on what web developers actually do and the foundations they might need for advancing their education. “This project is designed to fill in the gap for people who are trying to hack it on their own but still want a high-quality education,” according to the site.

Programiz

Programiz’s mission is to create a space in which learners can learn how to program easily and at their own pace. The platform offers tutorials in a variety of languages, the browser is free to use and no installation is required.

Programiz claims to teach the skill of coding step by step, via the use of online compilers available in more than 20 languages and interactive lessons that offer a guided path to learning programming with practical code that runs in your browser. 

Don’t miss out on the knowledge you need to succeed. Sign up for the Daily Brief, Silicon Republic’s digest of need-to-know sci-tech news.

In October last year, Spotify started testing a new feature that let users prevent certain songs from affecting their called Taste Profile. The whole idea behind this new trick was to let users customize their music feed and what they see on the homepage based on their specific preferences. Officially, Taste Profile became its own feature and went into the testing phase in May this year, but only for a limited audience. Now, it’s finally making its way to the US market.

Earlier today, Spotify announced that Taste Profile is now available to all users who are above 18 years of age in the US. “Taste Profile gives you more control over your recommendations, whether you want to explore beyond your usual interests or fine-tune what you already love. For the first time, you can see Spotify’s brief interpretation of your taste across music, podcasts, and audiobooks,” says the company.

The best part about this feature is that it’s not an overtly technical upgrade and doesn’t need any learning curve. Instead, it takes a conversational approach. So, when you swipe on the homepage and access the Taste Profile option in the side menu, you get a text box where you can write in natural language what it is that you want Spotify to show you more or less of. You can ask it to play more Pink songs in the evening, or surface more news-focused podcasts.

Spotify says these notes ultimately dictate what you see on your home feed, whether it’s discovery of new music, podcast, or a certain kind of audiobooks. Interestingly, the conversational notes that you feed into the Taste Profile search box don’t only cover genres of music, but they also dynamically respond to a certain mood, emotion, or areas of interest, like history, technology, or art.

You just have to describe what exactly it is that you want to hear more of, and your home feed and recommendations will be tailored accordingly. In order to check out the new feature, tap on the profile picture icon in the top corner, open the menu panel, click on Taste Profile, and type your note underneath the Tell us more, label.

Spotify says that once you have dropped a note to adjust your Taste Profile, you will see the changes reflected within a few hours. There’s also an option to edit or delete the notes that you have previously fed into the Taste Profile system. Spotify is separately working on a cache limit feature that lets users handle how much space Spotify’s temporary files take up on your phone’s storage.

RELATED COVERAGE:

First look: Echoing Apple’s recent iPhone 18 unveiling, Qualcomm has introduced two new Snapdragon 8 Elite mobile processors with AI assistants as a primary focus. While the chips significantly outperform the Snapdragon 8 Elite Gen 5 in CPU performance, GPU performance, and power efficiency, Qualcomm clearly sees AI agent support as the new lineup’s main selling point.

Qualcomm revealed the Snapdragon 8 Elite Gen 6 and 8 Elite Extreme Gen 6 at this year’s Snapdragon Summit. The mobile SoCs will power future flagship Android devices from Doubao, Honor, Motorola, Oppo, RedMagic, Stepx, Vivo, and Xiaomi.

Built on a 2nm process node that enhances power efficiency by 37%, both chips feature two Oryon Prime CPU cores that achieve 5GHz, six 4GHz performance cores, and 16MB of Flex Cache. While the standard Elite Gen 6 improves CPU performance by 10% over its predecessor, the Extreme variant extends the gain to 13%.

GPU and NPU performance enhancements are much more impressive. The new Adreno GPUs outperform the Elite Gen 5 by 35% and 44% in the standard and Extreme models, respectively, while raising power efficiency by 40%, partially thanks to AI rendering via the new Adreno Neural Fusion.

Meanwhile, the Elite Gen 6’s Hexagon NPU runs AI applications 14% faster in the standard model and 35% faster in the extreme variant, with AI performance-per-watt increasing by 20% and 33%, respectively.

Most of Qualcomm’s trailer for the Snapdragon 8 Elite Gen 6 focused on showing AI agents automating various everyday tasks that might take humans multiple steps. In one clip, an agent automatically sorts a newly recorded video and provides options for editing it. In another, a jogger receives a notification about a nearby property that meets their preferences, with the option to automatically share a photo and book a viewing appointment.

Regarding sound, AI also facilitates audio separation and voice isolation. Even the Qualcomm X105 5G wireless modem is AI-enhanced, improving energy efficiency while also increasing upload and download speeds. Meanwhile, Qualcomm’s Wi-Fi 8-compliant FastConnect 8800 can achieve 10Gbps with a 4×4 Wi-Fi configuration, tripling the gigabit range over prior models.

Camera performance is another notable difference between the two tiers. 8 Elite Extreme Gen 6-powered phones can record video at up to 60fps in 8K, while the cheaper SoC only achieves 30fps at that resolution.

The earliest devices powered by Snapdragon 8 Elite Gen 6 will include the RedMagic 12Pro+, iQOO 16, and iQOO Pad Ultra.

Cloud migrations often fail or require significant rework because important risks are discovered too late. Hidden dependencies, incompatible workloads, an unprepared target environment, unrealistic migration waves, incomplete testing, data-cutover problems and weak rollback planning can all turn a manageable move into a production incident.

The safest approach is to identify uncertainty before cutover, validate each workload against its target environment, migrate in manageable waves, and define clear acceptance and rollback criteria before production traffic moves.

What Does “Cloud Migration Failure” Actually Mean?

A cloud migration does not have to collapse completely to be unsuccessful. Failure can take several forms. A cutover might be abandoned and reversed, an application might move but no longer meet its functional or performance requirements, or the migration might technically complete while leaving serious operational problems that require immediate rework.

For example, an application could start normally in its new cloud environment while a reporting service remains on-premises. If the two components communicate frequently across a connection with higher latency, the reports may become too slow for their intended use even though both systems remain individually available.

It helps to distinguish four outcomes. A migration blocker prevents a planned workload from moving. A cutover failure prevents the new environment from taking over production successfully. A post-migration defect appears after the workload has moved. Strategic underperformance occurs when the migration technically works but does not deliver the wider business result that justified the project.

This article focuses mainly on the first three because they are closely tied to migration planning, workload preparation and execution. Broader questions about whether cloud transformation achieved its business goals belong in the surrounding digital-transformation strategy.

Failure Usually Starts Before Cutover

Cutover is often where a migration problem becomes visible, but the underlying mistake may have happened weeks earlier. Cloud migration normally moves through discovery, assessment, target design, wave planning, workload preparation, testing, cutover, validation and ongoing operation.

Google Cloud’s migration-planning guidance places workload discovery, dependency mapping, migration-strategy selection and foundation design before migration-wave planning. It also recommends running migration risk assessment alongside continuing discovery so workload-specific risks can refine later decisions.

AWS follows the same general pattern. Its portfolio analysis and migration-planning guidance calls for a high-fidelity inventory, dependency information, a migration strategy for each application, platform readiness and a high-confidence migration-wave plan.

This lifecycle view matters because many apparent migration failures are really assessment or preparation failures that become visible only when production traffic is involved.

Where Cloud Migration Risks Usually Enter the Lifecycle

The same production symptom can originate at different stages. This table shows where several common problems are introduced and the control that should exist before the migration advances.

The table is not a ranking. A weakness early in the lifecycle can create several downstream symptoms, and multiple controls may be needed for the same workload.

Incomplete Inventory and Hidden Dependencies

You cannot safely sequence systems you do not fully understand. A workload may appear to consist of one application server and one database while actually depending on identity services, file shares, third-party application programming interfaces (APIs), batch jobs, monitoring systems, scheduled tasks and other applications.

AWS describes high-confidence dependency data as an important input to migration-wave planning because both technical and nontechnical relationships affect how systems should be grouped. Its wave-planning guidance includes application dependencies, infrastructure dependencies and operational considerations among the inputs used to form migration waves.

Consider an application that makes frequent database calls. Moving the application while leaving a latency-sensitive database behind can make the application appear slow or unreliable even though both components remain individually healthy. A shared database creates another complication because several applications may have to move together or remain temporarily connected across environments.

Discovery therefore needs more than a spreadsheet compiled once at the beginning. Automated discovery can provide communication and infrastructure data, but application owners are still important because technical telemetry may not reveal monthly batch jobs, business-calendar restrictions or integrations that run infrequently.

Google’s migration risk guidance recommends continuing discovery and assessment during wave planning so new workload-specific information can refine scope, priorities and risk mitigation.

Choosing the Wrong Migration Strategy for a Workload

Another failure pattern is applying the same migration method to every application. A workload that can be moved largely unchanged has different requirements from one that depends on unsupported software, requires substantial architecture changes or is better replaced with another service.

Rehosting, often called lift-and-shift, is not inherently a bad strategy. It can be appropriate when the objective is to move with minimal application change. The problem arises when a team chooses it without understanding compatibility, architecture or business requirements.

For example, moving a legacy application unchanged does not resolve a dependency on an unsupported operating system or a hardcoded network address. In that case, remediation, replatforming, refactoring or another workload strategy may be needed before production migration.

Choosing the migration strategy for each workload should follow its compatibility, dependencies, business requirements and acceptable level of change.

Where teams need to distinguish the trade-offs more directly, the difference between rehost, replatform and refactor comes down largely to how much of the existing workload is preserved and how much engineering change the migration can justify.

Building the Migration Plan on Incomplete Business Requirements

A workload can be technically ready to migrate and still be scheduled at the wrong time or moved using the wrong availability assumptions. Migration planning therefore needs business information as well as infrastructure data.

Microsoft’s cloud adoption plan template for migration includes workload criticality, data sensitivity, compliance requirements, maintenance windows, business freeze periods, geographic restrictions and success metrics among the information that should inform migration planning.

Two recovery terms are particularly useful. Recovery Time Objective (RTO) is the targeted time for restoring a service after disruption. Recovery Point Objective (RPO) describes the acceptable data-loss window, expressed as a point in time. Those requirements influence backup, replication, migration and rollback design.

A month-end finance system illustrates the problem. The software may be technically straightforward to move, but a migration window that overlaps financial close could create unacceptable disruption. Likewise, a customer-facing transaction system with a very low downtime tolerance needs a different migration approach from an internal development environment that can be unavailable for several hours.

Migrating Before the Cloud Foundation Is Ready

Workload readiness and target-environment readiness are separate questions. An application can be prepared for migration while the cloud environment still lacks the services and controls required to operate it safely.

Before production migration, teams need to know how identity, network connectivity, Domain Name System (DNS), access control, logging, monitoring, backups and operational support will work in the target environment. Larger organizations may formalize these shared capabilities as a landing zone, while smaller environments may implement a simpler foundation.

Google’s migration-planning guidance places foundation design before migration-wave execution and lists identity and access management, networking, logging, monitoring, billing and security among the target-environment concerns that should be established and tailored to workload requirements.

Moving first and designing these controls later increases rework. An application may technically start but remain difficult to monitor, inaccessible to the correct users or connected through temporary network arrangements that need to be redesigned shortly after go-live.

Compatibility Problems Discovered Too Late

“It works on-premises” does not guarantee that a workload can move unchanged. Older software may contain assumptions about operating systems, drivers, network addresses, local storage or authentication that do not fit the target environment.

Microsoft’s current workload preparation guidance identifies issues including unsupported operating system versions, legacy network drivers, local file input/output dependencies, hardcoded IP addresses and hardcoded user accounts as compatibility problems that should be resolved before production deployment.

The important lesson is not that every application must become cloud-native. Compatibility needs to be verified rather than assumed. A stable legacy application may still be suitable for cloud virtual machines if its operating system, networking, storage and supporting software can operate correctly and remain supportable.

Problems should be remediated and retested before the production move. Discovering a blocker while users are waiting for cutover completion leaves the team with fewer safe options and greater pressure to accept temporary fixes.

Security and Governance Are Added After the Move

Security becomes harder to retrofit once workloads have already been deployed around weak assumptions. Identity, access control, data protection, network design, logging and incident response should therefore influence migration planning rather than becoming a cleanup project after cutover.

Microsoft’s secure cloud adoption guidance recommends integrating security considerations into every phase of cloud adoption and includes confidentiality, integrity, availability, incident preparedness and landing-zone security among the areas that require planning.

This does not mean every migration needs identical controls. Requirements depend on the workload, data, organization and applicable obligations. A public marketing site and a financial transaction system should not receive identical risk treatment simply because both are moving to cloud infrastructure.

Governance matters for the same reason. Teams need clear rules about who can provision resources, who approves access, how activity is logged, how exceptions are handled and who owns security decisions after migration.

Migration Waves Are Too Large or Poorly Sequenced

A migration wave is a group of workloads moved within the same planned period. Waves make a large migration program easier to control, but poor grouping can create new risk.

AWS recommends combining prioritization, dependency information and business drivers when building waves, and its portfolio migration guidance recommends prioritizing simpler, noncritical applications in early waves while considering security, operational and platform readiness.

Microsoft similarly recommends grouping dependent systems and using lessons from completed waves to refine later planning. Its migration-wave planning guidance also emphasizes business timing, team capacity, testing, rollback procedures and success criteria.

A common mistake is moving too many critical workloads together because a calendar deadline is approaching. That concentrates technical complexity and can exceed the capacity of migration, application, security and support teams at exactly the point where fast decisions are needed.

Waves should be revised as the organization learns. A dependency discovered during one migration may change the grouping or timing of several later workloads.

Testing Does Not Resemble Production

A test environment can produce reassuring results while still failing to represent the conditions that matter in production. Missing integrations, different identity configuration, unrealistic traffic or configuration drift can hide defects until cutover.

Microsoft’s workload-preparation guidance says test environments should contain the required dependencies, configurations and integrations because missing components can produce false positives or leave problems undetected. Its environment guidance describes configuration drift as discrepancies between environments and recommends keeping staging as close to production as practical.

Testing should cover more than whether the application opens. Functional tests confirm expected application behavior. Integration testing verifies communication with databases, identity systems and external services. Performance testing checks whether the target environment can handle realistic demand. User acceptance testing verifies important business workflows from the user’s perspective.

Microsoft’s pre-migration validation guidance specifically calls for functional, integration, regression, performance and stakeholder acceptance testing before production deployment.

For example, a migrated order-processing application might pass a basic login test but fail when it attempts to call a payment integration, create a scheduled export or process peak transaction volume.

The practical standard is not perfect duplication of production. It is enough similarity that testing exercises the dependencies, configuration and load characteristics most likely to affect production behavior.

Data Synchronization and Cutover Are Underplanned

Moving compute is only one part of migrating a stateful application. Databases, files and transaction data may continue changing while the target environment is being prepared, so teams need a defined point at which data is synchronized and production traffic switches.

AWS’s cutover guidance describes a sequence that can include an ingestion freeze, final backup, final data synchronization, routing changes, testing and validation before the migration is considered complete.

This becomes especially important when users can create new data immediately after cutover. Once transactions exist only in the new environment, rolling back to an older source environment can discard or conflict with those changes unless a reconciliation or replication method has been prepared.

DNS changes, load-balancer changes and other routing steps also need to be coordinated with application readiness. Redirecting users too early can expose an environment that has not completed data synchronization or acceptance testing. Maintaining two writable environments without an intentional synchronization design can introduce a different consistency problem.

A cloud migration cutover checklist can turn acceptance criteria, data synchronization, rollback triggers and post-cutover validation into explicit go-live controls.

The Rollback Plan Exists Only on Paper

A useful rollback plan answers two questions before cutover begins: when should the team stop? and how will service be restored?

AWS recommends defining rollback checkpoints, a strategy for handling the rollback and its data, and a named contact who decides whether to fix forward or return to the previous environment. Its cutover guidance also distinguishes rollback before new data is created from rollback after the cloud system has accepted new transactions.

That distinction matters. Before new writes occur, rollback may involve restarting the source environment and reversing routing changes. After new transactions have been recorded in the cloud environment, the source data may be stale and the team needs a way to reconcile, replicate or restore the newer data.

A practical rollback plan therefore includes the trigger, decision owner, technical procedure, data-handling method, expected restoration time and validation procedure. Microsoft also recommends documenting rollback triggers, backup and restoration procedures, recovery validation steps, and regularly testing those procedures before they are needed.

Tested backup and recovery planning supports this process, but a backup by itself is not a complete rollback strategy. Traffic routing, application state, data consistency and acceptance checks still have to be handled.

Skills and Ownership Gaps Appear During Execution

Cloud migration is not only a tooling problem. Someone must understand the application, someone must own the platform, someone must make security decisions, and someone must decide whether production acceptance criteria have been met.

Microsoft’s migration-plan template explicitly includes operating-model responsibilities, workload ownership and cloud training because teams need clear accountability before workloads move. The planning framework also recommends documenting platform and workload responsibilities rather than assigning them after deployment.

A common failure pattern is that the migration team can move the workload, but nobody is clearly responsible for monitoring it afterward. Another is that a business owner is unavailable during cutover, so technical staff cannot confirm whether an important workflow is functioning correctly.

For each migration wave, identify the workload owner, platform owner, security contact, migration lead, business acceptance owner and escalation path. Small organizations may combine several roles, but the responsibilities still need to be explicit.

The Team Declares Success at Cutover

Routing production traffic to the new environment is a milestone, not the end of the migration. Workloads need post-cutover validation under real operating conditions before the wave is considered complete.

Validation should confirm user access, important business transactions, integrations, scheduled jobs, monitoring, performance, backup behavior and error rates. The operations team also needs updated documentation and a clear support path.

AWS’s migration-planning guidance treats test, cutover, validation, wave closure, lessons learned and resolution of post-migration issues as parts of the migration-wave lifecycle rather than treating cutover as the finish line.

A stabilization period is useful because some issues appear only under real traffic or after scheduled processes run. An overnight batch job, for example, may reveal a missing file path several hours after daytime users have successfully tested the application.

How to Reduce Cloud Migration Risk Before Go-Live

Before approving production cutover, confirm that the major uncertainties identified during planning have been converted into observable readiness conditions. These checks are parallel gates rather than a substitute for a detailed cutover runbook.

No checklist can remove every migration risk. Its value is that unresolved assumptions become visible before time pressure and production impact make them harder to address.

Conclusion

Cloud migrations become safer when teams discover uncertainty early rather than trying to compensate for it during cutover. Complete workload and dependency information, realistic testing, controlled migration waves, a prepared target environment and a usable rollback strategy give teams more options when something behaves differently from the plan.

The most important shift is to treat migration as a lifecycle rather than a transfer event. Cutover is only one stage. The quality of discovery, assessment, preparation and validation around it largely determines how much unresolved risk reaches production.