Migration testing verses Code Testing

By
What it means to change produciton server location. New hardware same applications what should be updated. What applications get cut over first.

New hardware....

Same code base...

Sync content w/ test and prod

The cut over to a new data center

Comments

Post a Comment

Popular posts from this blog

By
Acts of Defiance: Hacking Spelling Tests, Grey-Box Bullpens, and Unlatching Staging Gates For over twenty years, my professional world has been governed by rigid gates. Code blocks wait in staging pipelines, automation frameworks run validation suites, and as technology leaders, we evaluate systems to answer one fundamental question: Is this build safe to release to production? If it isn't, the traditional corporate mechanism dictates a rollback. In a modern, mature DevOps ecosystem, a rollback is tactical, data-driven, and blameless. You isolate the anomalous telemetry curve, revert to the last known stable configuration, and adjust the sprint. But long before I ever managed global engineering architectures or negotiated delivery pipelines, I lived through a rollback that wasn’t agile at all. It was purely Waterfall. And it left behind a massive wave of cognitive technical debt. When I was a kid, my family relocated to Big Bear Lake, and the school system made a top-down, monolith...
Read more

Decoding Silent Signals: Inclusion Without Shame in Engineering Leadership

By
In the early architecture of software delivery, the tech industry valued a rigid, monolithic ideal of executive performance: the manager or engineer who sat motionless, commanded the room through unwavering direct eye contact, and delivered razor-sharp status updates without a flicker of hesitation. For a leader trained in systems, however, real-world team dynamics quickly expose the flaws in that mental model. Human interfaces do not run on a single, standardized driver. True organizational resilience requires realizing that non-standard behavioral patterns—a team member who constantly fidgets during an architecture review, or an engineer who stares intently at the floor while walking through a critical deployment script—are not indicators of a lack of confidence, engagement, or competence. More often than not, those physical behaviors are vital processing mechanisms. They represent an individual actively managing sensory input, hyper-focusing on complex logic, or navigating their own...
Read more