this post was submitted on 30 Jul 2023
369 points (96.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54716 readers
320 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Okay, I would say my argument probably breaks down at small individual projects. For larger corporations though I think it's still stands true. Anyone who's worked in JIRA is probably familiar with the status "Won't Fix". For essentially any bug incoming you would weigh the user impact versus the revenue impact. You prioritize based on severity but also prioritize based on revenue. Your Sprint cycles by very nature can't be oriented to producing the best possible product if the best possible product is only what makes you the most money.
EDIT: I would also say that this largely depends on how you define what a good product is. Is a good product one that makes you a lot of money? Is a good product one that is high functioning and provides good use?