To recap:
- no one locked down APIs
- you could access a wide variety of them
- no limits on them
- they were slow and unreliable
As APIs became reliable & fast, they imposed limits on them
So not sure what was lost considering it sounds like they didn’t work well and when they did work they were incredibly slow aka self imposed rate limiting
Yeah, that’s my point. It’s not like they’re dumped onto the side of the yard, when they get decommissioned they end up going into these or parts can come out of them.
People make these comments then have no problem swapping their car out every 4-5 years and it’s like what do you think happens with those eventually?
Heroic feels a bit strong, but overdue I would agree. It’s an area that’ll always exist and has been neglected by US industries outside of the company’s that are just government contractors (General Dynamic, Lockheed, etc) as the supply pool for these types of products is very small & not forcing innovations via competition as a result.
Yeah, I’ve lived the life of straddling .NET Core and ASP.NET while also dealing with React vs Angular2+ and having half of the system in the script bundling hell that was razor views and all sorts of craziness.
That experience is actually what led me to switch over to Product among other things, I get it when people joke (half joke) about considering retirement rather than going through that again.
This exact type of thing is why when I switched to the dark side (product) and sat in management meetings where often non-technical folks would go “we could measure by lines of code or similar” for productivity I often pointed out how that was a bad idea.
Did I win? Of course not, it’s hard for non-technical people to fully appreciate these things and any sort of larger infrastructure work, esp for developer productivity because it goes back to well how you going to measure that ROI.
Anyways, this was fun to read and brought back good engineering memories. I’d also like to say, as it brought back a bug I chased forever, fuck you channelfactory in c#.
Don’t worry about it, fair question and I wouldn’t waste calories on folks who can’t find it to be kind, especially with the job market as rough as it is now.
So, it’s a complex thing but the state has a vested interest in drivers being insured because of state / federal funding for roads, infrastructure and all of that.
The original intent was to stop humans from being greedy assholes and to provide a stick for when they messed up. Without the states involvement, insurance would likely go the way of used auto with “buy here pay here” lots which is a net negative for the state & society as a whole.
They want to make sure that “fair” prices are set so that there isn’t an overly disproportionate amount of people who need the insurance not having insurance. In reality, the less risky drivers do for all intents and purposes help off-set the cost of the more risky people but all of that is hidden in the premium logic.
At the end of the day, what has happened though is the state’s regulatory group overstepping their bounds (in my opinion) and ignoring good faith proposals with data showing why rate increases are needed which leads to situations we’re in now.
Having been in that world (I left it) I can honestly say there has to be some regulations or regulatory body because a lot of these folks spend so much time looking at numbers (actuarial science in general) they forget the fact there are humans behind those numbers.
I’m not sure you read my post then as it explains I’ve seen first-hand actual loss data because of supply chain & other costs leading to an unprofitable offering being denied by the state without any valid rationale other than “he didn’t see any cars outside his window”.
The point is that regulators have not been allowing rate increases with good faith justifications for years and now that they see their actions have caused companies to pull out they’re pointing the finger at the companies when it’s their poor judgment for years coming to fruition.
It is through reinsurance mechanisms and the way you build the portfolio.
If you can’t use predictive attributes, many not allowed in California, you’re not going to get reinsurance interest because you can’t really balance the risk across different risk types for drivers.
So the end result is the customer pays more, despite their driving record being clean, because that’s the only way to manage through the risk.
As APIs became reliable & fast, they imposed limits on them
So not sure what was lost considering it sounds like they didn’t work well and when they did work they were incredibly slow aka self imposed rate limiting