3 ms·
You are right of course. The thing that many people miss is that learning isn't just one thing from, say, Hello World to a fully fledged application but it invo
by lbriner 5y ago
You are right of course. The thing that many people miss is that learning isn't just one thing from, say, Hello World to a fully fledged application but it involves learning diferent types of things in different orders.
For example, going straight-to-web can be hard since it involves several different concepts HTML is not CSS is not JS is not backend code (mostly!). So it is sometimes better to teach the basics in a desktop or console app using a single language with a single paradigm. Once they understand that, you could introduce other abstractions and explain why sometimes strong type-checking is useful and other times it is unecessary and time-wasting.
- syshum 5y agoWhile I can understand that approach, I do wonder if my origin to programming is common or not. I did not get in to programming to become a programmer. I learned programming to solve a problem I was having, in my case I did start out in web development in the 90's. I wanted a website that did something that I could not find premade software that did it in the way I wanted so I wrote my own. I also learned of open source and and other communities via this process. Had I just stuck with the commercial software solution I bought, that was terrible, I would have missed out on on a skill I eventually learned to love. The website (and company around it) I built was never successful, but from that experience I learned a skill that carried me to the career I now have