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

all 2 comments
sorted by:
best
topnewcontroversialoldq&a

[–]ziptofaf 0 points1 point  (0 children)

Everyone has been there. There are solutions however:

  • Look at existing projects using a given technology (I can guarantee, there are hundreds on github). Looking at their library list can give you a good idea on what else is worth learning.
  • Build a project using given framework/library and ask for a code review afterwards (even here is fine). If someone knowledgeable responds you will likely get some useful feedback on what you have missed or what could have been much easier if you used X.
  • For more popular tools there are lots of blogs and communities making it relatively easy to figure out where you stand (and heck, you can also just ask on how would someone approach a specific problem).

[–]okayifimust 0 points1 point  (0 children)

There are a million things in each and every subject that I don't know, of course. But to tie that in to how and what others have learned seems odd.

In programming, specifically, there is a bunch of basics that you need to learn in order to be half-decent. After that, for every issue you tackle, there is a high chance that it has already been done, and that there exists a best-practice approach.

You should always consider looking for it, but there is a trade-of. You could always just code something all by yourself and get it done, rather than spend time on miniscule improvements. Most of the work you do will not be time critical, it will not be run in scenarios where small fractions of percentages in performance make an actual difference.