discussion on how we can use statistical methods to measure and improve the efficacy of http://freeCodeCamp.com
@luishendix92: I have also a python script... would you like to talk about this? Shall we make a skype or something?
@/all: everyone is also invited to contribute! Make teams, create projects!
@luishendrix92 let's keep talking! I will make a note of this for the next Digest, we could make something interesting with this...
Just one thing: I saw the codepen... what is it purpose, if you can tell me?
@luishendrix92, @vicky002 : it is hard to get it because we only have access to heroku at the moment, but I could say we can try to build a recommender?
Something like, after pasting your code in a form as the @luishendrix92's codepen, the recommender could show SIMILAR solutions which could be ordered according to easy-to-get parameters, like length... Very much like: "Check what other people using similar techniques as you did for this bonfire..."
for or while loops, functional programming style, if vs switch, etc. However, I think it needs human intervention to label the data (recognizing functional programming is not so straight forward and for and while loops are not always used with the same intention)
@jbmartinez, @luishendrix92, @vicky002, @jameswinegar indeed: we must cluster/classify the solutions somehow and might need some human intervention for sure... perhaps not entirely for a hackaton for people who just only want to code, but for a good project for an API type that could...
Anyway, we could see... at least we have a first idea...
@jbmartinez
the algorithm would be a nice way to how other people solved a problem after submitting their solution. Some sites just let the user browse for other solutions, which is not fancy but it's effective
what do you mean?
@jameswinegar about:
what features are relevant
That would be emerging features, likely specific per bonfire... it won't be an exact thing: it is a recommender, so it will bring you to similar solutions to comparing...
The only thing is it is a post-recommender, so it is not recommending anything, so probably the name recommender is actually wrongly used here...
But we could suggest how similar the solutions are, without saying anything about efficiency though...
For classifying, we could end up using an ad-hoc classes in case we are lack of any other more-formal classes...
Anyway: I will be talking to @vicky002 soon... I also suggested him other project...
And well: @/all are invited to participate!
https://bonfirefetcher-luishendrix92.c9users.io/luishendrix92
@luishendrix92 sound good... but I think I can discern some pitfalls in the whole project...
For example: to load a sample side by side the user should have first found one to compare...
My proposal would be to classify all them in advance (eg. functional-like solutions, ES6 solutions), and then let the user to pick one classification of interest where several algos could be found...
The person can select any or an specific one of that group, according to his/her preferred coding style, and suggest a comparison...
We could eventually add a "like" or "views" so we can use also that as a classifier for the most popular algos, and the person can compare with those accordingly...
Reading the wikipedia... hilarious! Explaining to the duck!!!
Yea... I don't think we are going to get to a corrector as I suggested...
Giving it a second thought, that would be like making an editor for JS in the first place, and that is for me like re-inventing the wheel...
IMO it could be more like a more elaborated extension of the CodeReview chatroom...
@jbmartinez, @luishendrix92
In that chatroom people meet to share further developments and improvements to their codes...
We could bring that to another level: instead of a chatroom, an API... Actually both...
Obviously I need to work on getting rid of the CSS/jquery waypoints