|
|
|
|
|
by mgsouth
1436 days ago
|
|
Sorry, no. From a technical standpoint it's ridiculous. If there's even a minimal amount of error checking, a failed update would be akin to a shotgun blast, not a laser beam. Is it theoretically possible for it to cause just one highly specific problem? Yeah, but extremely unlikely. And its only "an easy check" _for the supporting engineer_. For the customer it's very inconvenient, and is very transparently just busywork to make the customer go away for a while. Speaking from my own management experience, it's OK for me not to understand a technical issue as well as the person I've made responsible for a task. But you have to have complete trust in their judgement and "communication accuracy." Free advice--take a good hard look at what else you've been told. I'm not saying someone is deliberately lying, but pressure and skill shortcomings can lead to untrue statements. You might also take a good hard look at what you've said and done. You get lots of points for directly speaking with customers in this forum. But it doesn't sound as if the technical side is your wheelhouse (which is OK, that's not what your job is), and you may be having "hair on fire" issues. That can very easily lead to making decisions and demands which are impossible for your team to fulfill, or lead them to making risky technical choices. A startup "failure is not an option" or "go big or go home" or "YOLO" mentality can easily go overboard can make it impossible for them communicate the true situtation to you _or even to themselves_. |
|