if you double click the coreml file in a mac and open xcode there is a profiler you can run. the profiler will show you the operations it's using and what the bit depth is.
Why shouldn't I get my cut, then? Why do they get to double dip? The point of the dash cam is that the data is ephemeral unless it's actually needed because something exceptional happened.
So you pay $20/month to be able to earn some crypto-coins they generate out of thin air to be used for...
If they aren't paying the equivalent of whatever the government allows you to deduct for 'wear and tear' on your vehicle then you're basically just subsidizing their data collection.
I don't even have an opinion on this, you do you.
--edit--
Oh, I saw down thread they're primarily a fleet services company and that explains a bunch. $20/month per car probably makes sense if you're outfitting an entire fleet and integrate it with your wonky in-house drivers' app which is barely fit for purpose. Yeah, I'm not bitter...
All I really have an issue with is the claim you get compensated for the time and energy you, essentially, donate to the company. If that's what you want to do with your time then by all means...
It just seems like a weird business model to me, they sell a pimped-out dash cam (fair enough) and pay some tokens (or rely on your philosophical bent) so you're willing to turn over all your data so they can repackage and sell it. To give credit where credit is due, they seem to be completely transparent with this and if the people who participate don't care then why should I?
stalin's pictures were photoshopped when he was in power, he was actually quite ugly. napoleon similarly was ugly looking but had himself painted as a chad after he betrayed the revolution
Big companies tend to have Staff/Principal/Distinguished type roles. Usually those roles give you a lot of independence. But that independence means you need to be able to find projects to do and advocate for them and get them staffed and planned and executed and out to production. Often those projects can span many teams and multiple organizations, depending on how the company is structured. So I suppose the most valuable skill is being able to earn the trust of the managers so that you're able to even get them to listen to you so your stuff ends up on their roadmap.
so i do sympathize with a lot of the negative sentiments about the role here in this thread, and i think that in general there is a lot of navel gazing about the staff+ tech ic roles, there is an actual place for them as tech leads of large projects.
Even for professional developers I am not buying this argument. I think there is an argument to be made that we actually don't know how to work with these tools effectively and repeatably yet. But as the tools improve and we figure out the processes more that may change. It might not too, but I am leaning more toward it working better when we figure out how to use it than not.
e: Not a q for parent, but maybe for others. Are we supposed to be making a distinction between "vibe coding" and "coding with an AI agent"? What is the difference?
According to Wikipedia, vibe coding is "fully giving in to the vibes, embracing exponentials, and forgetting that the code even exists" and "If an LLM wrote every line of your code, but you've reviewed, tested, and understood it all, that's not vibe coding in my book—that's using an LLM as a typing assistant"