These are chat archives for FreeCodeCamp/DataScience

2nd
Dec 2015
evaristoc
@evaristoc
Dec 02 2015 14:12
James Winegar
@jameswinegar
Dec 02 2015 17:31
@BerkeleyTrue: List of things I'd like to see, binary encoding for waypoint/bonfire/zipline/etc compeletion (0,1). Would be able to determine if people are skipping particular waypoints from these, by doing a continuous normalization.
by ID
evaristoc
@evaristoc
Dec 02 2015 18:42
hi @jameswinegar: why the binary encoding question to Berkeley, if I can ask? I don't understand... is it not already that implemented?
evaristoc
@evaristoc
Dec 02 2015 18:53
@faustor21 thanks for that point... I have heard about sails but I didn't know that...
CamperBot
@camperbot
Dec 02 2015 18:53
evaristoc sends brownie points to @faustor21 :sparkles: :thumbsup: :sparkles:
:star: 371 | @faustor21 | http://www.freecodecamp.com/faustor21
James Winegar
@jameswinegar
Dec 02 2015 18:59
@evaristoc I haven't tried to pull data yet, Berkeley said he'd like to know what type of data people would like to see a few days ago. That was just the simplest thing I could think of immediately.
evaristoc
@evaristoc
Dec 02 2015 19:05

@jameswinegar ok!... good point... there are very busy now with the new version, but I think they are thinking on an api for future developments... that means the pulled data could be done through something like an Ajax call, where the user will have access to the database using certain variables...

The number of people working on development is not huge so they are keeping some priorities over the main curriculum...

The main struggle right now is that without the api, projects like that one from roelver above (see the top100) are scrappers... they are then modifying certain parameters and more specially putting the database under pressure...

Those projects are fine, though... but better to handle them nicely and keeping in contact with FCC