WEBVTT

1
00:00:03.850 --> 00:00:08.871
Most software engineers have never been taught how their design choices affect energy use.

2
00:00:08.871 --> 00:00:15.326
The question a developer cannot answer at the keyboard is simply: where does this design choice spend energy?

3
00:00:15.326 --> 00:00:27.160
Neither the body of knowledge behind the curricula, nor mainstream courses, nor the development environment, nor the certification schemes yet answer it, and around all of them sit time pressure, and weak incentives.

4
00:00:27.160 --> 00:00:31.822
For engineering leaders that is a skills gap to close while also shipping.

5
00:00:31.822 --> 00:00:34.332
For universities it is a curriculum gap.

6
00:00:35.932 --> 00:00:39.063
GreenCode makes training a by-product of doing the work.

7
00:00:39.063 --> 00:00:47.759
As the pipeline refactors a codebase it writes transparent commit messages describing each change, and logs the QA analysis and energy profiling data behind it.

8
00:00:47.759 --> 00:00:56.456
At the end of a run that record is turned into human-readable reports and bespoke training materials prepared with reference to the team's own code.

9
00:00:56.456 --> 00:01:05.152
The reasoning is that a lesson drawn from the developer's own repository sticks better than an abstract best-practice document or a generic list of flaws.

10
00:01:06.752 --> 00:01:08.699
Two further mechanisms support this.

11
00:01:08.699 --> 00:01:20.771
First, GreenCode publishes evidence: it produces measurements that show whether a given green software pattern actually reduced energy in a real codebase, and feeds validated ones back to the pattern database.

12
00:01:20.771 --> 00:01:30.118
Second, successive analysis of a team's projects gives an indication of how sustainably the team works over time, pointing to where training is needed.

13
00:01:30.118 --> 00:01:37.517
And because GreenCode applies green principles on the developer's behalf, the message reaches teams that formal education would not.

14
00:01:39.117 --> 00:01:53.423
On the tooling side, three related items are planned: bespoke training material derived from the codebase and its optimisation decisions, codebase-specific guidance for upskilling a workforce, and documentation, learning artefacts and partner-facing workshops to support transfer.

15
00:01:53.423 --> 00:02:17.267
On the teaching side, the university partners are already putting the material in front of students: a master's course on energy-aware programming, a green software training programme run in a capital city and online, students taught to conduct empirical measurement studies, a cloud energy course with a lab on real infrastructure, and green IT in regular lectures on software architecture.

16
00:02:18.867 --> 00:02:31.955
For an engineering team, a run yields not only pull requests but a record of why each change reduced energy, expressed in their own code, which stays intelligible, so it is something a developer can learn from and build on.

17
00:02:31.955 --> 00:02:40.134
For universities and professional bodies, GreenCode supplies measured evidence and worked examples from real industrial codebases, so that sustainable practice becomes embedded rather than episodic.

18
00:02:40.134 --> 00:02:49.623
Reach out to us with the team you want to bring up to speed, and we will help you understand how GreenCode can teach them from their own code.
