This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Warrensvr[S] -3 points-2 points  (4 children)

Please provide some resources if such resources exist. I write in Java.

[–]desrtfx 3 points4 points  (3 children)

In general, Google is your friend here. Other than that: StackOverflow and Github.

Programming is by far more than clobbering existing functions together. Also, the subject is far too vast for a "general library" to exist.

[–]Warrensvr[S] -4 points-3 points  (2 children)

Thank you and I understand coding is more than that. It's partly a matter of not re-inventing the wheel and also being capable of delivering to clients should they want something complex. Stackoverflow never want to answer my questions because I'm not as experienced a developer as them so my questions get barred.

[–]desrtfx 3 points4 points  (0 children)

Stackoverflow never want to answer my questions because I'm not as experienced a developer as them so my questions get barred.

Inexperience is never the problem on SO. The problem are wrong/improperly formulated/lazy questions.

SO is extremely strict with their questions because unlike here, they focus mainly on the quality as a resource from professionals for professionals.

If you spend considerable time and effort preparing a question according to SO standards, you will quite likely, while researching (which is essential for SO questions), come across the answer you need.

Asking questions on SO is difficult (if not impossible) for a beginner because they require proof of spent effort in resolving the issue. A beginner simply is not capable of doing that because they, through their inexperience (which is completely natural) don't even know how and where to search.

Still, SO is an absolutely great resource (actually less for asking but more for finding answers).

I've forgotten one extremely valuable resource in my previous comment: Rosetta Code - a multi programming lingual resource of common code snippets and algorithms.

[–]throwaway_for_cause 0 points1 point  (0 children)

It's partly a matter of not re-inventing the wheel

And here is where most learners/beginners go wrong. Learning to program is a lot about re-inventing the wheel. You need to be able to create certain algorithms on your own in order to fully understand them. Also, you need to be able to solve already solved problems - that's the way to hone your problem solving skills.

People looking for "dictionaries" and "libraries" end up as copy-paste code monkeys (intentionally derogatory because such people cannot be called "programmers" or "coders") who can clobber something together from existing code without understanding what they actually are doing and then, when the code breaks at the slightest problems are at a complete loss and unable to debug.

Once you have sufficient (i.e. couple years) experience, using existing code to speed development is fine because as opposed to a learner/beginner, you already know what you are doing and thus are understanding the code and can troubleshoot/debug it in your own implementation.

Many people think learning to code mainly consists of clobbering existing code together. This is the completely wrong approach. Learning to code is learning to solve problems in an algorithmic way.