Cloud Carbon Footprint for On-Premise post

[mgriffin-scottlogic]

Please add a direct link to your post here:

https://mgriffin-scottlogic.github.io/blog/2024/06/20/cloud-carbon-footprint-on-premise.html

Have you (please tick each box to show completion):

• [x] Added your blog post to a single category?
• [x] Added a brief summary for your post? Summaries should be roughly two sentences in length and give potential readers a good idea of the contents of your post.
• [x] Checked that the build passes?
• [x] Checked your spelling (you can use npm install followed by npx mdspell "**/{FILE_NAME}.md" --en-gb -a -n -x -t if that's your thing)
• [x] Ensured that your author profile contains a profile image, and a brief description of yourself? (make it more interesting than just your job title!)
• [x] Optimised any images in your post? They should be less than 100KBytes as a general guide.

Posts are reviewed / approved by your Regional Tech Lead.

[mgriffin-scottlogic]

Nice work Matthew, I'm sure this will be very useful for people interested in this tool.

I've just got a few suggestions for bits I found confusing as a non-expert. It may well be that you're writing for a more informed audience than me, so feel free to politely ignore all my comments!

One general comment is that you should be clear from the first sentence what this blog post is about -- which is to say, why I should bother reading it?

• Is it to help the reader use this tool for themselves?
• Is it to help them evaluate whether to use this tool over an alternative?
• Is it something else?

Possibly this post does more than one of these things, which will irritate my tidy-mindedness, but it's still better to communicate that right from the start. You could even try out some different title ideas to see if they get the message across better.

Thanks a lot Joe, lots of good stuff to consider here. In terms of what it's about, I guess it grew out of an internal document to examine the tool and whether we would use it, so maybe the first point mostly? At the time it was written I wouldn't say there was a clear alternative, certainly not that was free and open source anyway. But I do think it's a very different prospect from their automated cloud based solution, which might not be what everyone would hope for.