difference between a script kiddie, programmer, computer scientist:
Script kiddie writes code without understanding the fundamentals of programming. Needs help not only understanding or solving the domain problem, but with using language features itself, using the appropriate data structure, choosing the appropriate algorithm, etc.
Programmer understands his language well, but may need occasional referencing of edge cases or less common features. Can appropriately choose known data structures and known algorithms, and re-implement them for custom behavior. Can be given a specification and code to that specification, generally without assistance (although assistance may result in a better solution).
Computer scientist might or might not understand his language well, but is primarily concerned with creating and understanding known and as-yet-unknown data structures and algorithms.
Poster above seems to be script kiddie tier.>>83823871
Figure it out on your own. THEN look up other people's solutions. Understand why their solutions are better than yours.
See above -- you're not expected to just magically know that the Sieve of Eratosthenes is an efficient way to find prime numbers, or to just figure that out on your own, but being told to find prime numbers using the Sieve of Eratosthenes, you should be able to look up the english description of the algorithm and implement the solution.
So, being told "find prime numbers," you'll program a naive solution. Then you're going to google "how to find prime numbers," and you'll see solutions using the sieve. You'll be like "Wtf is that" and find the wikipedia page. You'll understand it, do it yourself, benchmark your result. The other solutions are STILL faster than your's. Why? Oh, they're using a segmented sieve which is better on the cache -- let's try that way!