stankmut

I had to do this to get the factory oil filter off my motorcycle. Went through 3 different oil filter removal tools and all I achieved was rounding off all the edges of the filter.

Retailers do it because they pay a penalty when a chargeback happens and payment processors will cut ties with them if their fraud rate is too high.

The hospital has a method it can use if it wants to avoid losing access to federal funding without having to violate state law by pulling gender-affirming care. It can file a lawsuit in federal court and ask for a restraining order on enforcement of the executive order. That's the decision to make if the entire community's interest was in mind.

If the APIs are meant for public consumption, requiring feature parity makes a lot of sense. But when it's for internal use by your own developers, waiting means you are making a bunch of new API endpoints no one will ever use. People will write more and more code using the older endpoints and those endpoints will start getting changes that your new ones will need ported over.

I think if you are going to force people to use new endpoints, you'll need them to either write the endpoints themselves or have a team member who can write it for them and account for this while planning. If getting a new endpoint requires putting in a JIRA ticket with a separate backend team, 4 planning meetings, and a month wait, people are just going to stick with what currently exists.

It was basically the same thing. In the code base, there was only v3 and v4. I never bothered to check what happened to v1 and v2, but I suspect they were used in an older, archived code base.

He's running both the hospital and the insurance company. And it's apparently good quality insurance, so they aren't skimping on his treatment. There's no way both the hospital and the insurance company can be profiting from this guy getting all the bones in his body broken. Not at the same time.

Job posting requirements are done by a game of telephone where each person down the line is less technical than the previous.

A manager is able to hire a mid-level engineer, which their company defines as 4+ years of experience. An engineer tells the manager what technologies they use, bringing up fastAPI at some point. The manager then gives this list to someone who writes up the job posting who just puts 'requires 4+ years' on every bullet.

Nearly every job posting that asks for more experience than is possible or for something weirdly specific happens this way.

In my experience, having to write new v2 (or in my case v4) endpoints for most new features was expected.

Imogene is the name of someone in the article.

The 21 year old is a separate person.

I have my Final Fantasy X still, even used it when I played the remastered version recently. It didn't ask me to use the website for anything. I thought it was the Final Fantasy IX guide that required you to use PlayOnline for the actual solutions.

In the US, people consider any public sector job to be working in/for the government. Judges, Legislators, the president, TSA security, Park Rangers, Cops, Clerks at the driver's license office, etc. would all be considered government roles. Sometimes you need to clarify if you mean federal government or state government.

The president, his staff, and his political appointees are called the administration.