As a senior dev I can confidently tell you that isn’t a bug. The code was written to do it that way, and the code is right, so it must be right. Maybe there is a bug in what you think it should do.
It sounds like a joke but as another senior dev, one of the big lessons I’ve learned is getting really good at capturing all the requests that come in and who approved them.
It’s a bit of cya, but mostly so I can say “I can change that but it’s not a bug. It’s what was requested for this to do last year. Here’s the discussion” It’s surprising how often that results in “Oh yeah, that was for x. Let’s not touch it.” Or “oh that’s not a quick fix, let me come back with more information” etc
In my own workplace, it’s sometimes resulted in massive rabbithole searches along the lines of “this doesn’t seem right. Why would this even be designed this way if it wasn’t intentional?” Which then becomes asking even more senior devs who had been there for decades to scour decades old emails and/or hitting up another decades senior dev who’s now on another project on the other side of the country to check their emails until we eventually figure out why it was, in fact, intentional.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
As a senior dev I can confidently tell you that isn’t a bug. The code was written to do it that way, and the code is right, so it must be right. Maybe there is a bug in what you think it should do.
The only difference between bugs and features is documentation.
But there is no documentation
It sounds like a joke but as another senior dev, one of the big lessons I’ve learned is getting really good at capturing all the requests that come in and who approved them.
It’s a bit of cya, but mostly so I can say “I can change that but it’s not a bug. It’s what was requested for this to do last year. Here’s the discussion” It’s surprising how often that results in “Oh yeah, that was for x. Let’s not touch it.” Or “oh that’s not a quick fix, let me come back with more information” etc
In my own workplace, it’s sometimes resulted in massive rabbithole searches along the lines of “this doesn’t seem right. Why would this even be designed this way if it wasn’t intentional?” Which then becomes asking even more senior devs who had been there for decades to scour decades old emails and/or hitting up another decades senior dev who’s now on another project on the other side of the country to check their emails until we eventually figure out why it was, in fact, intentional.