I appreciate your feedback. Some background- the idea for
yoyobrain.com came from Will Bunker (match.com) who built the site to
help him switch from .net to web 2.0, because drilling with the
flashcards allowed him to work more efficiently so he didn't have to
look things up all the time... This method may work for some
developers, may not?
Yes, I agree. As mentioned I can speak only for myself and out of
I agree, the scrolling is important- we're going
to work on that.
It's a minor issue. Allowing to click the flip button and fix the card
The key feature of the site is the learning wizard
that will drill you on flashcards, but people seem to not find it when
they're on the site. Any suggestions on improving that usability
Only to add a very large text at top of the page
I just played around with it and came up with some points:
The questions are very short. It sometimes happened to me, that I
didn't get the idea out of the question, but found that I would have
known the answer.
Maybe the questions could be enhanced with some real code
examples, where the part that has to be answered is replaced
with question marks.
The answers are often not very helpful. Just stating syntax or
commands won't make anybody a developer. The answers should
explain the usage and maybe link to further documentation.
(and some code examples)
question: How do you search for a record by field value in table?
I often answered questions here in this forum that way. Only
to find, that people (mainly beginners) don't get it. The unavoidable
next question is:
I typed TableName.find_by_fieldname('value') in my code and got
this or that error, because they copied exactly that code.
You must explain, that TableName must be replaced by the name
of the model in use and fieldname by the name of the field
By the way the answer isn't accurate, it should be
since tablenames are plural and lowercase while models
are named singular and uppercase
Another example: Questions about Model relationship.
It's nice to know, that belongs_to defines a relation.
But there should be some info, how to set up the database tables
Or maybe questions could be chained?
Q: How define a many-to-one relationship?
Q2: What column does the many side need?
Q3: If defined Login belongs_to Client, how can you get all records
belonging to @client?
Best feature would be:
Take a real world oss project that makes use of as much
rails features as possible and base your questions/answers on
that and then let the answer point to a place in the code where this
feature is used in context.