JavaScript for Impatient Programmers
91–100 of 104 posts
Re: JavaScript for Impatient Programmers
#92HN: Is today's hectic javascript making you tense and impatient? Me: Shut up and get to the point! Yeah, it's a futurama quote On topic: This is quite a list so I just clicked a random link and voila: > 7.1.1.3 Assertions > An assertion describes what the result of a computation is expected to look like and throws an exception if those expectations aren’t correct. For example, the following assertion states that the…
"7.1.1.3 Assertions .... It is part of a Node.js assertion API that is explained later in this book."
Re: JavaScript for Impatient Programmers
#93Re: JavaScript for Impatient Programmers
#94Earlier quoted context omitted.
I believe the JS criticism is more about the culture and ecosystem than the language itself. In short: Most if not all JS devs are more interested in playing with specific tools and APIs rather than dealing with and/or implementing programming patterns and principles. In the last decade "small modules" skyrocketed the popularity of NPM and a lot of people pushed the idea of "don't reinvent the wheel just 'npm install…
What is a meta framework? This is the first time I heard this term.
Re: JavaScript for Impatient Programmers
#95Earlier quoted context omitted.
Most stuff getting slung around, as the parent mentions, is rooted in the kind of development that relies on NPM-adjacent tooling. The two things you mention (Java and modern Web development, especially something modelled after another thing found on GitHub Pages) tend to be miles apart in this decade. Where does Java come in to it?
He may mean JavaScript not Java. I get a lot of we newbies asking referring to Java when they mean JavaScript. Especially when in the context of web development. For the parent: Java is completely different to JavaScript - the similarity is an accident of marketing and an original vision of the Web (in which most code was written in Java not JavaScript.)
Re: JavaScript for Impatient Programmers
#96Earlier quoted context omitted.
How much time would you say is fast enough to build a full front end and back end login/authentication system in nodeJS with any db ? I mean including throttling, pwd reset, forgot email/pwd, 2fa, confirmation email etc? Most of the tutorials are notoriously outdated and won't work bc dependencies, but I have build one such app. For someone who knows the J's basics , I mean
It depends on what exactly your app is because you might be able to use existing solutions. But my recommendation is Firebase or Supabase. These tools were basically designed for this type of webapp. I know a team of junior devs who created a production-app in a few weeks with Firebase. Firebase handles authentication, the database REST endpoint, and various other common webapp functionality, so that stuff is serious…
Re: JavaScript for Impatient Programmers
#97Earlier quoted context omitted.
> "My "real" advice for impatient programmers: just start programming, and every time you encounter a problem google it." In my experience, this is a terrible advice. However, many of my students follow this advice over my protests and only a handful of them actually learn anything at the end of a long masters program.
I agree. But over the years I've come to understand there are two kinds of learners; a) "I learn what I need to accomplish this task". This is observed as question/answer and only the simplest version of the answer is needed. So something like "how do I create a variable x and assign 10 into it. All he's looking for is x = 10 b) The second kind wants to understand the nuance of what's happening, so they can apply tha…
Re: JavaScript for Impatient Programmers
#98Earlier quoted context omitted.
Most stuff getting slung around, as the parent mentions, is rooted in the kind of development that relies on NPM-adjacent tooling. The two things you mention (Java and modern Web development, especially something modelled after another thing found on GitHub Pages) tend to be miles apart in this decade. Where does Java come in to it?
He may mean JavaScript not Java. I get a lot of we newbies asking referring to Java when they mean JavaScript. Especially when in the context of web development. For the parent: Java is completely different to JavaScript - the similarity is an accident of marketing and an original vision of the Web (in which most code was written in Java not JavaScript.)
Re: JavaScript for Impatient Programmers
#99Earlier quoted context omitted.
I agree. But over the years I've come to understand there are two kinds of learners; a) "I learn what I need to accomplish this task". This is observed as question/answer and only the simplest version of the answer is needed. So something like "how do I create a variable x and assign 10 into it. All he's looking for is x = 10 b) The second kind wants to understand the nuance of what's happening, so they can apply tha…
Great explanation! I wish I could influence the student intake but as a faculty I find it difficult to negotiate with the administrators whose objective function is to maximize the program enrollment! So I have accepted the status quo. Nonetheless I show them how I would solve a specific problem without going to Google at all.
I've [1] adopted the approach of meeting the student where they are answering their question, then trying to take them one step further. I try to encourage good habits, and at the same time ceasely mock bad habits (in a gentle, running-joke, kind of way.)
That said I also demonstrate the use of Google in answering a bunch of questions, for which the internet is overflowing with answers. Google is a fantastic resource and there's a lot of great stuff out there.
[1] I am not an academic, and my "students" are not in school. They are typically professionals, trained in another discipline, who were around when computers started, and there was no software so they had to write their own. They have 40 odd years of programming experience, but usually with zero formal training. Seeing individuals in this age-group make breakthroughs though is immensely rewarding.
Re: JavaScript for Impatient Programmers
#100Earlier quoted context omitted.
You cannot just google your way through it. There are times when you don't even know what to google. I remember as an early beginner being stuck with something that had to do with closures. I had no idea what was going on and didn't know what to google and when I asked questions on stackoverflow and reddit please started saying things about decorators and whatnot!!! It is only when I sat down and went through some ki…
I’m the complete opposite; I’ve yet to encounter a problem I couldn’t Google or bug someone in IRC about (and that’s the key). Sometimes you have to engage with someone else to solve a problem, but there are hundreds of people willing to do just that at literally any given time of day.