brogrammernot

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?

The cognitive dissonance that happens with tech workers believing their own work isn’t some form of blood money in the end is comical.

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.

Please post a source of the “unused tanks and planes” dumped in the desert.

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.

Good luck, you got this.

“Commenters: please don't reply to job posts to complain about something. It's off topic here.”

“Commenters: please don't reply to job posts to complain about something. It's off topic here.”

They can and will. California will go after you for them. Happened to a friend who had documented 7 months in another state.

Yup, I hated reviewing California based book of business.

Everyone is upset their rate is going up but the issue is lack of ability to use predictive underwriting because of what you said and more.

This is always a fun topic for me.

If everybody is sharing all the risk that’s the same thing (obviously I’m being simplistic) as them underwriting the risk themselves.

Yeah but that’s compounded by access to the information & who do you trust.

Also human nature is to look at the odds and not believe you’re going to be that 1 in 125,000 :)

Yes but less so on the rates themselves & rather do you have enough cash to stay alive without going under.

They’re obviously related but less regulatory focus on rates, more on cost of business and that.

Edit: Basically you can run at a loss (most do) for a limited period of time but have to show that you will be liquid on the other side of the losses.