- First Name
- Joe
- Joined
- Jun 28, 2023
- Threads
- 18
- Messages
- 247
- Reaction score
- 321
- Location
- UPSTATE NY
- Vehicle(s)
- 2022 Maverick ECO, FX4, 4K, 2023 Bronco Sport, 2024 Escape Red Line
- Engine
- 2.0L EcoBoost
I have a feeling the engineers each specialize in their own "pocket" of the code. Sometimes a small simple change in one pocket has a negative effect on an area of the code you wouldn't expect. That means the final code must be fully tested with every variance in mind. Where I work we call it regression testing and it's extensive to the fullest extent of the definition "extensive". Any change anywhere in the code triggers one of these tests to ensure the final release is deemed stable.And you truly think that we bought a Maverick hybrid to have to go through the approximately 1,239 steps you just listed to have a vehicle we can trust that it isn't killing another battery?
I have a much better idea.
How about Ford releasing the permanent fix for the Maverick that they announced and promised one year ago they would have the fix to prevent deep sleep out by the end of quarter one of 2025, and later moved that date to the end of quarter two?
This isn't rocket science. A major auto manufacturer should be able to engineer a solution to this problem, if they have competent engineers.
I'll leave it at that.
Consider the variables in the options you can order when you buy a vehicle. That's why they offer technology "packages" (to trim down the variables), EV or ECO, 4K, FX4, ect. Each has it's own needs from a software standpoint.
No, I don't work for an automaker. But I would think the testing protocol is the same. And it takes time to cover all the bases.
Sponsored