The Green Software Practitioner in 2024?

[russelltrow]

As we move into the new year this is a great opportunity for us to start discussing what we would like to see from the Green Software Practitioner course in 2024

Planned

There are a few initiatives that we have previously discussed and are planned for this year:

• https://github.com/Green-Software-Foundation/writers/issues/185
• Translations - Dutch, Chinese, Japanese, German
• v2.0 of the course updated based on learning feedback with more far visuals and videos
• Creation of an eLearning/SCORM course from the existing content

There are also a few larger Executive Programs that will support the GSP course more broadly:

• GSF Learn Platform, Bring the GSP course in-house
• Redesign the learn.greensoftware.foundation website
• Distribution of the course to other training platforms such as coursea, Pluralsight

As an extension to the course we have also discussed the creation of a Certified Green Cloud Engineer Exam

Potential

We would now love to hear from you. What do you need from the Green Software Practitioner course? How would you like to see it evolve? How else could our training support you?

• How might we answer "What next?" after completing the course - Now that I have completed the course how can I apply the knowledge and continue my journey?
• How might we have less developer-centric content? What about Design, Product and other related functions?
• How might we connect with the patterns?
• How might we provide the knowledge in alternative formats such as a Chat bot or microlearning?

[russelltrow]

In the Principles & Patterns project call on 9th January the following ideas were raised for evolving the Green Software Practitioner and Patterns projects:

learn.greensoftware.foundation website

• Organise the website around the concept of "Measure > Learn > Reduce"
• Use the website to bring together the best of the GSF projects and demonstrate how they connect in the real-world

Green Software Practitioner course

• Course revamp - There is a lot of new content that we could add
• Use more videos & visuals to make the course content easier to digest
• Create Different levels of practitioner courses similar to AWS
• Make it less developer centric
• Review whether there is too much content in the current course - does everyone really need to know everything?
• Make it easier to apply the knowledge gained - Answer "what next?" after completing the course as we are currently missing what this means for me as a practitioner

Green Software Patterns

• Make the Patterns more accessible by linking them the core green software principles and real-world Use Cases
• Gather SCI Use Cases and link to the Patterns & Principles

Certification

• Re-assess the proposed “Green Cloud Engineer Certification”

---

I will create a comment below for each of these issues so we can continue evolving them.

[aecurrie]

I'm going to step in with a pre-measurement suggestion. The biggest low hanging fruit doesn't need us to measure anything other than your hosting bill. So there are measure learn reduce loops that happen with proxy measurements before carbon comes into it and those are probably going to be your biggest wins

…

On Mon, Jan 15, 2024 at 1:16 PM Russell Trow ***@***.***> wrote: In the Principles & Patterns project call on 9th January <Green-Software-Foundation/patterns#293> the following ideas were raised for evolving the Green Software Practitioner and Patterns projects: learn.greensoftware.foundation website - Organise the website around the concept of "Measure > Learn > Reduce" - Use the website to bring together the best of the GSF projects and demonstrate how they connect in the real-world Green Software Practitioner course - Course revamp - There is a lot of new content that we could add - Use more videos & visuals to make the course content easier to digest - Create Different levels of practitioner courses similar to AWS <https://aws.amazon.com/certification/> - Make it less developer centric - Review whether there is too much content in the current course - does everyone really need to know everything? - Make it easier to apply the knowledge gained - Answer "what next?" after completing the course as we are currently missing what this means for me as a practitioner Green Software Patterns - Make the Patterns more accessible by linking them the core green software principles and real-world Use Cases - Gather SCI Use Cases and link to the Patterns & Principles Certification - Re-assess the proposed “Green Cloud Engineer Certification” ------------------------------ I will create a comment below for each of these issues so we can continue evolving them. — Reply to this email directly, view it on GitHub <#213 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2TULDFGNBMCECLUMUORT3YOUT3FAVCNFSM6AAAAABBS5GOS6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCMZTGAYTA> . You are receiving this because you are subscribed to this thread.Message ID: <Green-Software-Foundation/learn/repo-discussions/213/comments/8133010 @github.com>

[russelltrow]

[learn.greensoftware.foundation]

Idea: Organise training around the concept of "Measure > Learn > Reduce"

https://greensoftware.foundation/articles/green-software-foundation-expands-efforts-to-incentivize-decarbonization-in-t

[russelltrow]

(learn.greensoftware.foundation)

Idea: Use the website to bring together the best of the GSF projects and demonstrate how they connect in the real-world

• Lower the barrier to entry for practitioners
• A "Green Software Academy"
• Bring together Standards, tooling and best practices for creating and building green software” (all our projects in one place)
• Bring together all our knowledge projects (Patterns, Maturity, OUSE, SOGS etc..)
• Speaks to Engineering, Design, Product etc..

[russelltrow]

Discussed and developed the idea in P&P call on 16th Jan

[russelltrow]

(Green Software Practitioner)

Idea: Course revamp - There is a lot of new content that we could add

• If we were to revamp the course what was that mean for existing practitioners?
  • Would it be confusing for those who have already gained the certification?
• Are we better building on top of the the course rather than amending the existing content?
• Others are already developing new content so should we be referencing others work rather than developing more for ourselves?
  • Should we be duplicating effort?
  • e.g. https://www.greenskills.inco-group.co/
  • e.g. https://www.unssc.org/courses/digital4sustainability-learning-path
  • e.g. https://lfca.earth/event/digital-sustainability/
• Rather than a revamp, what is 2.0? - What is the increment we want to see?
• How can we tackle any potential gaps in the content around specialisation (non-developer)
• Received feedback that lots of the examples are too trivial - Missing the real-world application
• Could well be better to connect to our tooling and use-cases

A revamp feels a lower priority

[russelltrow]

Discussed and developed the idea in P&P call on 16th Jan

[russelltrow]

(Green Software Practitioner)

Idea: Use more videos & visuals to make the course content easier to digest

• Analyse feedback collected from the Linux Foundation course #199

[russelltrow]

(Green Software Practitioner)

Idea: Create Different levels of practitioner courses similar to AWS

• Create Different levels of practitioner courses Similar to AWS
• Connect different levels to Maturity Matrix

[russelltrow]

(Green Software Practitioner)

Idea: Make it less developer centric

• Questioned whether the course truly is developer-centric or it just appears that way
  • Does it not really speak to non-developers rather than actually being developer-centric
  • Is it just a positioning thing?
  • Is it a language thing? Are we speaking in a language that is familiar to non-developers?
• We should assess which content is applicable to everyone vs developers
• Having clear next steps from the course be more powerful than trying to cater to everyone in the one course
• Connects to Idea: Review whether there is too much content in the current course

[russelltrow]

Discussed and developed the idea in P&P call on 16th Jan

[cf-almeida]

An important point would be to put some thought on the Principles as well. Efficiency is a core and mostly the only aspect we are focused on. That makes GSF very engineering centered and may reduce the reach to other audiences. Even if the scope stays within efficiency, it is interesting to maybe explore what efficiency could mean to designers and product managers beyond energetic efficiency. For example, how is efficiency seen in a context of user experience? How can design friction and the absence of it impact on user behavior and therefore on the gains created by engineering efficiency? How can that impact as well on cost, price fluctuations, profit margins and potential creation of business models that are supportive also a sustainable and fair future instead of leading to even greater levels of exploitation?

[Mettenim]

Would also like to add that there are gains to be made in the area of service design as well. This often involves how multiple software tools work with each other in tandem within an ecosystem, and ways to ease the end-to-end processes (both technical and user facing)

[russelltrow]

(Green Software Practitioner)

Idea: Review whether there is too much content in the current course

• Does everyone really need to know everything?
• Split into different levels of depth depending how deep you want to go
• Content is a lot more complex than first appears
• Some elements are too specific

[russelltrow]

(Green Software Practitioner)

Idea: Make it easier to apply the knowledge gained

Answer "what next?" after completing the course as we are currently missing what this means for me as a practitioner

[russelltrow]

(Green Software Patterns)

Idea: Make the Patterns more accessible by linking them the core green software principles and real-world Use Cases

• Make more accessible by connecting to the Principles
• Link each Pattern back to the 3 core principles
  • Carbon Efficiency: Emit the least amount of carbon possible.
  • Energy Efficiency: Use the least amount of energy possible.
  • Carbon Awareness: Do more when the electricity is cleaner and do less when the electricity is dirtier.
• Connect to a use case - “Here is how it might look”
• Use Cases that are potentially not directly connected to SCI
• Potentially other measurements such as Cost, "How a person's work impacts green software" > Overall productivity
• CAST are developing case studies based on https://www.omg.org/spec/ASCRSM/1.0/Beta1/About-ASCRSM#document-metadata to allow a direct link between the project and reduction - Plan to publish a selection e.g. Italian Highways - Expect to have results this year

Agreed that Use Cases are a very powerful way prove the value of our projects

[russelltrow]

Discussed and developed the idea in P&P call on 16th Jan

[russelltrow]

(Green Software Patterns)

Idea: Gather SCI Use Cases and link to the Patterns & Principles

• e.g. [Dow/MSFT] Graph DB Use Case sci-guide#31
• Prove that you can reduce your carbon footprint by applying these principles & patterns
  • Having SCI gives me proof and allows me to demonstrate the impact
• It can be a challenge to implement SCI so a higher barrier to entry
• One of the biggest challenges is simply having the data
• Use Cases are particularly interesting as have the blessing of companies - Significant effort to get them published
• We need to speed up the process of creating Use Cases
• Tammy is applying SCI to her dog food business - A great example of SCI application outside the norm
• https://sci-guide.greensoftware.foundation/CaseStudies
  • Focus on the DOW/MSFT one first - It's almost there

[russelltrow]

Discussed and developed the idea in P&P call on 16th Jan

[russelltrow]

(Certification)

Idea: “Green Cloud Engineer Certification”

• [Project Proposal] Certified Green Cloud Engineer Exam community-wg#92