Quote:
Originally Posted by Korvacs
Now your contradicting yourself again, now we should supply people with everything despite you previously agreeing that a tiered restricted system would be suitable.
Not to mention that we do have implementation available already, i was merely stating (Again) that this is how the community is now, the majority of us (I believe) would rather not hand out complete implementations for problems, rather sudo code and theory so that people have to atleast write it themselves. Your idea allows anyone to just C/P code into a project and go away knowing nothing at the end of it, not knowing how to debug it, now knowing how to improve on it, and not knowing where its flaws are.
Where as someone who has been given sudo code/theory can go away and write their own implementation, understands how the code works top to bottom, knows where its flaws are, and how to debug it and therefore how to improve on it in future.
Anyone (again) who is smart enough to be able to learn from existing implementation (such as yourself) is equally smart enough to be able to read some theory and write something fit for purpose.
|
Hah. Wrong. I don't think everything should be spoon fed.
That's cool you don't want to hand out implementations. Implementations can't be copy pasted necessarily. Even then, what the hell do you think has been happening all these years since the original CO emulator attempt? Everyone's been copy pasting nonstop. I remember when the questions were a flat out "this didn't work when I copied it to my source". I learn something better given something to play with. Something I can work with as is. I don't need to be given an entire source of a functional server to learn how to do it. When I go to learn something new, I find a practical application of a similar model. For instance, if I'm learning how to develop a packet queue system, I won't look specifically at a packet queue system in another program itself, I'll look around for any sort of queue system, learn how they work, compare and contrast, and then I'll make one (keyword make, not copy paste). All that is possible (and now I've learned exactly how it works) because there were implementations to be studied. When the packet encryption first came out oh so long ago, people were all saying things like "It's SSL" "It's Blowfish" "It's this, it's that". I was trying to keep up and my lack of SSL experience (and asm) prevented me from truly learning how to defeat the new system because there were conflicting messages, confusing ones, and no one willing to help. Not saying to code everything for the noobies and let them run amuck, but information is power. If you were to tell me exactly what something is, I could go figure out exactly how to pull it off without you giving me a line of code. But that's the issue there. No one was (still maybe?) willing to give out the smallest pieces of information. Therefore, I took a break.
Also, don't assume everyone thinks alike like I said already. Just because you might learn something one way doesn't mean others do the same. I am a very hands on learner. Theory and talking do nothing for me. I taught myself to code with a like 600 page C++ book and VC6.0. I read the basics of an if/else/functions and shit like that (though I had already known because of my prior experience with mIRC scripting) but beyond that, the rest I learned from typing in what I thought would work, and seeing the results in front of me. Being 13 didn't give me very many options to learn any other way. That's my story, I'm sure you really wanted to read it, but it does tie into my point. Plenty of people can be turned off and turned away just because you try to appeal to only one type of person. I sure was.
Quote:
Originally Posted by Korvacs
Hardly working against each other if no one has actually bothered to put the work in previously.....if the information just isnt available then its just not available,
|
I meant in general.