01:41:05 RRSAgent has joined #mdn 01:41:05 logging to https://www.w3.org/2019/09/18-mdn-irc 01:41:09 RRSAgent, make log public 01:46:34 Meeting: Results from MDN Developer Survey 01:54:36 masonfreed has joined #mdn 01:55:07 tantek has joined #mdn 01:55:24 Zakim has joined #mdn 01:55:28 present+ 01:55:30 jgraham has joined #mdn 01:57:22 dom has joined #mdn 02:01:44 jorydotcom has joined #mdn 02:02:11 present+ 02:02:22 CharlesHall has joined #mdn 02:02:33 present+ 02:02:47 Present+ 02:02:52 Chair: Kadir Topal 02:05:08 zcorpan has joined #mdn 02:05:12 ScribeNick: jorydotcom 02:05:35 kadir: Introduces the MDN product advisory board 02:05:40 wendyreid has joined #mdn 02:05:41 zghadyali has joined #mdn 02:05:49 torgo has joined #mdn 02:06:14 JohnJansen has joined #mdn 02:06:19 ...they helped put this together as an effort of the MDN not just Mozilla 02:06:28 cbiesinger has joined #mdn 02:06:39 present+ 02:06:43 present+ 02:06:43 heejin has joined #mdn 02:06:45 Boaz has joined #mdn 02:06:45 Travis has joined #mdn 02:06:45 present+ 02:07:01 Dongwoo has joined #mdn 02:07:04 present+ 02:07:08 tobie has joined #mdn 02:07:14 ...recap is that we published this in July to reach a broad audience of developere and designers to understand their needs 02:07:19 karl has joined #mdn 02:07:21 ...the goal is to do this annually 02:07:33 RRSAgent, make minutes 02:07:33 I have made the request to generate https://www.w3.org/2019/09/18-mdn-minutes.html zcorpan 02:07:34 Dongwoo has joined #mdn 02:07:38 ...we want to understand and prioritize painpoints over time 02:08:23 ... 29 queations, localized into 8 languages. fielded for 4 weeks. 76k responses 02:08:30 RRSAgent, set logs public-visible 02:08:46 ...more than 28k people completed the survey from 173 countries 02:08:55 [thinking aloud - since survey will be run in northern Spring next year, we can expect an even broader set of participants compared to mid-Summer (northern)] 02:09:10 RRSAgent, make logs world-visible 02:09:11 ... 10k hours of developer time to complete 02:09:25 present+ 02:09:34 present+ 02:09:36 please paste a link to the report 02:09:42 present+ 02:09:45 ... the goal of the session is to walk through the survey and show you some results that we have 02:09:59 ... and understand what you want to see for segmentation 02:10:03 present+ 02:10:18 ... what can we do differently for the next version of the survey 02:10:23 ?? Can we share the report? 02:10:42 s/??/Dom_for_JohnJansen/ 02:10:49 kadir: not now, hope to have full public report published by end of October beginning of November 02:11:14 I have a question. Will the published report include the raw data of the responses to the survey? 02:11:17 RRSAgent, make minutes 02:11:17 I have made the request to generate https://www.w3.org/2019/09/18-mdn-minutes.html zcorpan 02:11:18 ... we had 29 questions, 2 were free form 02:11:21 qq+ zghadyali 02:11:27 q+ zghadyali 02:11:29 NavidZ_ has joined #mdn 02:11:37 ... they were aboutu paintpoints and what they would like to be able to do 02:12:01 ... we got more than 12k responses in 9 languages so we need more time to analyze, taht will be part of the full report 02:12:18 zghadyali: will the report be published with teh raw data? 02:12:37 q? 02:12:39 kevers has joined #mdn 02:12:44 kadir: we will only be able to do a pdf report for budget reasons, hope to have budget for next time 02:12:45 ack Zakim 02:12:53 ack zghadyali 02:13:19 ... this is the first iteration, we really just wanted to get it out so we can take into account 02:13:27 tobie: was it a legal problem? 02:13:54 kadir: no it was just technical. We didn't have the budget. so we didn't even ask legally. hope to have that next year 02:14:17 q+ to ask about backend development survey (http, server-side framework). 02:14:18 tobie: I think it would be valuable to consider next and last year's data if you can 02:14:18 kadir: makes sense! 02:14:38 karl: I read the survey 02:14:55 https://docs.google.com/spreadsheets/d/11jMfXWxw9bBZeCG8PYSoWsQZnRd2OBGSKSEwSF8nd0Q/edit#gid=0 - please add your IRC nicks here to help the scribe 02:15:06 ... I don't remember if there was a distinction between front and backend devs 02:15:09 q? 02:15:16 q+ 02:15:26 ack karl 02:15:26 karl, you wanted to ask about backend development survey (http, server-side framework). 02:15:36 ...did we focus enough on the questions/needs of backend devs? 02:15:53 kadir: maybe to answer this lets look at who we surveyd 02:16:18 ...we wanted to talk to people who actually code 02:16:27 ... that was the first disqualifying question. a pure vis designer wouldn't qualify 02:16:41 ...we do ask people about this later 02:16:59 Boaz : a format could be that we go through all of these now and have a group discussion after? 02:17:13 ... or the 5-10 key ones 02:17:22 +1 let's see the data!! 02:17:33 jgraham: keep talking and save questions for the end 02:18:18 kadir: I wanted to walk quickly through this and do some live segmentations, we might be able to do that for some of the segments that I have pre-prepped 02:18:32 ...the first one is the qualifying question: what do people do when they say they code/ code and design 02:19:04 ... how many hours to do you spend writing code? 80% spend more than 20 hours a week 02:19:41 ... next one is the type of dev you are. How do you ask whether you are a fe dev, backend, fullstack? there aren't shared established terms 02:20:19 ... it was a difficult disctintion to make, pilot testers got it but it may not have been clear in other langs 02:20:52 ...10% said they were backend developers. the main channel we sent this out in is MDN, so it makes sense we may not have reached a be community 02:20:59 s/be/backend 02:21:54 ???: is there a difference between vis design and code design 02:21:57 iank_ has joined #mdn 02:22:00 kadir: we hadn't thought about that 02:22:04 s/???/iank_/ 02:22:24 ... we saw roughly equally proportions JS/HTML/CSS 02:22:33 grisha has joined #mdn 02:22:38 ...50% had less than 2 years experience 02:23:02 twisniewski has joined #mdn 02:23:03 ... we think because of MDN's reach and the reach of the PAB we think this is pretty representative 02:23:11 ...this is something to keep in mind 02:23:41 [there may be a bias in that MDN attracts beginners more / more often than experienced people] 02:23:41 ...sometimes people don't know that browsers have versions, 02:24:04 so there is zero excuse for that experience demographic to not be aware of accessibility. 20+ years of a spec for it. 02:24:08 cathiechen has joined #mdn 02:24:19 ... keep this data in mind, about half have less than 2 years and 2/3rds have less than 5 02:24:35 ... something went wrong on this one (gender demo slide) 02:25:42 MikeSmith has joined #mdn 02:26:54 dontcallmeDOM has joined #mdn 02:27:05 ...Gender question, we did not get a good representation 86% of respondents identified as male. We think in the Us it should be 20% at least 02:27:09 RRSAgent, make minutes 02:27:09 I have made the request to generate https://www.w3.org/2019/09/18-mdn-minutes.html karl 02:27:21 ... for next year we want to do better and to compensate for this bias. 02:27:44 ... the needs and painpoints might look different. We hope to have budget to address this next year 02:27:52 fantasai has joined #mdn 02:28:14 RRSAgent, draft minutes 02:28:14 I have made the request to generate https://www.w3.org/2019/09/18-mdn-minutes.html dontcallmeDOM 02:28:19 ... what country do you live in? This is roughly what we expected with the expecption of Chinca 02:28:26 s/Chinca/china 02:28:53 ... it's hard to parse out to know if we got more participation because we localized into those languages. 02:29:09 ... this is not just US or EU, we really wanted diverse representation 02:30:01 dom: can people talk/tweet about this? 02:30:21 kadir: yes, recall that this is raw data and is just an indication of where things are going 02:30:34 ... so when you segment this you partially get different results 02:30:54 ... we already talked about the first 5 and how interop is a big problem 02:31:13 iank_ what are the plans for next year to understand the interop problems more? 02:31:27 s/iank_/iank_:/ 02:31:39 kadir: once we have analyzed the free form results we will see if there are additional items 02:31:50 ...interop is at the top of the list, let's look at the bottom 02:32:33 ... making sites accessible. This doesn't mean it's not a problem, it may mean that they don't focus on it or aware of the issues 02:32:43 ... they may not know what they don't know 02:32:53 ... that's why we do the interviews 02:33:16 ... keeping up with changes to the web platform, that was also a surprise. It's evidently not a big isssue 02:33:34 ...but compared to keeping up with the tools and frameworks, that was a bigger issue 02:33:56 iank_ : do you find the interop quesiton when you look at other countries? 02:34:32 joe: I wonder if people not keeping up with the platforms is related to not knowing that browsers have versions 02:34:58 zcorpan: most of the respondents are pretty new. If you've been a web dev for 1-5 years you may not id it as a problem 02:35:11 kadir: experience level is something that we segmented by 02:35:31 ...(shares slides) 02:35:51 ... it's the same thing. Interop is the biggest issue whether you just started or have been on for 10 years 02:36:01 ... also keeping up with the frameworks and tools 02:36:42 jgraham: arguably there's a degneracy between these because a lot of devs use frameworks to leverage the web platform 02:37:12 kadir: how many people use these vs. abstract that away? the platform underneath may not be of concern to you? 02:38:01 q+ did you collect data about framework usage? 02:38:03 ... we asked them how much do you think this represents your painpoints. 72% agree or strongly agree that this was a good representation 02:38:38 ... it makes us happy that this was a good representation for most people. that's why we had the free form to get the 8% who didn't agree 02:38:45 q+ to ask whether data about framework usage was collected? 02:39:01 ... a lot of it was related to non-tech issues like office politics, which may well top the list if we had added it 02:39:13 ... but this was not the purpose on the survey 02:39:48 ... how would you rate your overall satisfaction? 77% are satisfid or very satisfied. we are surprised because people like complaining! 02:39:57 ... most people are actua;ly quite happy 02:40:16 s/actua;ly/actually/ 02:40:19 ... we asked abotu whether they were doing this for personal or professional. most of them are doing it for their job 02:40:31 ... almost half the participants had a cs or engineering degree 02:40:48 ... almost everyone also added that they were self-taught 02:41:00 ... we didn't expect that 02:41:18 ...what team structure best describes your situation? d you work alone or with others? 02:41:44 ...66% said they work in an org with other devs, 10% said they are the sole dev in an org 02:41:57 ... which platforms do you target? this was another surprise 02:42:19 ... 95% target the desktop, only 62% target the mobile web? 02:42:26 iank_ is this skewed for the US? 02:42:31 kadir: no 02:42:49 ???: did you ask about enterprise vs. the consumer web? 02:42:52 kadir: no 02:43:13 ... what browsers do you support? 02:43:21 ... almost everyone came out with I hate IE 11 02:43:48 zghadyali has joined #mdn 02:44:16 s/???/cbiesinger/ 02:44:19 ... but there's more to it. the surprising thing is that safari is supported mroe than safarie IOS which is dispropotionate to marketshare 02:44:23 gsnedders has joined #mdn 02:45:00 ... follow up to that was which browswers give you the biggest issues? Chrome is at the top of the list, but keep in mind most people aren't supporting the other browsers 02:45:28 ... the chart is difficult to read, 02:45:57 ...when IE was ranked, it was the biggest issue. whereas with chrome it was ranked but gave the least problems 02:46:31 ... if people have to support safari IOS it is a bigger issue 02:47:10 ... the browser people primarily use for development is chrome, but we were surprised by chrome for andriod so we think there may be an issue with this question 02:47:29 ... so we look into whether this is understood 02:47:48 iank_ this doesn't surprise us 02:48:23 Kadir: we were looking to understand what dev tools people have, this may have been unclear in terms of how we phrased the question 02:48:31 ? will there be opportunity to provide feedback on the wording of the questions and research process for 2020? 02:48:37 ... which browsers do you test in? 02:49:00 ... chrome, firefox, edge 02:49:24 ... Installable web applications. this is about PWAs. when we asked about PWAs people didn't really know what it means 02:49:51 ... so we asked a question with a definitaion about PWAs, and with that definition, 29% said yes, and 10% said IDK 02:50:39 ... when a new tech becomes available what are your barriers for adoption. It's usually documentation but this was interop by far 02:51:22 gsnedders could people be interpretting outdated browsers / legacy browsers into this question? 02:51:30 kadir: maybe, we should look into that 02:51:40 q? 02:51:43 q+ 02:51:50 gsnedders: is tehre any support of implenation differences? 02:51:55 kadir: we should look into that 02:51:59 q+ 02:52:35 ... we asked people which languages they use, this is not a surprise. WASM was at 3%. this queastion was asked so we could segment other questions by it 02:52:46 Travis : what's the answer? 02:53:01 kadir: i don't know. this is a very early preview of thedataset 02:53:28 ... we asked where are you using JS? almost no one is using it on the server exclusively? 02:53:46 ... what are the biggest painpoints in JS development? feature adoption and performance 02:54:19 ... people don't really differentiate between the core lang and the APIS, and it changes over time 02:54:38 q? 02:55:06 ... next issue there are two things taht stand out. performance is not surprising. 02:55:40 ... with HTML, there were no pain points! second one is lack of browser adoption and inability to customize components. THere was a difference in Chinca 02:55:49 s/Chinca/China 02:56:19 ... in CSS it wasn't interop, it was challenges with layout. 02:56:26 q+ 02:56:42 also surprised to see no pain points here 02:56:44 [probably the webdevs having difficulties to implement what the designers ask them to do.] 02:56:52 [yeah] 02:56:55 ... WASM it was lack of debugging/tooling 02:57:27 zcorpan, close the queue 02:57:34 Zakim, close the queue 02:57:34 ok, zcorpan, the speaker queue is closed 02:57:35 Zakim, close the queue 02:57:35 ok, dontcallmeDOM, the speaker queue is closed 02:57:51 ... do you get to choose the tech you use? 2/3rds to get to choose what they use. Most people do get to choose. Devs are the right people to target 02:57:51 q? 02:57:56 ack Boaz 02:58:19 Boaz conversation of use cases. There's active work weher these insights are going to be useful 02:58:37 ... one of our action items was to be able to give efeedback on this next year so we can help compute priority 02:58:43 ... excited to collaborate with you on this 02:58:54 ack tobie 02:58:54 tobie, you wanted to ask whether data about framework usage was collected? 02:58:58 kadir: offer stands if you need a cut of this data so you can get if you need 02:59:24 tobie : it would be interesting to have data about specific JS and CSS frameworks? what frameworks and whether they are or not 02:59:40 kadir: shows the next sli ewith some of that data 02:59:55 ack JohnJansen 03:00:19 ... for next year we want to understand the buckets better so we can ask better questions 03:00:47 JohnJansen : the PWA data that you saw is verified by our crawler. It seems to match what you do. SW debugging is a bad experience. A future question could be more nuanced 03:00:51 ack jgraham 03:00:54 kadir: abso;luutely 03:01:37 jgraham: you were surprosed about the testing results. I think it depends what youmean by testing. Pulling apart those things would be better. Then you can pull out which tools you are using 03:02:02 ... I think for this kind of question it might be more interesting, if you say you're using CI which tool are you using 03:02:19 kadir: very true 03:02:39 ... this is very helpful, i fyou think of additional questions, go to your PAB person or come talk to me or email me at atopal@mozilla.org 03:02:59 ... any recommendations for the next iterations are welcome, and your feedback as well 03:03:06 RRSAgent, draft minutes 03:03:06 I have made the request to generate https://www.w3.org/2019/09/18-mdn-minutes.html dontcallmeDOM 03:03:23 RRSAgent, make minutes public 03:03:23 I'm logging. I don't understand 'make minutes public', gsnedders. Try /msg RRSAgent help 03:03:45 RRSAgent, make logs public 03:17:50 jorydotcom has joined #mdn 03:26:46 MikeSmith has left #mdn 03:28:31 torgo has joined #mdn 03:59:31 torgo has joined #mdn 04:22:10 tantek has joined #mdn 04:22:40 RRSAgent, make logs public 04:24:07 karl has joined #mdn 04:29:39 dontcallmeDOM has joined #mdn 04:30:13 torgo has joined #mdn 04:32:51 jorydotcom has joined #mdn 04:34:30 present+ 04:44:01 dom has left #mdn 04:50:43 jorydotcom has joined #mdn 04:51:13 karl has joined #mdn 05:04:43 torgo has joined #mdn 05:06:43 jorydotcom has joined #mdn 05:34:19 torgo has joined #mdn 05:34:23 torgo has left #mdn 05:36:22 tantek has joined #mdn 05:37:07 heejin has joined #mdn 05:39:06 RRSAgent, pointer? 05:39:06 See https://www.w3.org/2019/09/18-mdn-irc#T05-39-06 05:46:03 jorydotcom has joined #mdn 06:52:15 Zakim has left #mdn 07:34:25 atopal has joined #mdn 07:35:44 tantek has joined #mdn 07:53:36 jorydotcom has joined #mdn 08:00:15 jorydotc_ has joined #mdn 08:14:55 jgraham has left #mdn 08:19:11 karl has joined #mdn 08:21:47 karl has left #mdn 08:37:36 jorydotcom has joined #mdn 08:42:17 ryuichi has joined #mdn