Coding Culture

181
1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 1 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 1 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 1 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 1 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 1 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 1 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 1 1 1 0 1 0 0 0 1 1 1 0 1 0 1 0 0 1 0 1 0 1 CULTURE @svenpet CODING

description

One day we woke up and realized that our days are filled with all kind of stuff unrelated to code or product, that our goals are driven by product owners, and that our code design is dictated by architects trying to tell us how we should solve problems. A strong coding culture gives the power back to the developer to concentrate on one thing: Create awesome stuff! Imagine a culture where the input of the whole organization turns an individual idea into a user story in just a couple of hours; where everybody's goal is to make the customer awesome, and where you work on stuff you love instead stuff you loathe. A great coding culture concentrates on making developers productive and happy by removing unnecessary overhead, bringing autonomous teams together, helping the individual programmer to innovate, and raising the awareness among the developers to create better code. I will talk about how to establish and foster a strong engineering-focused culture that scales from a small team to a huge organization with hundreds of developers. I'll give lots of examples from our experience at Atlassian to show that once you're working in a great coding culture, you won't want to work anywhere else. You can find a video version of the talk here: https://www.youtube.com/watch?v=rRc0FEg46kw

Transcript of Coding Culture

Page 1: Coding Culture

1001

0101

0011

1010

0011

1010

1001

0101

1010

1001

0011

0101

1110

0001

0000

1000

1110

0001

0000

1000

1010

1001

0011

0101

1001

0101

0011

1010

0011

1010

1001

0101

1001

0101

0011

1010

0011

1010

1001

0101

1010

1001

0011

0101

1110

0001

0000

1000

1110

0001

0000

1000

1010

1001

0011

0101

1001

0101

0011

1010

0011

1010

1001

0101

0011

1010

1001

0101

1110

0001

0000

1000

1001

0101

0011

1010

0011

1010

1001

0101

1010

1001

0011

0101

1001

0101

0011

1010

1010

1001

0011

0101

1001

0101

0011

1010

0011

1010

1001

0101

1001

0101

0011

1010

0011

1010

1001

0101

1010

1001

0011

0101

1110

0001

0000

1000

1110

0001

0000

1000

1010

1001

0011

0101

1001

0101

0011

1010

0011

1010

1001

0101

1001

0101

0011

1010

0011

1010

1001

0101

1010

1001

0011

0101

1110

0001

0000

1000

1110

0001

0000

1000

1010

1001

0011

0101

1001

0101

0011

1010

0011

1010

1001

0101

0011

1010

1001

0101

1110

0001

0000

1000

1001

0101

0011

1010

0011

1010

1001

0101

1010

1001

0011

0101

1001

0101

0011

1010

1010

1001

0011

0101

1001

0101

0011

1010

0011

1010

1001

0101

CULTURE@svenpet

CODING

Page 2: Coding Culture

THE FOLLOWING PRESENTATION HAS BEEN APPROVED FOR

OPEN AUDIENCES ONLYBY THE PRESENTATION ASSOCIATION OF MY IMAGINATION

PROFANITYP Hypersensitivity to occasional profanity requires covering ears.

OCCASIONAL PROFANITY (SORRY MOM!)

Page 3: Coding Culture

WHAT IS

?CULTURE

Page 4: Coding Culture

SO, WHAT IS CULTURE?

Page 5: Coding Culture

THAT MAKES THE DEVELOPER HAPPYAPING PONG & FREE FOOD

BEER ON TAP

NERF GUNS

CULTURE

Page 6: Coding Culture

CULTURETHIS IS NOT

Page 7: Coding Culture

EXAMPLECULTUREBAD

Page 8: Coding Culture

WHY ARE COMPANIES DOING THAT?

Page 9: Coding Culture

FREDERICK WINSLOW TAYLOR

IT’S HIS FAULT!

Page 10: Coding Culture

EFFICIENT WORKERS THINKING MANAGERS

Page 11: Coding Culture

TIMES HAVE CHANGED!

Page 12: Coding Culture

WORK HAS CHANGED!

Page 13: Coding Culture

PEOPLE HAVE CHANGED!

Page 14: Coding Culture

COMPANIES…CHANGE SLOWLY

Page 15: Coding Culture

NOWPAST

Page 16: Coding Culture

Sven PetersAtlassian Evangelist

@svenpetsvenpet.com

Page 17: Coding Culture
Page 18: Coding Culture

ATLASSIAN CO-FOUNDER

Page 19: Coding Culture

INNOVATIONOF

1

CULTURE

Page 20: Coding Culture

INNOVATE OR DIE

Page 21: Coding Culture

GO & INNOVATE

Page 22: Coding Culture

$ FOR GOOD IDEAS!

Page 23: Coding Culture

INNOVATE ?HOW TO MOTIVATE PEOPLE TO

Page 24: Coding Culture

GIVE THEM TIME

THEIR OWN IDEAS TO TRY

Page 25: Coding Culture

SHIP IT DAY

BRAINSTORM HACK 24 HOURS

THE WHOLE COMPANY EVERY QUARTER

SHOW & WIN

Page 26: Coding Culture
Page 27: Coding Culture

SHIP IT DAY

WORKING PROTOTYPE

REASON WHY WE DECIDED TO BE DEVELOPERS

HAPPY DEVELOPERS

Page 28: Coding Culture

INNOVATION FOR THE MASSES

Page 29: Coding Culture

IDEAS CAN HAPPEN TO ANYONE ANYTIME

Page 30: Coding Culture

INNOVATION HAPPEN

GIVE IT A POSSIBILITY TO GROW

Page 31: Coding Culture

HAPPINESSOF

2

CULTURE

Page 32: Coding Culture

FAMILY & FRIENDS DAY

TEAM BUILDING

EOFY PARTY (GAMES OF CODE)

FUN WITH CO-WORKERS

Page 33: Coding Culture

FUN WITH CO-WORKERSBUILDS RELATIONSHIPS

LEARN ABOUT STRENGTH & WEAKNESSES

Page 34: Coding Culture
Page 35: Coding Culture
Page 36: Coding Culture

LIFE MOVES PRETTY FASTIF YOU DON’T STOP AND LOOK AROUND ONCE IN A WHILE, YOU COULD MISS IT

Page 37: Coding Culture

& CELEBRATE THE TEAM WINS!STOP

ORGANIZE A RELEASE PARTYBAKE A CAKE

DO A TEAM OFFSITE

Page 38: Coding Culture

SERVICE TEAM VALUES

Page 39: Coding Culture

THEY BECAME BLURRY ON A DAY TO DAY BASES

Page 40: Coding Culture

& CELEBRATE THE CULTURE ROCKSTARS!STOP

Page 41: Coding Culture
Page 42: Coding Culture

& CELEBRATES SMALL & BIG WINSSTOPMAKES US HAPPIER

HELPS US TO FOCUS

Page 43: Coding Culture

HOW HAPPY ARE YOU?

Page 44: Coding Culture

AND YOUR TEAM?

Page 45: Coding Culture

SUCKS & SLOW

Page 46: Coding Culture

LEARN

Page 47: Coding Culture

MEASURE

Page 48: Coding Culture

ADOPT

Page 49: Coding Culture

ADOPT

AFTER OUR COMPANY PARTY

http://atlss.in/mood_app

Page 50: Coding Culture

ADOPT91% HAPPY!

TALKED TO UNHAPPY PEOPLE

94% HAPPY!

Page 51: Coding Culture
Page 52: Coding Culture

SHARE THE PAIN

SERIOUSLY NO FINGER POINTING INFORM & UPDATE

Page 53: Coding Culture

SHARE THE PAINWIN AS A TEAM & LOSE AS A TEAM

Page 54: Coding Culture

MAKES US STRONGER

Page 55: Coding Culture

BALANCE PASSIONOF

3

CULTURE

Page 56: Coding Culture

WHY DO WE CODE?

CODING / CREATING GREAT SOFTWARE MAKES US HAPPY

Page 57: Coding Culture

INGREDIENTS FOR GREAT SOFTWARE

SUPPORT FROM MANAGEMENT

PASSIONATE DEVELOPERS

THE BEST TOOLS YOU CAN BUY

GREAT CULTURE WITH RESPECT & TRUST

Page 58: Coding Culture

INGREDIENTS FOR GREAT SOFTWARE

SUPPORT FROM MANAGEMENT

TALENTED, PASSIONATE DEVELOPERS

THE BEST TOOLS YOU CAN BUY

GREAT CULTURE WITH RESPECT & TRUST

Page 59: Coding Culture

CODING / CREATING MAKES US HAPPY

WHY DO WE CODE?GREAT SOFTWARE MAKES THE CUSTOMER HAPPY

Page 60: Coding Culture

DON’T FORGET YOUR CUSTOMER

Page 61: Coding Culture

EMMA

WILLIAM

DON’T FORGET YOUR CUSTOMER

Page 62: Coding Culture

EMMA

WILLIAM

FAKE

DON’T FORGET YOUR CUSTOMER

Page 63: Coding Culture

WE USE

PERSONAS

Page 64: Coding Culture
Page 65: Coding Culture

WE STICK THOSE ON THE WALL

Page 66: Coding Culture

REMINDS US WHO WE BUILD THE SOFTWARE FOR

Page 67: Coding Culture

WE CAN’T ESCAPE

Page 68: Coding Culture
Page 69: Coding Culture

BE

PASSIONATEABOUT YOUR SOFTWARE

YOU SPEND 8 HRS A DAY ON IT

Page 70: Coding Culture

YOUR PRODUCT

Page 71: Coding Culture

YOUR CODE

Page 72: Coding Culture

ENGINEERING VALUESHAVE

Page 73: Coding Culture

public boolean isTrue(boolean value) { if (value == true) { return true; } else { return false; } }

Page 74: Coding Culture

SAY ‘NO‘IF YOU FEEL IT WILL HARM THE CODE

Page 75: Coding Culture

DON’T WRITE CRAPPY CODE

Page 76: Coding Culture

for(int i=0;i< names.length;i++){ if (zipFile.getEntry(name[i])!=null){ return true; } } return false;

Page 77: Coding Culture

return Arrays.stream(names).anyMatch (name -> zipFile.getEntry(name) != null);

Page 78: Coding Culture

SCROLL BAR IS A SOLUTION…

Page 79: Coding Culture

TRY AND FIND BETTER WAYS

Page 80: Coding Culture

PRIMADONNA

Page 81: Coding Culture
Page 82: Coding Culture

TURN YOUR PASSION INTO PRODUCTS

Page 83: Coding Culture

DUKE NUKEMFOREVER

Page 84: Coding Culture

BALANCE ARCHITECTURE WITH GTD

Page 85: Coding Culture

ENGINEERING VALUESWRITE DOWN YOUR

SO YOU CAN REFER TO THEM

Page 86: Coding Culture

public void greatCode() { startCoding(); }

BALANCE YOUR PASSION

Page 87: Coding Culture

BEING ONE TEAMOF

4

CULTURE

Page 88: Coding Culture

12

Page 89: Coding Culture

12NATURAL TEAM SIZE

Page 90: Coding Culture

150

Page 91: Coding Culture

150DUNBAR’S NUMBER

Page 92: Coding Culture

150MAINTAIN STABLE RELATIONSHIP

Page 93: Coding Culture

SILO PROBLEM

Page 94: Coding Culture

SILO PROBLEM

LEGAL DEVELOPER

Page 95: Coding Culture

BRING PEOPLE TOGETHER

LEGAL DEVELOPER

Page 96: Coding Culture
Page 97: Coding Culture
Page 98: Coding Culture

INTRODUCE YOURSELF

Page 99: Coding Culture

SOME PERSONAL STUFF

Page 100: Coding Culture

START CONVERSATIONS

Page 101: Coding Culture

TRANSPARENCY

WINS FAILS DECISIONS QUESTIONS

Page 102: Coding Culture

WIN!

Page 103: Coding Culture

FAIL!

Page 104: Coding Culture

SUBJECT TO BE DISCUSSED

Page 105: Coding Culture

QUESTION FOR THE WHOLE COMPANY!

Page 106: Coding Culture

TRANSPARENCY ENEMIES

Page 107: Coding Culture

TRANSPARENCY ENEMIES

Page 108: Coding Culture

CHAT

Page 109: Coding Culture

CONNECT WITH THE TEAM CHAT

TEAM CHAT ROOMS

Page 110: Coding Culture

RECONNECT WITH THE TEAM CHATz z z

CHAT ROOM HISTORY

Page 111: Coding Culture

CONNECT YOUR SYSTEMS CHAT

INTEGRATIONS & BOTS

Page 112: Coding Culture

CONNECT THE WHOLE ORGANIZATION

CHAT

Page 113: Coding Culture
Page 114: Coding Culture

TRANSPARENCY

BRING PEOPLE TOGETHER

Page 115: Coding Culture

REMOTE OFFICE

TRANSPARENCY

Page 116: Coding Culture

PACIFIC STANDARD TIME CENTRAL EUROPEAN TIME

TRANSPARENCY

Page 117: Coding Culture

CFO CODER

TRANSPARENCY

Page 118: Coding Culture

SPREADS THE CULTURE

TRANSPARENCY

Page 119: Coding Culture
Page 120: Coding Culture

MEETINGS

Page 121: Coding Culture

Less people

LESS PEOPLE

Page 122: Coding Culture

SHARE RESULTS

IN A LIVING DOCUMENT

Page 123: Coding Culture

MAKER’S SCHEDULE

MANAGER’S SCHEDULE

Page 124: Coding Culture

INFORMAL MEETING SCHEDULE

Page 125: Coding Culture

SCALESTHAT

5

CULTURE

Page 126: Coding Culture

12

Page 127: Coding Culture

6-8

Page 128: Coding Culture

6-8PROGRAMMING TEAM SIZE

Page 129: Coding Culture

DESIGNER

Page 130: Coding Culture

DEVELOPER WITH DESIGN SKILLS

DESIGNER

Page 131: Coding Culture
Page 132: Coding Culture

6-8 6-8 6-8

ONE PRODUCT

Page 133: Coding Culture

6-8 6-8 6-8FRONT END PERFORMANCE DATABASE

ONE PRODUCT

Page 134: Coding Culture

COORDINATION PROBLEMS

MISSING CUSTOMER RELATION

Page 135: Coding Culture

6-8 6-8 6-8FRONT END PERFORMANCE DATABASE

Page 136: Coding Culture

6-8 6-8 6-8EASY START ENTERPRISE DEVELOPER TEAMS

Page 137: Coding Culture

6-8 6-8 6-8

USE TOOL X

DON’T USE A TOOL

Page 138: Coding Culture

6-8 6-8 6-8

MEET WHEN NECESSARYDAILY MEETINGS

Page 139: Coding Culture

6-8 6-8 6-8

AUTONOMY

Page 140: Coding Culture

6-8 6-8 6-8

NEED SUPPORT

Page 141: Coding Culture

YOU HAVE TO WAIT 2 SPRINTS WE HAVE DIFFERENT PRIORITIES

CAN WE GET SUPPORT FROM YOUR TEAM?

Page 142: Coding Culture

6-8 6-8 6-8

JUST DO IT

Page 143: Coding Culture

DOMOCRACY

Page 144: Coding Culture

AUTONOMY TRUST

DOMOCRACY

Page 145: Coding Culture

AUTONOMY TRANSPARENCY TRUST

DOMOCRACY

Page 146: Coding Culture
Page 147: Coding Culture

CHANGING OTHER PEOPLE’S CODE?THERE IS NOT SUCH THING

CODE REVIEWSWHO’S THE BEST TO CHECK IT?

Page 148: Coding Culture

AUTO SUGGEST

REVIEWERS

PREVIOUSLY CHANGED

FILES

Page 149: Coding Culture

AUTONOMY TRANSPARENCY TRUST

DOMOCRACYGIVES LIGHT WEIGHT CONTROL

Page 150: Coding Culture

DOMOCRACYSCALES BY KEEPING DEVELOPMENT SPEED

Page 151: Coding Culture

MAKE SURE NEW PEOPLE

FIT INTO YOUR CULTURE

Page 152: Coding Culture

BE PICKY!INSPECT CANDIDATES CAREFULLY

Page 153: Coding Culture

PROGRAMMING

EXPERIENCE

PASSIONBEER TEST

Page 154: Coding Culture

PROGRAMMING

EXPERIENCE

PASSIONPAVEMENT TEST

NO HIRE

Page 155: Coding Culture

PROGRAMMING

EXPERIENCE

PASSIONPAVEMENT TEST

HIRE

Page 156: Coding Culture

HARD TO GET INTO A STRONGCULTURE

Page 157: Coding Culture

HAVING A

BUDDY

Page 158: Coding Culture

BEER

BIKE

NEW ATLASSIAN

BEER

Page 159: Coding Culture

THE FIRST DAY AT WORKNOW DO SOMETHING

AWESOME!

Page 160: Coding Culture

MAKING MISTAKESLEARNING FROM

BUT WE CAN HELP SPEED IT UP A BIT

Page 161: Coding Culture

FIRST WEEKS

BOOTCAMPLOADING….

LESSONS BY EMPLOYEES

Page 162: Coding Culture
Page 163: Coding Culture

CULTUREBE ONE TEAM

BALANCE YOUR PASSION

AUTONOMY & TRUST

TRANSPARENCY

HAVE THE CUSTOMER IN MIND

Page 164: Coding Culture

CULTURE IS FLUFFY

BUT ALIVE

Page 165: Coding Culture

CULTUREBE ONE TEAM

BALANCE YOUR PASSION

AUTONOMY & TRUST

TRANSPARENCY

HAVE THE CUSTOMER IN MIND

Page 166: Coding Culture

CULTUREBE ONE TEAM

BALANCE YOUR PASSION

AUTONOMY & TRUST

OPEN COMPANY, NO BULLSHIT

HAVE THE CUSTOMER IN MIND

Page 167: Coding Culture

CULTUREBE ONE TEAM

BALANCE YOUR PASSION

OPEN COMPANY, NO BULLSHIT

BE THE CHANGE YOU SEEK

HAVE THE CUSTOMER IN MIND

Page 168: Coding Culture

CULTUREPLAY, AS A TEAM

BALANCE YOUR PASSION

OPEN COMPANY, NO BULLSHIT

BE THE CHANGE YOU SEEK

HAVE THE CUSTOMER IN MIND

Page 169: Coding Culture

CULTUREPLAY, AS A TEAM

OPEN COMPANY, NO BULLSHIT

BE THE CHANGE YOU SEEK

BUILD WITH HEART & BALANCE

HAVE THE CUSTOMER IN MIND

Page 170: Coding Culture

CULTUREPLAY, AS A TEAM

OPEN COMPANY, NO BULLSHIT

BE THE CHANGE YOU SEEK

BUILD WITH HEART & BALANCE

DON’T #@!% THE CUSTOMER

Page 171: Coding Culture

VALUESPLAY, AS A TEAM

OPEN COMPANY, NO BULLSHIT

BE THE CHANGE YOU SEEK

BUILD WITH HEART & BALANCE

DON’T #@!% THE CUSTOMER

Page 172: Coding Culture

GIVES YOUR CULTURE STABILITYVALUES

Page 173: Coding Culture

REMIND PEOPLE

Page 174: Coding Culture

ONE MORE THING

Page 175: Coding Culture

PRODUCTS COME & GO

Page 176: Coding Culture

PRODUCTS COME & GO

STAYSCULTURE

Page 177: Coding Culture

THANKSsvenpet.com/talks

@svenpet

FIND SLIDES HERE

Page 178: Coding Culture

PICTURES

http://www.flickr.com/photos/38190880@N06/5736623377 http://www.flickr.com/photos/11248435@N04/7502913456/ http://www.flickr.com/photos/73491156@N00/2739212947/ http://www.flickr.com/photos/60821278@N07/6291929645  http://www.flickr.com/photos/43322231@N07/4565750318/ http://www.flickr.com/photos/33227787@N05/12827891104 http://www.flickr.com/photos/85966598@N00/265719387 http://www.flickr.com/photos/23566085@N00/8396406730/ http://www.flickr.com/photos/20654194@N07/5130851019  http://www.flickr.com/photos/54289096@N00/204269498/  https://www.flickr.com/photos/35237092540@N01/3380860520 https://www.flickr.com/photos/56155476@N08/6659995783/ https://www.flickr.com/photos/29226759@N00/4583440116/ https://www.flickr.com/photos/kwl/3629264624 https://www.flickr.com/photos/matt_hintsa/2936348771/

Page 179: Coding Culture

https://www.flickr.com/photos/45429411@N00/5005135146/ https://www.flickr.com/photos/48865263@N00/5369298398/ https://www.flickr.com/photos/48865263@N00/5369298398/ https://www.flickr.com/photos/18548283@N00/8568402603/ https://www.flickr.com/photos/41864721@N00/2392037612/ https://www.flickr.com/photos/8977174@N08/2742657654/„ https://www.flickr.com/photos/85473033@N00/3329823685 https://www.flickr.com/photos/34316967@N04/6056999187/ http://i.stack.imgur.com/U0udS.jpg https://www.flickr.com/photos/markdodds/2335260459/ https://www.flickr.com/photos/lea-kim/8105644612 https://www.flickr.com/photos/neilmoralee/7997543466/ https://www.flickr.com/photos/neilmoralee/6924161862/ https://www.flickr.com/photos/sangudo/11223036166 https://www.flickr.com/photos/despotes/1598834337

PICTURESMORE

Page 180: Coding Culture

ICONSArrows designed by Juan Pablo Bravo from the Noun Project Unlink designed by Bri Piccari from the Noun Projec Money designed by Laurent Canivet from the Noun Project Happy designed by Tina Abi Hachem from the Noun Project Poop designed by Isabel Foo from the Noun Project Map designed by Mister Pixel from the Noun Project Ying Yang designed by Mister Pixel from the Noun Project Handle With Care designed by MarkieAnn Packer from the Noun Project Running designed by Kevin Laity from the Noun Project Winner designed by Juan Pablo Bravo from the Noun Project Skull designed by Tim Piper from the Noun Project

Page 181: Coding Culture

ICONS

Speech Bubble designed by Erin Standley from the Noun Project Pointer designed by Evan MacDonald from the Noun Project Heartbreak designed by Luis Prado from the Noun Project Friends designed by Luis Prado from the Noun Project Graduate Cap designed by Diego Naive from the Noun Project Calendar designed by Laurent Patain from the Noun Project House designed by Lil Squid from the Noun Project Exercise designed by Ilya Melichenko from the Noun Project Teacher designed by visualiaBCN from the Noun Project Megaphone designed by Bram van Rijen from the Noun Project Google Car designed by Guillaume Berry from the Noun Project Robot designed by Rutmer Zijlstra from the Noun Project

MORE