Do you miss something on BrainKing.com and would you like to see it here? Post your request into this board! If there is a more specific board for the request, (i.e. game rule changes etc) then it should be posted and discussed on that specific board.
Modificado por goodbyebking (29. Janeiro 2007, 01:47:48)
It strikes me that for every improvement Fencer introduces to the site, several other requests invariably follow. It would be impossible to follow up on every suggestion for improvement, as they surface exponentially in relation to Fencer's power to make them happen. I have noticed the effectiveness of Fencer declaring that he would introduce ten new games by a certain date. Supplying an intention and a deadline helps to quell the waves of well-intended suggestions for even more games.
I propose that Fencer create a sort of calendar, where (let's say quarterly in a year) he establishes that a new game will be created on a regular schedule. On the same calendar, he could say that (on every Monday, let's say) a new feature could be added. It can help prioritize feature requests. After all, this method would limit the amount of new features to 52 a year. Such a posted calendar can help brainking members know when to expect change, so they have a date to check in and expect news. Primarily, though, it will afford Fencer some time. I think some players' responses to Fencer's statements have incited aggressive, arguementative discussion. Possibly part of that has been a result of F. being overwhelmed by an insatiable group of regular members. In order to abate Fencer's pressure brought on by this vast, open forum, what we need is, well, order. A calendar is an orderly, limiting structure.
Modificado por jessica (29. Janeiro 2007, 02:26:48)
emmett: i agree with that general idea but instead of posting everything that he has promised to do quarterly, it might be simpler to do it monthly or weekly.
jessica: I meant a new game quarterly. But you're right, it is a general idea. I think the point is that Fencer should do a little less in terms of quantity, but have more of a regular, public schedule, so that: a) we have reasonable expectations based on time and published comittment b) the pressure (which has started to show a little more) is more evenly distrubuted for Fencer.
A few things I've learned as a programmer: 1. Users ALWAYS want MORE. 2. A simple feature will always mushroom to a complex one. 3. There are no such things as bugs...only unwanted features! 4. Users HATE waiting for a new feature. 5. Users think they deserve to know the developer's Timeline/Schedule. 6. Timelines/Schedules are an "estimate" because Developement is creativity. 7. Developers make poor Users because they *think* they know how easy/quick a feature is to add. 8. The Developer knows what's best for the User
One thing I will say for Fencer. His site is remarkably free.
Fencer: I can see that. I guess I was trying to find a way to have people expect less. Every time there is a new improvement, there are complaints and even more requests, and even arguements, that outweigh the impact of the original improvement. It is disheartening after awhile to see so many arguements on the discussion boards. They are usually about feature requests.
emmett: People would never expect less. They just have to get used that some requests will be answered with a delay and some of them will never be answered at all.