Sounds like both a lack of trust and communication between you and the team.
> If you have better metrics or management skills than what everyone in the world has figured out, myself and many others would gladly adopt these approaches.
Oh boy...
edit: One issue might be they fear that bad news will lead to a knee jerk reaction that gets them or their teammates fired. They should feel comfortable to encounter problems and openly discuss them in the open with out fear of repercussions. In fact, I would argue this is one of the major advantages of a team; pooling collective knowledge and abilities. If people fear honest communication then the performance of the team is impacted. The manager has the greatest ability to fix this, IMHO...
Call your credit card company. They can block a merchant, perform a chargeback, and/or issue a new credit card number. I don’t know the rules for a debit card, but you’ll at least be able to get a new debit card number.
FWIW, actually, one thing I learned in practice that’s wasn’t highlighted in my Algorithms course: overhead (constant C) matters. You can feel good about yourself for choosing an algorithm that scales in O(lg n) time, but if your you ignore the cost of each operation (C) you might be slow.
For example:
1. When n is small, an array is almost always better. Arrays have very little overhead compared to even a hash map.
2. Algorithms with the same O() may still have significant differences at runtime and might be balanced differently between insert and search times. AVL trees take longer than Red Black trees to insert, but might be 1 level better in height. That means one less access. Useful for a routing table, for example.
So, in summary, if your looking at other people’s code and see lots of arrays don’t get too smug…n is usually small.
I've removed one and never heard anything. I doubt they even check if it's functioning unless they are attempting to repossess the car. As I recall, some modules have the ability to unlock and start the car as well (I think; it was years ago when I found one and researched it...)
We leased a new Jeep Cherokee from a Miami dealership some time ago. It was a company car and was financed. Some months later we noticed the odometer was blinking constantly so we took it in for service to a different dealer. The tech pulled it out and told us about it. He said they didn't do it at that dealership, but some do it.
It was just hanging off the OBD2 port, so if you're concerned about it when leasing or buying a new car then just make sure to check that port.
I still have it in a box somewhere. I'm not sure if there's anything interesting that can be done with it...