• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle

  • He is correct that the forces are different. The equation for centripetal force is Fc = Mv2/R.

    Radius is the distance from the focal point, and each seat will be different distances.

    So he is technically correct that seat position could be calculated in perfect conditions with accurate measurements.

    But none of the data that reaches this service will be remotely accurate or complete enough to make that determination. It will only have one passengers phone data, and even if it collected everyones phone data, phone sensors have a margin of error well above what the difference would be. GPS data is only even marginally accurate up to something like 6ft, and really not even then. Then cars have a lot of other factors like suspension and compression in seats, etc, that would absorb enough of the forces to muddy the data even if accurate sensors were everywhere.

    Tl;dr; another cocky person that took a few physics courses but walked away with a poor understanding of real world applications talking out their ass.








  • I find the “clean history” argument so flawed.

    Sure, if you’re they type to micro commit, you can squash your branch and clean it up before merging. We don’t need a dozen “fixed tests” commits for context.

    But in practice, I have seen multiple teams with the policy of squash merging every branch with 0 exceptions. Even going so far as squash merging development branches to master, which then lumps 20 different changes into a single commit. Sure, you can always be a git archeologist, check out specific revisions, see the original commits, and dig down the history over and over, to get the original context of the specific change you’re looking into. But that’s way fucking more overhead than just looking at an unmanipulated history and seeing the parallel work going on, and get a clue on context at a glance at the network graph.





  • Wrench@lemmy.worldtoMildly Infuriating@lemmy.worldstupid smart TVs
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    8 months ago

    My wife’s car disconnects my bt audio like every 5 mins. There are certain intersections where it always connects. I’ve long suspected its because of other bt devices using the same frequencies. This is on a 2023 ev car using android auto.

    My shitty aftermarket bt radio I installed on my 2003 PoS is 100% stable. No problems.





  • That’s fair. As a developer that has been burned by Google dropping support for shit they created, I can’t say for certain it was malicious or just Google being Google.

    They used to create a ton of tools and protocols and drop support a couple years later because it wasn’t worth it to them to maintain it. Lots of pet projects used to get promotions, but no budget for sustained support.

    A big client onboarding and exposing major flaws could absolutely shine and unwelcome light and force them to take a critical eye and come to the conclusion of “yeah, everyone that worked on that has moved on, it’d take too many resources to revive it, and it’s just going to help our competitor anyway. Our business need for it is gone because does similar things. Cut the cord”

    It sucks, and isn’t an excuse. I stopped using Google dev tools because of it long ago. Very unreliable. But I don’t think it’s the same intent as Apple by a long shot.