►
Description
Digital services play an integral part in our daily lives. Many great things resulted from it but also many undesirable side effects. For example, digital services are responsible for 4% of global CO2 emissions, more than aviation.
As a developer, we can wonder what can we do to be more responsible in our work and reduce the negative side effects of it. How can we work on being more inclusive? On making our apps more accessible? How can we reduce the energy consumption of our software?
Join us to discuss what is responsible code and what can we do to implement it in our work.
A
A
A
The
way
ibm
decided
to
address
this
was
through
the
responsible
computing
framework.
The
framework
is
split
into
six
main
categories:
free
about
social
topics,
so
impact
system
and
data
usage
and
free
robot
technology,
so
data
center
infrastructure
and
code.
My
focus
was
on
code
and
I'm
guessing
yours
would
have
been
too.
So
what
is
responsible
code
responsible
code
is
to
be
aware
of
the
potential
environmental,
societal
and
economic
impact,
your
design
and
requirement
choices
could
have
and
how
you
can
minimize
their
negative
impact.
A
Now
we've
seen
already
some
of
the
negative
impact
of
technology,
but
I
still
want
to
spend
a
minute
on
the
impact
of
iit
on
our
environment.
Indeed,
digital
sources
amount
to
four
percent
of
the
global
queen
has
gas
emission
so
twice
that
of
aviation,
and
it's
important
to
understand
where
most
of
our
work
is.
A
So,
first,
what
are
the
kind
of
impact
I.t
can
have
on
our
environment?
So
obviously
there
is
energy
use
and
a
greenhouse
gas
emission
associated
to
it.
We
have
the
water
consumption
to
create
new
equipment
and
the
depletion
of
resources
again
linked
to
the
creation
of
equipment
and,
out
of
all
of
this,
a
study
by
united,
ranked
by
categories
with
numbers.
A
A
So,
as
you
can
see,
data
centers
that
are
often
depicted
as
a
villain
at
the
bottom
of
the
impact
hierarchy
for
digital
services,
both
at
the
energy
consumption
and
manufacturing
level,
it
doesn't
mean
we
don't
have
to
do
things.
The
trade
has
been
impacted,
but
it
shows
that
we
can
have
a
huge
impact
at
the
user
level,
especially
regarding
the
manufacturing
of
equipment,
so
the
manufacturing
of
user
equipment
is
responsible
for
more
than
half
of
impact
as
developer.
A
So
now,
let's
talk
about
how
we
can
reduce
the
impact
of
code
on
our
environment
step,
one
is
to
remove
unnecessary
features
and
code.
The
same
way,
you
would
say
the
best
trash
is
the
one
that
does
not
exist,
but
pollution.
You
can
say
the
same
about
code,
so
the
best
code,
slash
feature
is
the
one
that
does
not
exist.
A
A
An
example
of
design
choices
that
you
need
to
always
remove
is
autoplay,
because
you
use
data
and
energy
to
run
the
video,
but
might
not
even
interest
the
user
and
also,
if
you
have
user,
that
are
visually
impaired
and
might
mess
with
their
experience
on
your
web
page.
So
you
can
answer
things
about
following
the
requirements.
A
We
are
lucky
enough
in
the
web
area
to
have
a
standard,
but
it's
called
the
wcag
2.1,
so
you
just
need
to
have
an
aaa
rating
on
this.
One
ibm
also
made
a
website
available
for
you
with
tools
to
test
accessibility
of
your
web
page,
and
you
also
want
your
code
to
not
follow
the
digital
divide,
meaning
make
it
work
for
people
that
are
not
as
technology
savvy
as
you
are,
or
have
a
bad
internet
connection.
A
And
finally,
you
want
inclusivity
in
your
illustration,
videos
and
forms
so
that
everyone
feels
included
on
your
website
and
stay
wary
of
biases
in
ai
models.
Apis
or
data
sets
you
are
working
with
and
once
you've
done
all
that
you
will
need
to
optimize
your
code.
So
I
said
previously,
most
of
the
impact
of
digital
services
happen
in
the
creation
of
different
terminals.
So
the
best
way
of
reducing
our
impact
is
to
fight
against
obsolescence
and
having
to
upgrade
the
hardware
to
match
software
needs.
A
So
when
we
use
more
ram
and
cpu,
our
computer
usually
goes
slower
and
that
drives.
We
want
in
consumer
to
upgrade
to
a
new
and
faster
computer,
which
is
the
main
issue
we
have
right
now.
So
optimizing
your
code
and
looking
at
kpis
such
as
cycle
count,
cpu
consumption
memory,
usage
network
calls
size
of
your
page
is
the
way
to
go
to
try
to
keep
resources
usage
as
low
as
possible
and
to
fight
obsolescence.
A
A
And
certified
libraries-
usually
they
already
are
optimized
to
the
best
of
what
is
possible.
However,
so
you
do
not
have
to
spend
your
time
optimizing.
The
code
yourself,
however,
if
you
do
use
that
just
stay
careful
of
possible
data,
which
is
when
using
public
libraries
now
that
we
have
looked
through
all
of
this,
you
might
think.
Well,
it's
all
filed
well,
but
I'm
not
alone
in
my
team
and
I
do
not
have
the
full
creative
power
of
the
application.
A
A
So
let
me
tell
you
about
my
story
and
the
way
I
started
acting
to
make
sustainability
more
of
a
common
topic
to
be
discussed
so
that
everyone
in
my
team
thinks
about
it,
not
just
me.
So
when
I
first
started
working
within
my
company,
I
looked
around
and
I
saw
so
many
things
that
could
change
and
that
needed
to
change
and-
and
I
think
we
all
do,
one
of
that
things
was
about
a
very
specific
topic
on
sustainability
and
lucky
enough,
I
found
someone
else
that
wanted
to
do
something
about
it
around
a
coffee
machine.
A
So
we
started
getting
in
touch
with
the
person
in
charge
of
such
things
to
discuss
possible
challenges,
and
while
talking
to
them,
we
found
out
that
we
had
been
approached
by
two
other
people
on
the
topic.
So
I
wasn't
alone
trying
to
change
things.
All
I
needed
to
do
was
to
find
others
like
me
and
start
working
on
things
together.
A
The
thing
about
big
dreams
is
that
you
need
to
put
in
the
rock
to
make
sure
that
you
can
reach
them,
and
the
first
thing
to
ask
that
matter
was
that
we
needed
to
be
taking
seriously
and
not
just
as
idealists,
as
might
be,
the
case
when
it
came
to
sustainability
a
few
years
ago
and
still
do,
and
so
we
worked
hard
on
making
professional
presentations
the
same
way.
We
will
do
if
we
were
talking
to
a
client,
even
if
it
was
all
about
internal
topics
and
not
a
business
faded
on.
A
So
we
started
by
creating
a
structure
that
could
scale
to
get
more
people
in
and
then
we
made
branding.
So
we
had
a
logo
and
a
catchy
name
that
was
korean
with
our
company's
brand.
So
if
you
do
the
same,
make
sure
that
the
people
in
charge
of
the
brand
for
your
company
know
about
your
project.
Otherwise
you
might
get
in
trouble
because
there
is
a
lot
of
legal
aspect
linked
to
branding.
So
that's
why
we
chose
to
keep
our
branding
internal
and
I'm
not
showing
it
to
you
right
now.
A
A
We
believe
this
will
also
give
us
more
credibility
when
presenting
our
project
later,
especially
to
executives
once
we
had
a
solid
base.
We
started
expanding
and
finding
people
like
us
that
were
interesting
about
sustainability
and
wanted
to
act.
That
way,
we
started
to
grow
and
work
on
more
projects
and
we
ended
up
with
quite
a
big
community.
A
So
now,
if
you
want
to
do
the
same,
I
can
give
you
some
advice
of
what
I
found
and
learn
along
the
way.
So
first
start
small,
then
scale.
This
is
key
because
in
the
beginning
you
will
encounter
a
lot
of
setback
and
it
will
require
a
lot
of
on
top
work.
So
you
will
need
to
be
passionate
about
what
you
are
doing
in
order
to
not
lose
interest
and
motivation,
and
so
focus
on
one
project
with
people
you
trust
and
make
it
become
a
reality
that
way.
A
A
So
now
let
me
go
into
the
final
tips
and
tricks
to
creating
your
community.
So
in
the
beginning,
do
not
cont
your
hours.
Creating
community
takes
time.
You
have
to
work
on
branding
structure,
presentation.
You
also
need
to
onboard
new
people
and
find
sponsors.
So,
as
you
can
guess,
it
takes
quite
some
time.
A
A
A
Indeed,
most
of
the
time
people
want
to
help,
they
just
don't
know
how
or
where
to
start
also
most
of
the
time
what
you
are
doing
with
your
community
would
be
on
top
of
your
job,
and
it
would
require
a
lot
of
work.
So
you
need
to
remind
yourself
that
you
need
to
keep
it
light
and
enjoy
what
you
are
doing.
Otherwise
you
will
lose
interest
and
motivation
quite
quickly.
A
A
We
ended
up
working
on
quite
a
few
projects
and
presentation
to
teach
our
colleagues
more
about
sustainability,
so
this
all
led
to
the
topic
being
more
and
more
discussed
in
regular
meetings
and
everyone's
starting
to
think
more
and
more
about
it,
and
also
our
executives
are
the
employees
speaking
on
this
with
a
common
and
bigger
voice.
So
they
now
know
what
it
really
matters
to
us.
So
now
I'll.
Let
stefan
walk
you
through
his
parts
on
how
you
can
engage
your
team
towards
the
common
goal.
B
Wow
lucille
thanks
for
your
presentation,
that's
really
so
inspiring
to
to
hear
it,
and
you
know
this
is
a
great
example
to
follow
how
to
actually
make
something
happen
and
and
create
enthusiasm
and
and
motivating
people
to
to
bring
change
right
and
also
all
those
guidelines.
I
think
we
should
really
look
more
at
those.
I
really
see
myself
as
a
developer
that
sometimes
I
forget
those
so
always
a
great
inspiration.
B
How
do
you
actually
manage
to
bring
change
in
your
product
in
your
offering
what
you
are
actually
doing
for
work
right,
and
this
is
very
often
when
it
gets
difficult,
but
why
is
that
actually
so
difficult
to
make
it
happen?
Well,
you
know.
One
thing
is
that
the
dimension
keep
increasing.
You
have
to
take
care
about
efficiency.
B
B
B
This
is
an
example
of
a
gdpr
here,
but
on
the
climate
side
as
well,
things
are
not
slowing
down
at
the
opposite,
they
are
getting
faster
and
faster
and
the
goals
are
getting
stronger
and
stronger
each
year.
So
we
really
have
to
take
new
methods
for
that.
We
cannot
just
do
it
the
old
way
and
just
say:
yeah,
look
we'll
optimize
a
bit
the
front
end
and
make
the
database
a
bit
smaller,
whatever
clean
up
a
build
to
feel
no,
you
really
have
to
go
to
much
greater
length
and
rethink
the
way
you
work.
B
B
B
B
And
so
that
that
was
an
interesting
thing
for
me,
because
this
was
made
me
think.
Okay,
there
seems
to
be
a
problem
of
alignment
with
the
rest
of
the
team.
Like
not.
The
whole
team
is
the
line
on
those
goals
and
if
you
have
the
only
the
developers
who
care
about
this,
this
won't
work,
and
it
looks
to
me
like
this-
is
often
the
problems
that
happens
in
the
team.
B
You
have
either
the
developers
or
a
special
group
of
interested
people
around
ethic,
around
sustainability,
around
accessibility
depending
of
their
own
interest,
but
that
doesn't
map
to
the
whole
team,
and
so
here
in
the
last
decade,
working
with
designers,
I
really
learned
a
lot
about
how
they
think
and
how
they
have
different
methods
for
getting
to
success
and
developer.
Probably
in
my
view,
I
have
a
lot
to
learn
from
this.
So
what
do
designers
do?
Generally?
They
don't
accept
to
work
on
a
single
unit
problem.
B
B
B
And
so
what
about?
If
we
had
the
same
view
on
those
coding
topics
as
well,
you
know
those
co.
Those
topics
that
actually
we
thought
just
touch
the
code,
but
actually
they
don't.
They
touch
the
whole
team
and
I
think,
that's
a
general,
a
general
thing
in
software
right
now
that
software
actually
touches
the
whole
society.
So
it's
not
it's
not
a
thing,
that's
hidden
anymore,
and
so
that's
why
also?
We
have
to
rethink
a
bit
about
our
responsibility
in
the
world.
B
So
how
do
designer
work?
Well?
They
have
different
methods,
for
example,
design
thinking
that
you
might
have
known
or
touched
or
tried
to
gather
already,
but
in
in
our
organization
we
have
this
fantastic
guy
called
tom
dayton
and
he
used
to
work
at
the
nasa
and
he
used
methods
very
similar
to
design
thinking
for
working
with
engineers
and
project
managers
to
actually
clearly
define
a
requirement
across
a
broad
set
of
organizations
and
specialties,
and
he
taught
me
the
word
collaborative
methods,
and
so
I
search
a
bit
more
about
this,
and
this
is
very
interesting.
B
Collaborative
methods
according
to
wikipedia
are
the
process
behavior
and
conversation
that
relate
to
the
collaboration
between
individuals.
This
method
specifically
aimed
to
increase
the
success
of
teams,
as
they
engage
in
collaborative
problem
solving
well.
This
sounds
very
interesting.
This
is
really
about
bringing
the
whole
team
together
and
having
common
decision
in
a
way,
that's
the
most
effective.
That
brings
the
best
results
without
wasting
too
much
time,
but
at
the
same
time,
not
letting
good
things
on
the
table.
B
So
what
are
the
base
principles
to
make?
Actually
this
work?
Well,
one
of
the
things
that
first,
everyone
has
an
equal
voice.
This
is
aim
at
flattening
the
hierarchy.
So,
of
course
you
cannot
change
everything.
Loud
people
will
probably
stay
loud.
Quiet
people
will
probably
stay
quite
a
bit,
but
many
of
the
processing
methods
and
collaborative
methods
are
actually
made
to
to
to
to
drastically
reduce
those
kind
of
differences.
B
B
The
next
thing
is
that
also
ids
should
be
additive
means
anyone's
id
account.
Anyone's
id
can
be
produced
and
put
on
the
board,
and
if
you
disagree
with
an
id
just
write
your
own
id,
but
don't
try
to
talk
down
the
the
other
ids
and
again
here.
The
facilitator
is
here
to
prevent
that
kind
of
misbehavior
and,
with
that
context,
the
flattened
hierarchy,
the
additivity
of
the
ids,
you
create
a
very
safe
environment
where
everyone
can
feel
safe
to
be
creative
and
and
propose
things
that
it
wouldn't
has
proposed
in
traditional
meeting
models.
B
Usually
there
is
no
big
discussion
on
that
that
this
is
actually
a
valid
point
to
to
be
brought
forward,
or
at
least
analyzed
and
validated
to
the
next
step.
So
what
are
collaborative
methods
that
you
can
use?
Well,
there
are
quite
quite
a
few
of
them,
and
so
this
is
a
very
short
list
here,
but
look
at
design
thinking,
for
example,
I'm
personally
very
proficient
with
design
thinking
working
with
it.
For
the
past
six
years,
it's
it
served
me
very
well
and
it's
it's
always
great.
With
teams,
it's
very
positive
oriented.
B
B
Liberating
structure
offers
a
wide
range
of
exercise
that
sometimes
are
pretty
much
different
from
design
thinking,
sometimes
a
bit
more
similar,
but
they
have
also
formats
like
one-on-one
interviews,
and
you
know
like
a
model
for
ids
to
bubble
up
as
some
kind
of
a
one-on-one
discussions.
So
it's
really
interesting
as
well
and
lego.
Serious
play
is
also
a
very
fun
and
interesting,
maybe
a
bit
more
oriented
toward
team
organization
problems
and
so
on,
but
still
very
interesting
and
I
think,
actually
usable
in
a
lot
of
different
ways.
B
Please
don't
call
them
workshops,
workshops
is
it
has
some
connotation
and
especially
one
that
I
think
is
detrimental
is
that
it
make
you
think
yeah
you're
going
on
this?
Maybe
I
don't
know
one
week
retreat
or
so
and
doing
a
workshop
and
then
you're
done,
and
this
would
be
like
saying
that
you
would
work
on
your
continuous
integration
for
one
sprint
and
then
you
you
just
let
it
as
is
and
and
don't
work
on
improving
it
anymore.
B
You
will
be
leaving
a
lot
of
potential
on
the
table
in
that
case,
so
my
recommendation
is
you
try
to
use
it
on
a
regular
basis?
Maybe
I
don't
know
once
or
twice
a
week
at
least,
but
in
small
bursts
of
one
to
two
hours,
so
people
don't
get
burned
out
by
it
because
believe
me,
when
you
are
really
into
such
kind
of
activities,
this
is
very
demanding.
You
have
to
be
fully
there,
and
so
many
people
are
not
used
to
that.
B
You
can,
of
course,
start
with
a
short
workshop
and
it's
always
good
for
the
base
education
for
for
getting
the
ball
running
at
the
start
and
setting
the
right
goals,
but
then
a
afterwards.
You
should
really
make
it
a
process
inside
your
team,
so
at
ibm
we
actually
use
even
design
thinking
for
designing
ai
concepts.
B
So
this
is
a
method
that
I
know
works
very
well,
and
the
advantage
of
that
method
is
that
you
bring
everyone
together
and
the
product
managers,
the
designers,
the
data
scientists,
the
developers,
the
marketing
and
you
discuss
together
about
the
feasibility,
the
pro
and
cons
of
each
id,
and
you
try
to
be
to
be
to
be
creative
and
bold
and
then
bring
it
back
to
what's
to
actually
doable,
and
you
also
look
at
the
ethical
aspect
of
the
solution.
What
could
go
wrong?
B
So
collaborative
methods
are
still
no
magic.
I
think
they
are
very
useful.
They
are
a
major
tool
and
very
important,
but
there
are
no
magic.
For
example,
they
highly
depend
on
the
facilitator.
You
have
on
board
right,
but
still
they
will
help.
You
become
a
responsible
team
faster
and
how
actually,
by
taking
better
decision,
because
they
will
look
at
the
full
picture
in
your
own
context,
so
you
will
really
be
able
at
designing
and
crafting
the
best
solution
for
you.
B
What
your
team
can
actually
accomplish
and
will
allow
everyone
to
look
in
the
different
dimension
and
also
those
methods
are
very
fun.
So
usually
they
improve
the
team
spirits
and
they
allow
everyone
to
have
a
voice.
They
allow
the
whole
team
to
know
who
whose
strengths
is
in
what
area
and
they
improve
the
network
inside
the
team.
So
very
often
it
shortens
the
communication
path
afterwards
and
also
the
decision
path
in
first
decision,
so
they
have
really
good
side
benefits.