Planet Friendly

Web Development

Hello!

Chris Adams - @mrchrisadams

environmentally focussed web generalist

Designer, then Developer, then Sysadmin, then Developer again, then Product Manager, then UX Consultant, then User Researcher. Now (nearly) ALL OF THE ABOVE.

Why you might care

 

1. Why you might care.
2. How websites have an environmental footprint.
3. What you can do.

Why you might care

Our activity is changing the planet

Don't believe me?

Ask XKCD.

http://xkcd.com/1732

 

What can a technologist do about climate change?

http://worrydream.com/ClimateChange/

How websites have an environmental footprint

Where impact happens

Build the right thing

Build the thing right.

Deliver the thing.Right. 

Spreadsheet -  link

Build the right thing

Understand the problem

Australian DTO Head of Service Design 

Speaking to users and customers

Travel, often by air

Build the thing right

Solving problems with code:
Humans in buildings.
Servers in buildings.

 

Title Text

Deliver the thing

Sharing the solution:

More humans in buildings.
Humans outside of buildings

Other people's servers

Ever growing page sizes

Growing faster than aviation

Same CO2 footprint
as Poland.

Three main ways engineers can influence this

Where impact happens

Build the right thing

Build the thing right.

Deliver the thing.Right. 

Build the right thing

Understanding the problem

Exposure hours

Remote tools… 

Make speaking to users cheaper. You're more likely to build the right thing.

Closed

Calendly for booking calls and meetings

Slack for chat and live blogging use

Join.me for screen sharing

Google Drive for storing screen share vids.

Google docs for discussion guides

Wordpress  for blog

Open

<Insert Django form >

Mattermost - open source slack

WebRTC - talky.io

Owncloud for sharing videos

Text

<Insert Django Blog - Wagtail>

Build the thing right

Solving problems with code

Where does the power come from?

electricitymap.org

Green Clouds are easy now

Physical servers: i.e. Hetzner

IaaS: i.e. AWS, Google Cloud

PaaS: Cloudfoundry, Heroku

FaaS: AWS Lambda, Openwhisk

Open

IaaS:

Openstack

PaaS:

Cloudfoundry

FaaS:

Openwhisk, Funcatron -

Zappa

Closed

IaaS:

AWS, Google Cloud, etc

PaaS:

Heroku

FaaS:

Chalice - python on AWS Lambda

Deliver the thing

Sharing the solution

Easy Performance Budgets

Speedcurve

CI, for site performance

Django: Whitenoise
Nginx: ngx_pagespeed
Cloud: Optimise on upload (see wagtail tiny)

 

Where impact happens

Make talking to users easy

Green power first.

Minimise data over the wire

Thanks!

Made with Slides.com