Building developer community in Russia

Yelena Jetpyspayeva, @mursya DevRelCon 2016, London

past — BEM Program Manager @ Yandex, Moscow

present — Technology Marketing Manager @ Bright Computing, Amsterdam

about.me/mursya

Who am I?

2

Building BEM community in Russia and worldwide

What’s BEM? A little history Challenge accepted! BEM way Lessons we learned

We’ll talk about

3

What’s BEM?

4

5

6

7

Block__Element_Modifier = BEM

BEM as a methodology, invented at Yandex

BEM as a toolkit & a platform, all open source

BEM as a community

in 2015 BEM was team of 30 dev and 1 devrel

8

What’s BEM?

Little BEM history

10

Support someone else's code

Refactoring

Reuse

A lot of different frameworks & libs

No dependency management

Where pain comes from

11

12

13

14

15

16

17

18

cat_type_red

19

cat_state_wet

Block__Element_Modifier

Block__Element_Mod_ModValue

BEM naming convention

20

21

Methodology — idea and architecture

Toolbox — tools and SDK

Platform — Libraries, templates, client-side js, etc

Community

BEM

22

23

24

Challenge accepted!

26

27

28

29

External — build community that learn by themselves, become skilled enough to be hired, helps to develop, helps to test, develop together, own parts of BEM, locally & globally

Challenge

30

31

External — build community that learn by themselves, become skilled enough to be hired, helps to develop, helps to test, develop together, own parts of BEM, locally and globally

Internal — build infrastructure solution for services, win back client base, improve communication, be transparent, grow internal evangelists

Challenge

32

33

BEM ecosystem — self-sufficient

environment where processes work,

benefits are obvious, and community’s life is

not dependant on creators or evangelists

35

2 years 2 make

BEM way

External — build community that learn by themselves, become skilled enough to be hired, helps to develop, helps to test, develop together, own parts of BEM, locally & globally — 1st year

Internal — build for services, grow client base, improve communication, be transparent, grow internal evangelists — 2d year

Goals

38

› Core product team

› Yandex service teams — BEM users at work and in real life

› Developers outside Yandex — build with BEM / build BEM

Define ourselves

39

Market

› No developer success stories

› Events for awareness / hiring

› Only what comes from the West is good

40

Face the community, start to analyse

Lower quantity, better quality

From theory to practise

Move online as much as possible

Build infrastructure

Set the rules

Todo External

41

Stable and tested product

Build whats needed — no code without a client

Transparent client-oriented communication

Engagement of internal community

Todo Internal

42

Analyse everything — continuous survey

Internal audit — cost pro developer, hiring from the community

Meet and talk — discover user stories

Discovery

43

User focused bem.info redesign where community plays bigger role

Events, blog, community dev, external contributors

FORUM

en.bem.info to give it a global tint

social media + working channels (telegram)

Infrastructure & communication

44

From external conferences to own BEMups

From .ppt to live coding BEMups + webinars + lessons

From live coding BEMups to hackathons

From hackathons to NDA hackathons

Events

45

46

Product — quarter planning, public log, release scope, feedback

Communication — internal BEMups with success stories both from inside and outside

Inner BEM

47

Lessons learned

49

50

51

52

53

Aim global

Be trendy

Engage

Infrastructure matters

Devrel gives you more

But it needs more time

bem.info / github.com/bem-contrib

60

Head of BEM.Dev at Yandex

HTML/CSS/JS/BEM 24/7

tadatuta@yandex-team.ru

@tadatuta

github.com/tadatuta

Vladimir Grinenko

61

bem.info @bem_en #b_

mursya@gmail.com @mursya speakerdeck.com/mursya

telegram

Contacts

Yelena Jetpyspayeva Technology Product Marketing & Developer Relations

bit.ly/b_devrelcon

63