Dos&Don’ts — Best DX Practices

Starting community effort to improve Designer-Developer Experience in cross-functional teams

Dear All,

I’ll be concise. Below you can find frequently updated and continuously incomplete list of Dos and Don’ts defined by ViewsDX community members and based on their professional experience. We are building it as we go, so feel encouraged to contribute! To suggest your practises and findings message me directly in Slack @tom or leave comment below this post.

The most recent update: 15 June 2017

Dos

Write meaningful code

Example, name your blocks:

Greeting is Text
text Hello World

Name your props:

Greeting is Text
text props.greeting

It’s faster to find and understand the composition of a view with meaningful block and props names.

Don’ts

Don’t be afraid to ask

Collaboration in best cross-functional teams is based on trust that failures and lack of knowledge will not be used against team members.

I don’t want to call myself an expert, I can only speak from my experience.

Learning process is crucial part of product and teams growth. Don’t assume it’s expected from you to know the answer at all times. Don’t be afraid to ask when you don’t know.

Remember, leaders ask questions.