metric10

Oh wow, $GLAB is down 31.68% YTD and they are announcing a massive restructuring and work force reduction. Is this th en---oh wait, AI!!!

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...

[edit: minor grammar]

Presumably the City of Los Angles isn't confronting the problem due to an unwillingness to spend funds. If she is successful, the cost of doing nothing will increase. So her goal isn't to throw them out, it's to force the city's hand.

Yes. Back of envelope, took physics in college many years ago[1] analysis:

E=mc^2, or energy = mass * (speed of light)^2. According to Wikipedia a candle can produce 77 watts of energy "combined." I guess that means 77 joules (1 watt = 1 J/s). So we have:

77 = m * (299792458)^2

Solving for m via Wolfram Alpha:

m = 11 / 12839369696240252

Which is in grams. That's a _very_ small amount, but it's not zero.

edit:

[1] If I'm being honest, I got E=mc^2 from watching the Twilight Zone as a kid, not college physics.

While both RB and AVL trees grow at O(lg N) height, the constant for AVL trees is smaller. This means that for a large AVL tree it might be 1 or 2 layers shorter than the equivalent RB tree. This comes at the expense of a higher constant for insertion and deletion.

In certain contexts saving a node transversal will have a meaningful impact on performance.

From a security stand point you should at least have uBlock Origin installed for Chrome and Firefox. It can block JavaScript easily. I would trust NoScript as well which provides fine grain control over scripts. I get not wanting any extensions, but blocking scripts will unfortunately never be viable in a user base that doesn’t know what a “script” is...

Yeah, but in this instance we’re talking about Facebook. I could care less about what Apple charges them. I do feel for indie developers and don’t support the 30% fee, but in the case of $FB (or zoom) allow me to introduce you to the world’s tiniest violin...

Also, I’m sure FB is only piling on because of the privacy changes to iOS which harm FB’s core advertising business. FB would charge 30% in a heart beat.

Again, I would do away with the 30% fee, but please find me someone other than Facebook to feel sorry for.

I wish insurers weren't so heavy handed with this technology. If it's possible to tell if someone is a "good" or "bad" driver via this technology, why not at least just tell the driver without the big brother BS? Many drivers might change their habits based on this information.

I know insurers have apps that you can install on your phone or ODBC modules you can install. Does anyone know of any way to collect this data privately without reporting it to an insurer?