stankmut

It’s a common thing in programming. There’s some legacy code that isn’t being used and yet removing it causes things to break. Nobody has the time to figure out what is still referencing that code, so it just gets a comment next to it saying “Not used, but removing it breaks the build” and then forgotten about.

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.

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

Why would he turn away from the crowd and do the motion again if he was trying to show his heart going out to the crowd?

You would have to be an enormous idiot to believe in that excuse.

My first job I spent 3 years working on a variety of projects that never shipped. It was frustrating at the time, but the experience was good for me. Now I have fun writing code and working with my teammates and if my code doesn’t ship, well it’s not as bad as not having anything ship for 3 years.

You can’t just ignore the second part of that sentence which gives the right to make commits to all citizens of earth. That would include the person who wrote the last commit.

Newer generations have decoders/encoders for more codecs. 8th gen Intel Core cpus have good HEVC support while you need the more recent gens for good AV1 support.

Tinder isn’t verifying it. It’s just a joke.

Most elevators I’ve seen in the US have a minimum time for the doors to be open. Hitting the closed button won’t do anything, unless you had hit the open door button to keep them open past that time. So if you hit the open door button right before the doors closed to let someone in and they tell you they are actually going down, you can hit the close button and it’ll immediately close.

That’s not how tax write offs work. The only way to claim that money in a write-off would be for the business to also claim it as revenue. That would even out, with no tax savings. Businesses also don’t handle donations that way, they usually serve as a collection agent that just passes your donations on without being able to claim it towards their revenue or their tax write offs. The only person who can write-off their donation is the person who actually made it.

The reason businesses do it is for marketing. They get to put out a press release saying “They helped donate $10 million to puppies without borders.”