that's fine, as long as its a lifetime supply idc what size it is lol
Adopt a Noobread for elightenment
35 Replies - 2467 Views - Last Post: 27 January 2010 - 09:37 PM
#32
Re: Adopt a Noob
Posted 09 January 2010 - 10:51 AM
or kitkats, but yeah I think a 30 - 50 post limit would give a pretty good group of people that actually know what they are getting into
#33
Re: Adopt a Noob
Posted 09 January 2010 - 11:23 AM
yes, this site is a little more large than game dev i think, and there are a lot of noobs out there who just like to have things handed to them, so maybe implementing some kind of way to see that the noob is actually making an effort before assigning him a mentor would be a good idea. The 50 posts rule sounds like an excellent idea, and i think it would work.
maybe we could pass this idea along to an admin now? If none of the admins haven't seen it already. I would love to see what they have to say about it.
maybe we could pass this idea along to an admin now? If none of the admins haven't seen it already. I would love to see what they have to say about it.
#34
Re: Adopt a Noob
Posted 09 January 2010 - 02:38 PM
The admins have already seen the idea- I've been looking at this thread the same time many of them have. In addition, I've already contacted Skyhawk133 to reccommend your idea personally. He said that it was a good idea, and that he and the rest of the Team are going to discuss it in greater detail. So hopefully, this will idea will be implemented on DIC.
#35
Re: Adopt a Noob
Posted 09 January 2010 - 02:58 PM
Not a bad idea, but if it comes to fruition and is mandatory for the "Moderator" badge I will need to change my status as I simply don't have the time (which is the reason I've regretfully turned down moderator twice).
#36
Re: Adopt a Noob
Posted 27 January 2010 - 09:37 PM
I don't really understand this idea. When a mentor gives their newb a project, the newb is expected to do it. Under this context, it's like homework or work. What spurs the newb into stretching their boundaries when they are simply given an assignment?
Couple this with the fact that the newb quite possibly does not have enough discipline to work on a project that they have no real personal interest in. Furthermore, the fact that it's not the newb's project stifles innovation and experimentation because the newb probably just wants to get the job done and move onto the next task.
I think a better approach is to make the existing 52 weeks of code more robust. This way they are focused on a technology, but not confined to a specific application type.
On the subject of bottlenecks, you could have multiple newbs assigned to a single mentor or something. However, then it really becomes more of a class I guess.
Fun Fact: Most times I've typed the term "newb" in a very long time.
Couple this with the fact that the newb quite possibly does not have enough discipline to work on a project that they have no real personal interest in. Furthermore, the fact that it's not the newb's project stifles innovation and experimentation because the newb probably just wants to get the job done and move onto the next task.
I think a better approach is to make the existing 52 weeks of code more robust. This way they are focused on a technology, but not confined to a specific application type.
On the subject of bottlenecks, you could have multiple newbs assigned to a single mentor or something. However, then it really becomes more of a class I guess.
Fun Fact: Most times I've typed the term "newb" in a very long time.
This post has been edited by MentalFloss: 27 January 2010 - 09:38 PM

New Topic/Question
This topic is locked



MultiQuote





|