Today construction crews are installing a traffic light at an intersection nearby. Just three short months ago, my car was totaled in that same intersection when another driver blasted straight through the four-way stop. I’m grateful there were no major injuries, but I loved my car. And I miss my car.
There were city rumors of improving that intersection for years. Of course I can’t help but wonder, is the traffic light going up now because of the wreck? If so, how unlucky that mine was the final straw. If not, then the light was already scheduled to be installed now, and yet still unlucky that it wasn’t up sooner and crash avoided.
Granted, I know accidents can happen at traffic lights just as easily as four-way stops or anywhere else on the road. But the exact accident that totaled my car would surely have been avoided if there was a giant traffic light directing rights of way that day.
So, watching the new light get installed got me thinking. How often do legacy IT systems feel a bit like waiting for the inevitable major collision? When managing systems feels more like bandaging systems, it’s probably time to give your migration/upgrade the green light (pun intended).
Why do you have to wait for the server to crash or experience extended periods of production downtime before you commit to upgrading and/or migrating systems onto newer, more stable environments? You want your tired system to step down when you are ready to make the change, not the other way around.
You know the upgrade is necessary, but perhaps you want to squeeze the project into the next quarter or next year’s budget. Perhaps you don’t want to take resources away from other critical projects. Maybe you aren’t certain that in-house talent will deliver a new system that is fully optimized, scalable and adheres to industry best practices.
But delaying your inevitable upgrade might cost more than you think.
Take it from the victim of a major collision, do not hesitate or delay an anticipated upgrade. Who will be the victim when your aging system fails? Customers? Employees? Management? Ultimately what will be the cost of that failure? In order to remain competitive, the hard costs to physically design, architect, develop and implement the new technology are coming no matter what. But the soft costs of low customer satisfaction, declining employee morale, and not meeting management expectations can be minimized or avoided completely when you invest swiftly and correctly. By contracting experts with a proven track record for similar projects and implementations, such as Fairway Technologies’ professionals, you can realize your goals sooner and avoid nasty collisions before they happen.
Leave a comment
- iOS Unit Testing With OCMock
- Why Stakeholders Need To Be Involved In Scrum
- NuGet Config File Transformation Causes Duplicate Entries On Update
- Load Testing with Locust on Windows
- Writing A Custom LINQ Provider With Re-linq
- AutoMapper Profile Organization
- Rails 3.2: A Nested-Form Demo Part 4: Switch to Targeting Computer!
- SharpRepository: Configuration
- Rails 3.2: A Nested-Form Demo, Part 3: We’re Starting Our Attack Run!
- Rails 3.2: A Nested-Form Demo, Part 2: Accelerate to Attack Speed!
- Rails 3.2: A Nested-Form Demo, Part 1: All Wings Report In!
- iOS Behind the Curve
- Distributed Transaction Coordinators, Port 135, and Firewalls – Oh My!
- SharpRepository: Getting Started
- Find Performance Problems Using JMeter, MySQL and Xdebug/Webgrind
- Taming Hot Key Context Shifting When Running A Windows VM In Virtualbox On OSX
- Integrating Twitter’s Bootstrap Into Your Project
- Mobile payments, tags and more using NFC
- Stress Pig
- Dear Client Services, What Works?
- What Would Steve Do?
- Still Using Fiddler to Test & Debug Your REST Services?
- Write-through and Generational Caching Make a Great Team
- Thinking Recursively
- Development Incentives, What’s the Payoff?
- How do you like them Apples?
- “Optional” Software Development Practices Series — Code Review
- Adding Images to Select Lists in MVC3
- “Optional” Software Development Practices Series
- You Get What You Pay For…
- Outsourcing Safety Tips
- Facebook IPO
- The Ballad of Tim Toady
- The Little Schemer
- Newsflash: Mom leaves tech job at 5p.m.
- I <negative_emotion> Windows 8!
- Prefix vs. Postfix Increment and Decrement Operators in C++
- Corporate videos: viral boon or epic fail?
- Recruitin’ Time!
- Reference vs. pointer parameters in C++
- The IE8 "hover" Bug: The Most Awesome IE Bug Ever?
- When is perfect perfect enough?
- SOPA/PIPA: Anti-Censorship Protest or Techies Revenge?
- A Decade of Fairway
- Handling Session Timeout Gracefully
- Generating Software Diagrams
- The Audacity of Nope
- The Origins of Culture
- Scrum Overview in Prezi – not another boring slideshow
- Numbers don’t lie: LinkedIn Statistics
- What is your favorite software development tool?
- Best Practices for Selecting Onshore, Nearshore or Offshore Information Technology Outsourcing (ITO) Providers
- Sign of the Times
- Advantages and Risks of Offshoring, Nearshoring or Onshoring
- Does Outsourcing Mean Offshoring?
- Too little, too late?
- New Favorite Lunch Spot
- Why should I care about functions as first-class citizens?
- PHP Remote Debugging with XDebug and NetBeans
- Installing SubText with Web PI
- ROI Primer
- Learn Domain-Driven Design
- Learn Behavior-Driven Development
- Mario Kart Tournament
- F# in 90 Seconds
- Website Vulnerabilities
- Scrum Overview
- Language Club
- Top 12 Favorite Podcasts Ever…
- Fairway Dart Tournament
- Learn Lean Software Development and Kanban Systems
- Android – Eclipse Quick Start
- Learn Functional Programming
- Backup & Restore Strategy
- Smartphone Screens – Another Wireless Variable
- Wireless Application Market
- Head First AOP