100 Days of DX

100 Days of DX

are creating Developer eXperience content - 1 post every day for 100 days.

1

patron

$9

per month

I have a mission to educate business people about the needs of the developers.


The DX discussed here is mostly related to APIs and Platform Economy.
I've been writing a new book called Build for Developers for several months already. I had to build a habbit of writing at least something every day. First I tried to write one hour every day. That was overwhelming and I failed.

Now I write every day a short (around 500-1000 words) post about Developer eXperience. All the content probably helps in writing the book as well.

All posts are published at http://100daysdx.com

Why 100 days?

I noticed a friend of mine doing 100 designs challenge or something like that. I thought to try same thing with DX and writing.

What happens after 100 days?

I might be exhausted, but mostly likely I have learned a lot about DX and writing. At the same time, the 100 days acts as counter to book "Build for Developers" publishing. Aim is that after 100 days the book is ready.

The site stays alive until something peculiar happens. All the source will be in Github anyway, so it should be easy to maintain.
Tiers
Developer eXperience Patron
$10 or more per month

Backbone of better DX

Master Developer eXperience enabler
$20 or more per month

Master Developer eXperience enabler

I have a mission to educate business people about the needs of the developers.


The DX discussed here is mostly related to APIs and Platform Economy.
I've been writing a new book called Build for Developers for several months already. I had to build a habbit of writing at least something every day. First I tried to write one hour every day. That was overwhelming and I failed.

Now I write every day a short (around 500-1000 words) post about Developer eXperience. All the content probably helps in writing the book as well.

All posts are published at http://100daysdx.com

Why 100 days?

I noticed a friend of mine doing 100 designs challenge or something like that. I thought to try same thing with DX and writing.

What happens after 100 days?

I might be exhausted, but mostly likely I have learned a lot about DX and writing. At the same time, the 100 days acts as counter to book "Build for Developers" publishing. Aim is that after 100 days the book is ready.

The site stays alive until something peculiar happens. All the source will be in Github anyway, so it should be easy to maintain.

Recent posts by 100 Days of DX

Tiers
Developer eXperience Patron
$10 or more per month

Backbone of better DX

Master Developer eXperience enabler
$20 or more per month

Master Developer eXperience enabler