|
|
|
|
|
by throwaway1183
996 days ago
|
|
> Learning is part of the job. I don't know what to say. For example, I recently designed some webpage or made some prototype app using X framework in Y language. Do you consider that I learnt something? I don't know, I feel like that isn't learning. I just made the thing work because I read some stuff, processed information and did some hit and trial. Compared that to something like "ah hah!" moments; those are extremely rare at work. It only happens at debugging. The reason why I am stating it is because I have forgotten a lot of these things. What stuck with me are the basics and foundations and it took years to be reinforced. I doubt you will find a job where you get to learn in a proper way. |
|
I run into "average" developers who won't even look for an answer. They don't realize their problem has probably been solved many, many times before. They'll attempt to reinvent the wheel instead of using a proven solution like an existing library. They'll literally stare at an error message, not paste it into Google, then tell the team they're "blocked" a couple days later. How about asking someone?
What is the "proper way" of learning to you? Do you want to be taught in a classroom?