DUX (or DevUX) is an interesting area of UX that places developers in its center and is most often disregarded on projects. Why is it important to have a good flow for your developers and how that impacts your project, general motivation around it and improves the end result are just some of the things we are going to talk about. And, no, it does not have anything to do with designer's concept of UX. ;)


Comments are closed.

Miro Svrtan at 22:44 on 15 Nov 2018

Thank you Vilim for talking about DUX (though I more prefer DX abbreviation) but I feel it might have been bit too generic. All of the things he spoke about, actually apply to any employee and they are not really developer specific.

I would suggest replacing some of the terms like 'guys' -> 'people' and 'firm' -> company, hands up was bit confusing (yeah thats why I had my hand up longer than expected : ).

Try sprinking personal experiences on each subject, making the talk more practical oriented. Try to avoid lists of facts, especially if you don't plan to go thru them but just have them there as it kept me reading them instead of listening to you.

I think that non-technical subjects are as important as technical ones, thank you for sharing it with us! I do feel I need to work on some DX things as well in my team..

Interesting topic.

This is just me, getting you, to improve, upon.

Talk louder (sometimes you mumbled a few words).

Less text, more talk.
Otherwise, as Miro mentioned, I as well tend to jump a lot and start reading text vs listening to you
(or make a pause so everyone reads the text and then continue with the talk).

At the end,
I realized that there hasn't been a meeting where you didn't have a talk (be it lightning or presentation),
so, kudoz for keeping the meetings alive and not-topicless.