this post was submitted on 06 Feb 2025
812 points (100.0% liked)

Programmer Humor

20383 readers
1939 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
812
That shadowy place (lemmy.dbzer0.com)
submitted 1 day ago by [email protected] to c/[email protected]
30 comments fedilink hide all child comments
 
top 30 comments
sorted by: hot top controversial new old
[–] [email protected] 101 points 1 day ago (3 children)

I had this one user who kept using an old report. It used a terribly provisioned db account and had to be changed.

We created a v2 that was at feature parity to v1 and told users to move off of v1. Slowly but surely it happened.

Except one user.

We put up nag screens. Delays on data return, everything we could go "carrot" them to the new version but they stuck with it.

Eventually I called the guy and just asked him, "Why are you still using the old version?"

His answer, "no one ever told me about the new version."

I asked him if he got our email. He said no. I forwarded it to him.

"Oh."

I asked him didn't you read the nag screens? He said no.

I asked him, "The page doesn't allow you to move on until you wait 90 seconds. Why didn't you read it?"

"I didn't think it was important."

I learned an important lesson that day: never wait for all users to move. Once you have enough, start doing scream tests.

[–] [email protected] 61 points 1 day ago (2 children)

Bastard user from hell

[–] [email protected] 25 points 22 hours ago

Bastard user from hell

Every IT/software group needs to have one, otherwise you get complacent.

[–] [email protected] 11 points 22 hours ago

If some guy just minding his own business is your "user from hell" I am truly envious of your job

[–] [email protected] 18 points 1 day ago (1 children)

I used to work for a university trying to modernize how people got student and financial data. Over half my work was playing politics rooting out people who refused to change and going above their head. We had one guy who didn't want to update a script on his end to include the bare minimum amount of 'security': a hard coded plain text password. It took me months and I had to go to his office to update his script and he complained about it the entire four minutes it took

[–] [email protected] 14 points 1 day ago

Email to all:

“Due to budget constraints, resources will shift from $oldThingy to $newThingy. As a result, $oldThingy’s availability can no longer be maintained at the previous level.”

Then randomly kill oldThingy for more and more hours each day.

[–] [email protected] 12 points 1 day ago (1 children) 
location /old_api {
  redirect /new_api
}

(can’t be bothered to check the syntax).

[–] [email protected] 10 points 1 day ago (2 children)

If you have a major version change, it means that old API calls will break against the new API, assuming they are accurately following semver.

[–] [email protected] 8 points 1 day ago

You’re absolutely right. In my mind “feature parity” got garbled into “backwards compatibility”.

[–] [email protected] 1 points 22 hours ago (1 children)

A translation layer could be used, no? Check api version, translate any v1 specific calls into their v2 counterparts, then submit the v2 request?

[–] [email protected] 1 points 20 hours ago

This isn't really efficient because when v2 gets updated now you have to update the translation layer as well.

Any improvements you made in v2 would likely not translate.

Essentially the best way is to provide users with an incentive to switch. Perhaps a new feature or more requests.

[–] [email protected] 21 points 1 day ago

“The other 98% of the codebase.”

[–] [email protected] 50 points 1 day ago

This reminds me of QEMU internals. Virtual hardware support is paramount in an emulator, so nobody wants to break old code that was probably written by an expert who knew that piece of hardware better than you ever will.

[–] [email protected] 22 points 1 day ago (2 children)

I remember my engineer being such a hardass on using v2 of our API and when I went to implement a feature, v2 didn't even have ANY of the endpoints I needed

[–] [email protected] 23 points 1 day ago (3 children)

I don't get why anyone would publish v2 when it not really on feature-parity. Do companies really start releasing v2 endpoints slowly?

[–] [email protected] 31 points 1 day ago

it's called the strangler pattern, where the new version is layered on top of the old and gradually replaces it.

it usually doesn't work.

[–] [email protected] 4 points 1 day ago (1 children)

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.

[–] [email protected] 3 points 23 hours ago* (last edited 23 hours ago)

This is how we have 3 different APIs that sometimes do the same thing, but most times are incomplete when compared to the original v1, who in the meantime wasn't properly maintained because we were "migrating" and now you have to use bits and pieces of the 3 of them to do anything.

It's a nightmare. Can't wait for the next genius to come along and start a v4, that will never be completed and will only re-implement parts of the old APIs while implementing all the new features

[–] [email protected] 5 points 1 day ago

I suspect that starting your own version of the API is the Software Designer / Software Architect version of Programmers' "I know best so I'm going to do my part of the code my way which is different from everybody else's".

Mind you, at the very least good Software Architects should know best, but sometimes people get the title without having the chops for it.

[–] [email protected] 3 points 1 day ago (1 children)

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

[–] [email protected] 0 points 1 day ago (1 children)

v4???? At that point I'm just gonna guess the data

[–] [email protected] 1 points 1 day ago

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.

[–] [email protected] 14 points 1 day ago* (last edited 1 day ago) (1 children)

We've got 10 APIs, with a fraction of a percent of code coverage. None of the responses/requests/error messages/fetch services are standardized.

So unsurprisingly this project has been going on for 6 years.

[–] [email protected] 3 points 1 day ago (1 children)

Cheezus Crust!

[–] [email protected] 10 points 1 day ago* (last edited 1 day ago) (1 children)

It gets worse. Half the site is MVC, half is blazor. We depend on mainframe connections and external vendors, who in turn have their own API, which we have a wrapper API for.

The entire grahql fusion schema got nuked about two months ago, and we're still panicking to fix it.

And each of our environments are half environments, that mesh with one another to create a data integrity hellscape.

It's ~~turtles~~ rot all the way down.

[–] [email protected] 5 points 1 day ago (1 children)

who in turn have their own API, which we have a wrapper API for.

Oh noooo!

[–] [email protected] 4 points 1 day ago

That one is by far the worst to work with.

[–] [email protected] 9 points 1 day ago

I've seen this often. The app is marketed as being "api" first as if that's some benefit to the user of a SaaS application. However in reality much of the team is constantly busy patching the old legacy V1 api to keep it running. And management won't authorize the budget to create a new api version that replaces the old one, because it still works right?

Public facing web apis have always been a pet peeve of mine. So often the team uses the api their own frontend uses as the public facing api customers should use for integrations. Which on the surface seems smart, why implement and manage two apis that's just overhead. But in reality the apis suitable for a frontend (or often that specific frontend) isn't suitable for integrations at all. They both have a completely different target user and completely different requirements.

But hey we'll just market it as "headless", because one could totally put in the years of work and money we put in to create our front-end, if they really wanted to. Totally realistic thing that happens.

[–] [email protected] 13 points 1 day ago (1 children)

And by api v1 you meant stored proc, right ? 😝

[–] [email protected] 4 points 1 day ago

This thread is giving me so much anxiety. I can’t read any more of these comments.