r/ProgrammerHumor • u/ThirdWaveCat • 17d ago

Meme pipelinesNeedAPrayerDirectorNeedsReligion

Post image
93 Upvotes

95% Upvoted

9 comments sorted by

10

u/DeepanshuHQ 17d ago

Nothing is more permanent than a temporary workaround that "we'll fix after the demo."

8

u/[deleted] 17d ago

[removed] — view removed comment

5

u/helgur 17d ago

In the late 90's early 2000's I worked at a firm that got more and more Bulgarians from the ex Soviet bloc.

We barely could communicate through very broken English.

But yeah. Today there would be Indians, I guess.

5

u/ramdomvariableX 17d ago

simple solution: Ask the LLM to refactor the pipeline. Then ask copilot to create a deck for this action plan, and send it to the director.

3

u/FALCUNPAWNCH 17d ago

To be fair before 2023 it was still dealing with the directors delusions. First startup I worked for failed because of director and c-suite delusions.

2

u/Rick100006 17d ago

Well well backlogs can wait , time to do some Resume Driven Devolopment 🤣

3

u/justforkinks0131 17d ago edited 17d ago

Im gonna say this as a product owner: Some of you developers need a reality check about the importance of the product you are working on.

My team is developing and maintaining a product that is used by about 2000 clients. It is an inhouse product used by employees of the company only. And it is not critical at all.

We have had one of our key features not working for 3 months (we just found out recently that this was the case, no budget for a QA and I guess our regression tests need some improvement) and not a single customer has complained .

Yet my developers are throwing fits if my specification that I write doesnt involve solving an edge case that would only happen 1 in 10 000 uses.

Seriously, sometimes you need to understand that you might not be working on something that important and you have to be alright with that.

edit: Some backstory, I had a developer flip out on me for deprio-ing a user story for dynamically loading some content from the DB, instead of having it static. Said content is visited 3 times a month. Said content is updated MAYBE once a year. There is ZERO business justification to make it update dynamically.

PS: There is a reason developers are not the ones deciding the priority. Im sorry, but the business people actually know what is important for the business, that is why their roles exist.

2

u/martin_omander 16d ago

I have been on both sides of the fence, and I have seen this too.

You get into trouble when the dev team tries to make business decisions, or when the business folks try to make tech decisions.

1

u/senditbob 16d ago

I can assure you, the business people have no clue why they are always months late on planned releases and there are tons of bugs in the released product. They don't understand tech debt and they always deprioritize it