While some people prefer to get to know every tool in the toolbox before they start, others prefer to learn about them as they need them to solve a problem.
For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
Oldest comments (19)
I prefer to learn while I make.
There is so much widespread knowledge out there nowadays about so many programming technologies that it makes it really easy to find good learning materials and examples.
I like looking at examples, but I always try to understand why someone wrote code the way that they did. I try to comprehend someone else's thought process so that I can determine the clearest path forward.
I like to have a pretty deep amount of research before diving into a project and then learning nuances. The biggest thing I never want to run into is not knowing what I don't know, so I think doing a bunch of reading prior to starting a project helps map out the technology a bit before using it.
Like, conceptually, I know a bunch of ES6+ features. But before my summer project, I'd never used them, and all TypeScript examples assume you're a master of ES6, so I had to do some digging. Since I had that inkling of a foundation, I've been able to Google things more effectively. I probably read too much about Angular before jumping into a real project on it, but I think the TypeScript side of it had a healthy balance of knowing parts of it but just enough to know what to Google.
We are really similar hahaha, thanks for sharing your thoughts, Sine :D
I prefer a mix of both. Curiously, I find the harder subjects are easier for me to learn by making. Simply taking an example and learn by breaking it, then fixing what I broke has produced some quick results with sustained retention. This is then back filled by reading and expanding the example into the larger experience.
Code along classes have a place in this as well. Usually after the initial break fix cycle. Concurrently, there's a lot of additional reading on the subject.
I like to learn about big concepts, best practices, philosophy of the tech I’m about to use before diving into the project
And usually I learn how to really do things by making it
I believe having an idea of how to approach a project depending on the chosen technology and its design / architecture patterns is necessary to avoid a needed gigantic refactoring afterward
Learn while I make - sometimes it's frustrating, sometimes things just work, in all cases you learn a ton more than imagining to build something while learning
both actually , but i do love learn then make
Unless you start making you're not really learning. And I know I'm often so paralysed by choices that I just put off the making to another day and pointlessly consume another tutorial where I don't really have to take any responsibility.
My feelings exactly
I personally prefer making while learning, simply because if I start reading too much stuff without really knowing what I'm doing it doesn't stick and quickly forget as I start focusing on figuring out how to make something out of what I learned, and maybe remember bits as I write code. So I usually get a rough idea of what I need to do, then add to my knowledge as I find obstacles or feel like something can be done better.
A bit of both, but I really find making whilst I learn most productive. It tends to sink in more, plus learning before you make is often based on contrived examples that mean you don't really learn it until you start to make anyway!
That’s a great question and I actually do both. Going into a project without any prior knowledge it’s risky because you spend more time being stuck and frustrated than if you did some research first. This happened to me when I tried to get weather data from the OpenWeatherMap api, use axios, use vue and geolocation. I spent a good 3 days struggling with the results that I was getting because I did the bare minimum research.
On the upside I probably did learn way more struggling than getting a sure answer.
Now if you need to deliver something quickly it’s best to work with the tools you know to avoid wasting time trying figure out how to work with something - which usually could be fixed by a bit of research.
I guess the best would be a combination of both sides, use something new with something you know so you see progress and still struggle enough that you will learn something 😃