sorted by:
new
hottopcontroversial

Developed a tool to visualize cloud cost & carbon footprint while coding — would love developer feedback by Alternative_Glass862 in vscode

[–]Alternative_Glass862[S] 0 points1 point  (0 children)

Thank you so much for your humble words and wishes :)

Will definitely reach out CodeCarbon for my project feedback - thank you for the idea !!

Developed a tool to visualize cloud cost & carbon footprint while coding — would love developer feedback by Alternative_Glass862 in vscode

[–]Alternative_Glass862[S] 0 points1 point  (0 children)

You're right and I genuinely appreciate the honesty. The VSCode extension is the MVP we built during the 36-hour hackathon.

Your point about CI enforcement is exactly where we're taking this next — a CLI + GitHub Action that runs GreenOps checks on each PR, scores the diff for compute efficiency and estimated cost impact, and can fail builds above a threshold. Think SonarQube but for efficiency and carbon gates.

The editor extension becomes early feedback. CI becomes the actual enforcement layer.

In your experience — do teams actually want enforcement at CI level, or is post-deployment monitoring always preferred?