Page 43 of 134, showing 100 records out of 13,394 total, starting on record 4,201, ending on 4,300
# | Username | Text | |
---|---|---|---|
# | Jul 22nd 2009, 00:33 | jperras | it usually depends on whether or not you're familiar with calculus or not |
# | Jul 22nd 2009, 00:33 | pointlessjon | no worries, it's a big internet out there |
# | Jul 22nd 2009, 00:31 | jperras | not particularly; I took my stats classes in university for a math degree, so I'm not actually sure what they cover in those books. |
# | Jul 22nd 2009, 00:31 | pointlessjon | any particular recommendations? |
# | Jul 22nd 2009, 00:30 | pointlessjon | been on the computer too long today ;) |
# | Jul 22nd 2009, 00:30 | jperras | if you're really interested, there are a few books out there on statistics for programmers |
# | Jul 22nd 2009, 00:30 | pointlessjon | err |
# | Jul 22nd 2009, 00:30 | pointlessjon | the solution gets fuzzy around the solution for me |
# | Jul 22nd 2009, 00:29 | pointlessjon | yeah the problem is very clear |
# | Jul 22nd 2009, 00:28 | jperras | I tried to explain it in plain English terms in the wiki, iirc |
# | Jul 22nd 2009, 00:28 | jperras | yeah, they can be a bit dense in places |
# | Jul 22nd 2009, 00:27 | pointlessjon | indeed. I tried reading into the articles you linked to but it was beyond me |
# | Jul 22nd 2009, 00:26 | jperras | curiosity is mankind's greatest gift ;-) |
# | Jul 22nd 2009, 00:26 | pointlessjon | i'm mostly asking out of curiousity |
# | Jul 22nd 2009, 00:26 | pointlessjon | i see |
# | Jul 22nd 2009, 00:26 | jperras | really, it's just a mathematical construct to get a more accurate picture |
# | Jul 22nd 2009, 00:25 | pointlessjon | right |
# | Jul 22nd 2009, 00:25 | jperras | when it should really be closer to 1 |
# | Jul 22nd 2009, 00:25 | jperras | that outlier actually brings the mean to 1.8 |
# | Jul 22nd 2009, 00:25 | jperras | one person gives it 5 stars (e.g. person who wrote article) |
# | Jul 22nd 2009, 00:24 | jperras | 4 give it 1 star |
# | Jul 22nd 2009, 00:24 | jperras | 5 people rate an article |
# | Jul 22nd 2009, 00:24 | jperras | simple example: |
# | Jul 22nd 2009, 00:24 | jperras | pointlessjon: yeah, more like that |
# | Jul 22nd 2009, 00:24 | jperras | it's more of a modelization of how a rating system should function, based on a few assumptions |
# | Jul 22nd 2009, 00:24 | pointlessjon | will it simply be the numeric rating where the solution you were describing is just how we get there, or are we going to be looking more at charts |
# | Jul 22nd 2009, 00:23 | jperras | we're not really collecting statistics |
# | Jul 22nd 2009, 00:23 | pointlessjon | at the end of the day, what kind of statistics will we have? |
# | Jul 22nd 2009, 00:22 | jperras | pointlessjon: yup |
# | Jul 22nd 2009, 00:22 | pointlessjon | yeah let me step back -- you mentioned in the spec some crazy stuff about the ratings |
# | Jul 22nd 2009, 00:22 | jperras | gwoo: ha |
# | Jul 22nd 2009, 00:22 | jperras | gaussians and cake? |
# | Jul 22nd 2009, 00:22 | pointlessjon | what time is it anyway, like almost 2am? |
# | Jul 22nd 2009, 00:21 | jperras | I'm not following |
# | Jul 22nd 2009, 00:21 | pointlessjon | you're a fiend for the cake |
# | Jul 22nd 2009, 00:20 | pointlessjon | dude i just don't get gaussian distribution |
# | Jul 22nd 2009, 00:20 | gwoo | he missed us, all that time with his girlfriend.... |
# | Jul 22nd 2009, 00:20 | gwoo | hah |
# | Jul 22nd 2009, 00:19 | pointlessjon | but look how hardcore he is |
# | Jul 22nd 2009, 00:19 | jperras | I put a jet in your lag so you can jet while you lag, dawg |
# | Jul 22nd 2009, 00:19 | pointlessjon | that's what i was thinking |
# | Jul 22nd 2009, 00:19 | jperras | yo |
# | Jul 22nd 2009, 00:19 | gwoo | haa |
# | Jul 22nd 2009, 00:19 | gwoo | pointlessjon: he probably has some major jetlag |
# | Jul 22nd 2009, 00:19 | pointlessjon | jperras: yo dawg |
# | Jul 21st 2009, 21:20 | pointlessjon | !log |
# | Jul 21st 2009, 18:43 | pointlessjon | we're pretty much on the same page |
# | Jul 21st 2009, 18:43 | ProLoser|Work | gotta head out for a bit |
# | Jul 21st 2009, 18:43 | ProLoser|Work | and then you would almost use filters |
# | Jul 21st 2009, 18:42 | ProLoser|Work | i mean my suggestion almost seems like 2 sets of tags |
# | Jul 21st 2009, 18:42 | ProLoser|Work | honestly how you categorize can be completely arbitrary |
# | Jul 21st 2009, 18:42 | ProLoser|Work | that too can make a huge impact |
# | Jul 21st 2009, 18:42 | pointlessjon | i totally agree, andat the end of the day it's all user interface |
# | Jul 21st 2009, 18:42 | ProLoser|Work | it's up to you |
# | Jul 21st 2009, 18:42 | ProLoser|Work | crap i gotta go |
# | Jul 21st 2009, 18:42 | ProLoser|Work | so i suggested layers to create a degree of abstraction |
# | Jul 21st 2009, 18:41 | ProLoser|Work | when code/articles/tuts are all on the same topic, i would like to see them close together and easily referenceable |
# | Jul 21st 2009, 18:41 | ProLoser|Work | in that way i don't think code/articles/tuts/snippets should be the main heirarchy, cuz i don't like that much separation of content |
# | Jul 21st 2009, 18:40 | ProLoser|Work | or similar alternative hypothesis on the subject |
# | Jul 21st 2009, 18:40 | ProLoser|Work | i don't like the idea of a working peice of code being all the way in another section from discussion articles that may show what lead up to its creation |
# | Jul 21st 2009, 18:40 | ProLoser|Work | i just think when i'm looking at code, i can find nearby the relevent documentation on people who use it, examples of how it was used, or alternatives, snippets that led to it |
# | Jul 21st 2009, 18:39 | ProLoser|Work | but that's not the point i'm emphasizing |
# | Jul 21st 2009, 18:39 | ProLoser|Work | it's all very github/chaw like |
# | Jul 21st 2009, 18:39 | ProLoser|Work | it has a team of people working on it, it has an established code section |
# | Jul 21st 2009, 18:39 | ProLoser|Work | this is an example module |
# | Jul 21st 2009, 18:39 | ProLoser|Work | i am aiming to become as successful as drupal in this endeavor: http://drupal.org/project/modules?filters=tid:75andsolrsort=sort_title%20asc |
# | Jul 21st 2009, 18:38 | ProLoser|Work | well |
# | Jul 21st 2009, 18:38 | pointlessjon | I'm not sure I'm doing this justice -- I'll just have to show you something visually -- and perhaps you could do the same? |
# | Jul 21st 2009, 18:37 | ProLoser|Work | one-off documents? |
# | Jul 21st 2009, 18:37 | ProLoser|Work | i was requestion that they establish a form of linking |
# | Jul 21st 2009, 18:37 | pointlessjon | Articles, such as tools, tutorial, snippets, are more like one-off documents |
# | Jul 21st 2009, 18:37 | ProLoser|Work | i think that's clear they do not plan to mirror that on bakery 2 |
# | Jul 21st 2009, 18:36 | pointlessjon | including all those things |
# | Jul 21st 2009, 18:36 | pointlessjon | as i understand it, code items are becoming almost like github repos or chaw projects |
# | Jul 21st 2009, 18:36 | ProLoser|Work | so that usecases and documentation can be built up around it |
# | Jul 21st 2009, 18:36 | ProLoser|Work | i'm saying keep code near it's related articles |
# | Jul 21st 2009, 18:35 | ProLoser|Work | i'm not saying cause ambiguouty by calling everything code |
# | Jul 21st 2009, 18:35 | ProLoser|Work | this is an example of how it's used |
# | Jul 21st 2009, 18:35 | ProLoser|Work | this is the code to use |
# | Jul 21st 2009, 18:35 | pointlessjon | ah yes, code will have that |
# | Jul 21st 2009, 18:35 | ProLoser|Work | 'this is the tutorial |
# | Jul 21st 2009, 18:35 | ProLoser|Work | i know, so clearly break it apart into what is what |
# | Jul 21st 2009, 18:35 | pointlessjon | if it's in the article section, that article may contain 'code' in it for purposes of demonstration - but it is not meant to be dropped into an app |
# | Jul 21st 2009, 18:34 | ProLoser|Work | it would be nice to see the code, plus a tutorial on how to use it, plus snippets pertaining to the same vendor, plus an example of how it could be used, all be found in the same location |
# | Jul 21st 2009, 18:34 | pointlessjon | A content, item, node, etc. that is put in the code section contains portable, usable, stable code |
# | Jul 21st 2009, 18:34 | ProLoser|Work | and that's pretty much what we have now in bakery 1 |
# | Jul 21st 2009, 18:33 | ProLoser|Work | i thought you conceded that it creates a blob for the other areas that aren't code |
# | Jul 21st 2009, 18:33 | pointlessjon | exactly like the ticket (?) |
# | Jul 21st 2009, 18:33 | ProLoser|Work | so how would you organize them? |
# | Jul 21st 2009, 18:33 | ProLoser|Work | ? |
# | Jul 21st 2009, 18:33 | pointlessjon | err, just aren't |
# | Jul 21st 2009, 18:33 | pointlessjon | those are articles with examples of code in them |
# | Jul 21st 2009, 18:32 | pointlessjon | no, those just are categorized as code |
# | Jul 21st 2009, 18:32 | ProLoser|Work | ur leaving those out |
# | Jul 21st 2009, 18:32 | ProLoser|Work | what about articles, tuts, snippets? |
# | Jul 21st 2009, 18:32 | ProLoser|Work | so that's /code/ |
# | Jul 21st 2009, 18:32 | ProLoser|Work | okay |
# | Jul 21st 2009, 18:32 | pointlessjon | imho |
# | Jul 21st 2009, 18:32 | ProLoser|Work | component/behavior/helper makes sense for categorization, i just wanted to abstract it so that other items that ARENT code could be categorized in the same way |
# | Jul 21st 2009, 18:32 | pointlessjon | right. any code in the code section should be ready to be dropped into an app with little to no code modification, only implementation into your app |