:wave: Hi everyone, I’d like to get your feedback...
# general
w
👋 Hi everyone, I’d like to get your feedback on a new PR comment design that includes a better way to show costs related to usage-based resources. Please see this mock PR comment (for reference here’s the current PR comment). Questions: 1. Do Fixed and Variable costs make sense? or do “provisioned costs” and “usage costs” make more sense? 2. We’re thinking of removing the “New monthly cost” as it seems confusing to combine fixed and variable costs into one figure - what do you think? 3. In the summary table, variable costs would show when usage-based resources such as S3 buckets are added or removed. However, when things like lifecycle policies are changed, we could detect and indicate whether costs may increase/decrease. How useful do you think these things to engineers? (we can’t know the $ amount of the change yet, that’ll come in the future). 4. Any other feedback? If you have 15mins this/next week, please DM me as I’d also love to jump on a Zoom call to chat about the above.
c
1. I think both make sense however I think usage is more descriptive than variable. 2. I personally find the total cost valuable though I see your point wrt it maybe being confusing. Maybe it would be good to include new total cost near the top as like a summary alongside the Cost Checks? Monthly fixed costs will decrease by $1,393 and variable costs will decrease by $300. New Total Cost: $8,930 3. I’m not sure how I feel about it. Do you have any mockups of what that might look like? 4. New comment looks pretty clean 😄
w
Thanks @colossal-television-87079! Do like option 3 in this PR more? Regarding your qustion #3, the above options show “This pull request also has” list that describes the sorts of things it would flag.
p
it seems confusing to combine fixed and variable costs into one figure
Absolutely agree 💯
Variable costs, by definition, cannot be guaranteed to be correct at the point you evaluate them in the PR pipeline so the word
estimated
needs to be super obvious in any message.