These are chat archives for FreeCodeCamp/DataScience
discussion on how we can use statistical methods to measure and improve the efficacy of http://freeCodeCamp.com
evaderei sends brownie points to @evaristoc :sparkles: :thumbsup: :sparkles:
DSR (DataScience Room) is an effort to gather campers of all levels and specializations willing to engage in discussion, collaboration and practice of data-related projects, with preference for using FCC data.
Tentative DSR site: http://evaristoc.github.io/FreeCodeCamp_DSR/
This week we have been working on the FCC Survey. See some work at the room or visit the issue page of the FCC Survey Repo. We are working on providing a clean Dataset for further analyses and visualizations. We are inviting EVERYONE to participate. Check advances here: FreeCodeCamp/2016-new-coder-survey#26
erictleung, bradd123, tufonas, Dawny33, psuedoCode, zcassini, Mashadim, QuincyLarson, sudeepnarkar, shian48263, theflametrooper, codengraphix, emilaasa, Evaderei, nitisha8086, jboxman, krisgesling, CaseyJunio, zydecat, abhisekp, evaristoc, profoundhub, joeybuczek, kymanikd, twolfe2, ozkoc, SamAI-Software, AdventureBear
(For a longer list check:
'ethnic', 'excel', 'graph', 'minority', 'jscript', 'pies', 'viz', 'dissertation', 'podcast', 'survey'
(For a word cloud check:
We are inviting EVERYONE to participate. Check advances here: FreeCodeCamp/2016-new-coder-survey#26 :+1:
@AyanGhatak I can answer that question: no sticking. Why? It is also very important for the project that campers show their abilities in manipulating and presenting data as much as using specific tools.
Better d3 as it is part of the FCC program as well as the possibilities that d3.js offers for customisation but I would suggest not prescription as d3 is not easy.
The only issue is project consolidation: if we all start working different technologies that will affect the ways we consolidate the final work which should consist in a small website of visualizations (@QuincyLarson idea). However we could try to deal with that later...
@AyanGhatak let us know about your project!
I think we need to prepare something that support this interesting article:
I think the author did a pretty good job in terms of showcasing some common dev related podcasts and some basic tool comparisons. In terms of data viz though, what were you thinking in terms of a project? -
maybe analyzing other data-points to infer lack of adoption of podcasts?
Less of a visualization but more of a keyword aggregator of podcasts (which I suppose one could create linkage and visualization)?
Maybe consume/use some API for podcasts (though it seems it's pretty limited based on cursory google search something like what this person-was looking to do) -
But maybe something like top (n) code related podcasts with matching keyword within episodes to maybe teaching concepts or frameworks/technologies within
fcc 'stable (e.g., 'react','node', 'mongo', 'callback(s)'? - So, chart plus access ability to go to site and grab podcast?
Don't know if any of this is close to the initial/spark idea - but what are your thoughts?