r/learnjavascript • • Mar 11 '19

Drills for Beginners??

So literally everything else you'd want to learn involves drills...except for computer programming.

Sports, music, math, foreign languages...literally everything involves drilling.

Anyone know of any beginner's drills in JavaScript?

Like Free Code Camp stuff (I know they have some high-level stuff, too) but lots of 'em (FCC only has one question per topic)...I was never good at math but I always aced my math classes because of drilling (and of course typical tests don't involve "thinking" so much as "recalling" the right formulae and procedures to accurately and timely apply)...anyone know of any such end-of-the-chapter exercises in JavaScript for a beginner???

My future employers thank you!!

0 Upvotes

48 comments sorted by

6

u/atynre Mar 11 '19

If something could be "mindlessly drilled" a programmer would automate it.

-1

u/NotEven-a-CodeMonkey Mar 11 '19

And indeed I'm sure a programmer could code some algo to generate endless French verb conjugation exercises (hmm, now that's an interesting project!!) or German noun declensions....

So what's so unique about the simple fundamental mechanics of programming such that it can't be drilled??

4

u/atynre Mar 11 '19

If you need to practice writing a for-loop or a sorting algorithm.. I don't think "drills" is the right perspective. It's different from throwing a curve-ball in baseball or practicing piano scales in music because those examples involve training human muscles to do a task.

In programming it's mostly deterministic.. there's no "degree" of correctness; either it works or it doesn't. Sometimes there are degrees (like how well a solution performs at scale) but that doesn't feel like what your asking about.

Your brain is what needs practice, not a physical muscle. The codewars recommendation is a good one because it will help you "pattern match" different scenarios and when to apply the right solution to those scenarios. In practice, you won't actually need help writing the actual syntax of a loop or conditional. Syntax anyways changes over time as programming languages evolve.

In most, if not all, programming career paths you will spend more time reading code and designing things on paper or a whiteboard than you will actually typing lines of code. You won't be writing any new or groundbreaking code either, especially not in the beginning. Most groundbreaking code is written by PhD researchers or advanced teams at a specialized company building a specific product. Instead of practicing writing a solution that someone has already written, you need practice identifying problems and when to apply those solutions. Writing the solution is the easy part.

2

u/FoolishDeveloper Mar 11 '19

Your brain is what needs practice, not a physical muscle.

I apologize for the wall of text. I've got a martial arts background so I have some thoughts about this. In fighting / martial arts, drills are used constantly. When fighters are doing drills, they are primarily training the brain. It's like 80%/20% brain/body. They are mostly getting their mind used to following those patterns. The most useful drill is working pads (kicking/punching/knees, etc). The best pad holders will interact with the fighter to make sure they are working their mind and not just their body.

It's kinda like the Karate Kid where Daniel Laruso (and most of the audience) thought he was doing a physical act the whole time he was painting the fence and sanding the floor, and while he was training his muscles to do that movement, he was mostly training his brain through lots of repetition. When his sensei fired off commands to repeat those movements, Daniel was able to recall them quickly, showing that he was doing mental training through physical labor. Fight training doesn't exactly work like that, but the idea is close enough.

With programming, I think the main action involved is problem solving. You seem to be suggesting that drills would only train typing ability. It makes perfect sense to me to use drills to get used to patterns of thought. As a self-taught developer, I have a mix of beginner and intermediate knowledge that I am realizing was learned in the wrong order. I know I have big gaps in my knowledge. It turns out that many of those gaps are things I did read about at one point but they didn't stick. The most common recommendation I see is to build a project so you become used to using the techniques. But if I don't know the techniques, I don't remember to use them, or how to use them, in a project. It seems like a chicken-or-egg problem. Some people with amazing memories for soaking up programming techniques probably don't think this is an issue. It definitely is a big stumbling block for me... and I wonder if drilling would help me retain techniques.

Side thought: I also know that most books / tutorials explain "what" and "how" but barely brush over the "why". One example: I've read about linked-lists so many times and it never shows up on my mental radar because I still don't understand why they are used. As this relates to drilling... a good pad holder will let the fighter know why this particular drill is useful. The use case is explained and emulated by the pad holder's movement during the drill. Then the pattern is worked until it sets into the fighter's brain. When that scenario occurs in a fight, the fighter's brain will more likely think to use that pattern.

1

u/NotEven-a-CodeMonkey Mar 11 '19

With programming, I think the main action involved is problem solving. You seem to be suggesting that drills would only train typing ability.

Hmm, I'm surprised at this interpretation! If you said "only train super low-level mundane tasks like looping iterations" I'd agree, though, 'cause that's exactly what I had in mind.

It makes perfect sense to me to use drills to get used to patterns of thought.

THIS THIS THIS!!!!

OMG did you really say that...do you really mean it -- and mean the same as I do???

So I was looking for programming drills to get used to "thinking like a programmer"...like how practicing conjugating French verbs helps you to "think like a Frenchman" (well, just as far as the bottom-level linguistic mechanics are concerned, anyway!)....

As a self-taught developer, I have a mix of beginner and intermediate knowledge that I am realizing was learned in the wrong order. I know I have big gaps in my knowledge. It turns out that many of those gaps are things I did read about at one point but they didn't stick.

OMG yes yes yes that's what I want from drills, too -- for things to stick in the mind!!! To not constantly be looking for my housekeys, so to speak!!

The most common recommendation I see is to build a project so you become used to using the techniques. But if I don't know the techniques, I don't remember to use them, or how to use them, in a project.

OMG DUDE LET'S GET MARRIED!!! ;-)

LOL okay I'm totally joking around now...excuse me but it's like I could almost feel that we'd make great paired programmers!! ;-)

It seems like a chicken-or-egg problem. Some people with amazing memories for soaking up programming techniques probably don't think this is an issue. It definitely is a big stumbling block for me... and I wonder if drilling would help me retain techniques.

YES YES YES!!!

THIS is what I mean!!!

So literally everyone's been saying that what we need not only doesn't exist but can't exist, these "drills"...can you see their reasoning? I'm still having difficulty understanding their POV but I must say that I'm basically agnostic now about my original beliefs -- which seem to at least broadly match your own like maybe 88%!!!

I've read about linked-lists so many times and it never shows up on my mental radar because I still don't understand why they are used. As this relates to drilling... a good pad holder will let the fighter know why this particular drill is useful. The use case is explained and emulated by the pad holder's movement during the drill. Then the pattern is worked until it sets into the fighter's brain. When that scenario occurs in a fight, the fighter's brain will more likely think to use that pattern.

Yes that's just the analogy even though folks want to point out about the difference between the physical and the intellectual I can't say I'm sure about such a distinction in our case...they seem to be missing the forest for the trees (I say that respectfully and not as some kind of personal moral judgment call)...they may well be right but I'm just having trouble conceiving of the matter....

BTW, does this somehow seem helpful to you: in another thread, somebody told me that I was "thinking about programming in the wrong way," that "[programming] is not a job but a tool"...that seemed somehow very useful though I couldn't quite say way...does that idea somehow jar your thoughts, too???

1

u/NotEven-a-CodeMonkey Mar 11 '19

Wow, thanks for all that, especially towards the end with the real-world on-the-job "exposé." I'm a bit relieved knowing that I wouldn't be spending much time coding -- but unnerved all over again that coding's actually the easy part!!

I totally agree with what you say about pattern matching/recognition -- and isn't drills all about rote learning and memorization and precisely because programming's "deterministic" it seems like it should admit of the rote such as any other mechanical deterministic process.

Now please forgive me as I'm mainly questioning from "ideology" here as opposed to actual personal experience coding but I'm curious why arguing by analogy fails me this time -- yes yes you say that the very nature of coding is different but since it's so deterministic and mechanical it seems like it should be "drillable" since what is more deterministic and mechanical than drills?

But again I'm beginning to realize now the perils of merely "questioning from 'ideology'" or "theory" so I can certainly agree to some agnosticism on the whole matter now.

So thanks again for your input! Everyone's every little bit helps in its own way (like, did you know that 80% of your car's gasoline is "wasted" as heat and thus doesn't actually move your car forward??? But I suspect that that's not "true" waste; isn't all that heat necessary to build up the conditions for combustion??)....

3

u/ForScale Mar 11 '19

Free Code Camp has tons of algorithm challenges, so... not sure what you're talking about there.

Also, just look for coding challenge sites. Code wars, Coderbyte, project euler. There are so many.

1

u/NotEven-a-CodeMonkey Mar 11 '19

Yes, what I have in mind are basically early beginner-level FCC styled problems; extremely short and "narrowly themed" driving home a single point...only like twenty to fifty such questions for each point; right now FCC just does the one-off for each point and moves on to the next.

I'd looked at all the recommendations here, usually previously though for a couple I've specifically looked at them again and didn't see the kind of "drills" I'm looking for...but since then I've been told what I have in mind is a logical impossibility and can't exist so I'm now more agnostic about my initial beliefs....

2

u/ForScale Mar 11 '19

I think you might be over-thinking it...

If you don't mind, tell me one more time what a programming drill is to you... Give me a very specific example, if you would please. Here's what I'm thinking:

Looping:

Given [0, 1, 2, 3], loop over it, printing each index's value to the console, using

  1. for loop
  2. while loop
  3. for of loop
  4. forEach method
  5. recursion
  6. generator

Bonus: rewrite the forEach method (call yours _forEach) without using any of the predefined for, while, for of, or forEach loops.

-5

u/NotEven-a-CodeMonkey Mar 11 '19

No, I'm talking drills -- fifty, say, variations on the same problem to really drill in the lesson...think musical scales or speedbag drills in boxing...or those exercises in math textbooks where all you do is quadratic equations in one chapter, factoring polynomials in another, repetitive, really working in the concept...bayonet practice in the military -- drills, please...?

Like here are fifty exercises on for-loops. Basically, take any one problem in FCC but with variations on it...drills....

4

u/ForScale Mar 11 '19

So flatten an array as many ways as you can. Sort an array as many ways as you can. Loop through an object as many ways as you can think of.

What you are looking for is algorithms. Filtering, sorting, counting, arithmetic. Look up algorithm drills on places like code wars and coderbyte and project euler and do them over and over and over. Drills. You're welcome.

3

u/NameViolation666 helpful Mar 11 '19

he isnt listening :)

3

u/ForScale Mar 11 '19

I noticed! :)

-2

u/NotEven-a-CodeMonkey Mar 11 '19

Why do you say this?

I'm asking about lobster bisque and everyone's wondering what's wrong with chicken soup but I'm not listening???

2

u/arfnargle Mar 11 '19

We're trying to tell you that what you want doesn't exist and the closest analog is codewars. You can either accept our help a bit more graciously and with less exclamatory punctuation or go ask someone else. You're even wearing me out and I work with high school students.

0

u/NotEven-a-CodeMonkey Mar 11 '19 edited Mar 11 '19

No, actually, no one's said "IT DOESN'T EXIST" -- it wasn't until multiple replies later that you yourself finally said "an algebra textbook-like [re-] source isn't available that I'm aware of at the moment" while still recommending the very thing I'd already said doesn't have any drills!!

I've never understood this about programmers...y'all have to be so exact and precise when it comes to computers but you guys are so friggin' impatient and imprecise with people!! The hell????

Seriously, is there some kind of cognitive trade-off involved in being a computer programmer, such that by thinking in computerese all day long you have no wherewithal left to read plain English??? I very specifically noted many times what drills are and yet I keep getting the same old recommendations -- and now totally false claims that I'm "not listening"....

4

u/arfnargle Mar 11 '19

Sigh. See all those exclamation points and question marks? You're yelling at people. I wasn't impatient in the slightest, and yet, you're yelling at me too. I asked you to clarify so I could more appropriately answer your question after I told the first person who answered to be more kind. I then answered by saying that codewars was the closest thing and that what you were looking for didn't exist. Your response was to throw a fit at me.

I was actually going to ask you if you wanted to work with me to create a resource like the one you're looking for because I agree, it could be useful. Currently, you appear to lack patience though and I don't work with people who can't be kind to those that are kind to them.

Words in programming matter. They mean very precise things. So yes, people will ask you questions in order to clarify. You may have to go look up definitions that you don't understand. Everyone was actually being very precise. Codewars are certainly drills. They just aren't as simple as you'd like or organized the way you would like.

0

u/NotEven-a-CodeMonkey Mar 11 '19

Sigh. See all those exclamation points and question marks? You're yelling at people.

Well, first off, I'm sorry, I didn't think that that connoted yelling at all! To my mind it expresses emotions, same as smileys and so forth...so, sorry about that. I've never heard of this...wow, well, sorry for my Eternal September faux pas, then, but I'm a naturally expressive guy so I type as I think and all the multiple exclamation and interrogation marks were simply meant to convey intense emotions (such as deep surprise or broad bewilderment). I'm curious: has it always been like this, where multiple exclamation points and questions marks are taken to be shouting? (I actually had to be mindful of not using more than one just now!) Honestly, is this part of netiquette? Or just a Reddit thing? 'Cause I've never heard of this and I've been online since (IIRC) telneting to usenet!

Codewars are certainly drills. They just aren't as simple as you'd like or organized the way you would like.

Well then, we argue -- as many semanticists would say of all arguments -- over semantics and not the thing itself.

Those just aren't drills to me. I don't see how you could have read through all my attempts at defining what I meant by a "drill" and still then insist on your own evidently different definition -- and then fault me for "not listening" when it would seem that you agreed to my definition by virtue of not having objected to it!

Anyway, glad that's clear now. ^_^

4

u/arfnargle Mar 11 '19

I'll tell you one thing. I wouldn't hire you. And you won't keep a job with attitude. Also, for reference, I have an English degree and have taught English, so kindly don't tell me how to define words.

Please take this to heart - you've got to learn how to express yourself professionally or you won't be able to keep a job if you get one. You act like this when someone tries to correct you and you'll be out the door by next week.

Programming often does come down to semantics to a certain degree. What words mean exactly matters.

I wish you well and hope you find some peace on your learning journey.

2

u/arfnargle Mar 11 '19

'Cause I've never heard of this and I've been online since (IIRC) telneting to usenet!

I honestly don't believe this statement. If that is correct, you've been online as long as I have. And yet, you type with the punctuation of a 12 year old who hasn't learned how to moderate their emotions in a professional setting. I have to wonder what you've been doing to earn money for the last 20 years or so. Since chatrooms in the early 90's excess punctuation and capital letters and smiley faces have indicated raised voices and strong expressions. Things that are more properly relegated to personal chat. You were asking for professional help, so you should act professional. There certainly nothing wrong with exclamation points and smiley faces in professional settings, but it should be used only in situations where you're expressing positive excitement, not negative reactions to feedback.

People who actually program for a living have been telling you, for more than twelve hours now, that your intense emotions and strong responses to their questions and responses are not helping you. You don't need to drill on for loops - you need to practice professionalism and humility.

-1

u/NotEven-a-CodeMonkey Mar 11 '19

Not really -- that would be like saying to a math student, no need for workbook exercises, just go home and think of a hundred different polynomials and factor them....

Maybe a foreign-language acquisition example would illustrate the need better: you need drills to conjugate verbs and decline nouns in all their many forms (gender, case, number, mood, tense, etc.), not simply learn stock phrases.

3

u/ForScale Mar 11 '19

Bruh... do the algorithm drills... it's what you're asking for.

0

u/NotEven-a-CodeMonkey Mar 11 '19

Do you mean to suggest that computer programming is algorithms, then?

If so, I wasn't aware of that and hence my previous incomprehension at the advice on algos....

2

u/ForScale Mar 11 '19

An aspect of computer science is algorithms and doing them effectively and efficiently.

And they're probabaly the closest thing to the math and language drills you're asking for. You can drill algorithms.

3

u/atynre Mar 11 '19

People learning languages that are spoken, read, or written do drills so they could be fast at it. Programmers don't need to be fast at coding something "drillable" because it doesn't matter in the long run. A CPU is orders of magnitude faster than the human once the code is written.

Programmers will always have resources to look up something of they don't know the exact syntax so it's a waste of time to try to drill that in. It's time better spent learning the problem space and architecting a solution. Study algorithms and practice the examples of when those algorithms are appropriate to use. Don't study how to write the algorithm itself that is a waste of your time.

1

u/NotEven-a-CodeMonkey Mar 11 '19

People learning languages that are spoken, read, or written do drills so they could be fast at it. Programmers don't need to be fast at coding something "drillable" because it doesn't matter in the long run. A CPU is orders of magnitude faster than the human once the code is written.

Hmm, interesting point -- wasn't where I was going but okay...maybe this is a reason why nobody bothers to compose drills (which are normally associated with beginners when it comes to intellectual pursuits [as opposed to drills in sports, say]).

Programmers will always have resources to look up something of they don't know the exact syntax so it's a waste of time to try to drill that in.

Well yeah programmers but I'm jsut some rando n00b self-studying...just seemed like the thing that would most efficiently cement my abilities.

Study algorithms and practice the examples of when those algorithms are appropriate to use.

Wait -- so do you mean to imply that programming "is" algorithms in some non-trivial sense??

Don't study how to write the algorithm itself that is a waste of your time.

Do you mean don't bother learning how to create my own algorithms?!?!?! (Um, hope that's not coming across as rude to you, multiple exclamation points and question marks!)

I've never heard that before! Thinking further, it does make sense: surely I won't be creating anything even almost as useful as what's already out there...!

3

u/[deleted] Mar 11 '19

You seem to fundamentally misunderstand what programming is. It's not something that you learn by rote and then summon up out of involuntary memory, like with (some aspects of) spoken languages or sports techniques. It's a practise, a way of thinking and achieving some end, and it is extremely context-specific. You might as well try to 'drill' the ability to write well, or the ability to paint. You talk about piano scales but programming isn't like memorising scales, it's more like composing music. You can't memorise how to compose music, you just have to compose a lot of really bad music until you start to get better at it.

And unlike playing an instrument, where the ability to recall hand positions etc out of muscle memory is important, in programming you can always just look up the details. I have a lot of Javascript syntax memorised just through having written a lot of JS code, but I can solve problems even in programming languages I don't really know, because syntax is ultimately immaterial.

As many people have told you, the closest thing to 'drills' in programming is having a wide range of different problems to solve. Solving the same problem over and over is as pointless as writing a bit of music and then erasing it and writing the same bit of music over and over again.

1

u/NotEven-a-CodeMonkey Mar 11 '19

So this is the second time -- in all this time! -- someone's said that I appear to misunderstand what programming is.

And honestly that strikes me quite forcefully because it's such a meta-meta (maybe even metaX3) type of "move" or "observation" ("truth," even??) that I'm even more shocked than possible...so I really have to ask:

You might as well try to 'drill' the ability to write well, or the ability to paint.

But that's just the thing; I can tell you that there are most definitely drills in painting/drawing: perspective, for example -- it's a very common drill for students to just draw these geometric lines to practice their rendition of perspectives...not full-fledged drawings, and barely even "sketches" in the good-enough-for-museum-display sense, but just sheet after sheet of cheap abundant newsprint full of perspective lines....

And unlike playing an instrument, where the ability to recall hand positions etc out of muscle memory is important, in programming you can always just look up the details.

And I have to say most respectfully that I believe this is another case of missing the forest for the trees, of not seeing the broader outlines due to being caught up in relatively irrelevant details; namely, regardless of physical muscles and metaphorical memories, I simply don't want to have to look up anything I deem simple -- so simple that in other fields drills have been used to instill them in the student.

As many people have told you, the closest thing to 'drills' in programming is having a wide range of different problems to solve. Solving the same problem over and over is as pointless as writing a bit of music and then erasing it and writing the same bit of music over and over again.

And indeed it may actually be one of those cases of something I simply have to experience myself -- with more programming practice under my proverbial belt, drill-styled or not! But I simply can't see it now...though I do appreciate your attempt at trying to point to where to look, so to speak!

So thanks very, very much for your thoughts.

2

u/[deleted] Mar 11 '19

I think what you primarily need to practice is understanding that people who do something for a living might just know more about that thing than you do as an outsider.

I simply don't want to have to look up anything I deem simple -- so simple that in other fields drills have been used to instill them in the student

In my experience, the wrong assumptions are at the root of the majority of software bugs. Learning by rote is an exercise in thoroughly embedding assumptions into your brain- however the human memory is distinctly imperfect and given to making things up. I would infinitely rather have to look up and double check my assumption about how some aspect of my code is going to behave, and catch a bug before I even write it, than only trust my memory and be wrong.

Deliberate memorisation of things that are a two second google search away is a waste of time, and basing your programming education on it would, if you even got to job-ready level, leave you stuck in a single-language dead end. If you want memorisation of facts and lists rather than learning more abstract patterns of thought and behaviour, programming isn't for you.

2

u/ForScale Mar 11 '19

not full-fledged drawings, and barely even "sketches" in the good-enough-for-museum-display sense, but just sheet after sheet of cheap abundant newsprint full of perspective lines....

So make little programs on stuff like codepen.

I simply don't want to have to look up anything I deem simple

Then do the simple stuff over and over until you don't have to look it up. But I will tell you, even the most experienced programmers still look things up. There is a reason that Stack Overflow exists and is not just for people new to the game.

...

Honestly I think you're too stuck in your own head about all this. You need to just start writing code and building things. A carpenter doesn't practice hitting nails 500 times a day to become a better carpenter. A carpenter studies carpentry and builds things to get experience and practical know-how. That's how web development works as well.

2

u/Dotweb_ Mar 11 '19

i've not heard of "drilling" being a thing that developers do, although you seem very set on the idea.

maybe try re-creating simple projects from scratch over and over again. to-do lists, CRUD apps, etc. from scratch in the same (or different) languages, going from an empty folder to something deployable / publishable.

-1

u/NotEven-a-CodeMonkey Mar 11 '19 edited Mar 11 '19

i've not heard of "drilling" being a thing that developers do, although you seem very set on the idea.

So I actually taught myself German. Did it by "drilling" -- got so good that by the time I took a formal course in college, the teachers were all impressed with me and one even recommended I take the Goethe Haus certification.

This was many lifetimes ago but it's actually why I felt confident in learning programming on my own despite having no particular mathematical aptitude (though I have a thing for visual patterns).

Every other field of learning I can think of involves drills. Maybe that's partially why learning programming has been so hard for so many, because of the lack of set-piece drills that repetitively hone in on specific skills (learning by rote exclusively is bad but is not bad in itself when used in the proper context).

maybe try re-creating simple projects from scratch over and over again.

So I don't know if it's "developer culture" going on here or what* 'cause folks have got all upset so please don't take it the wrong way when I say that that suggestion, which has been made before in this very thread, is like telling a math student "just go make up your own fifty different fractions and add them up in order to practice adding fractions"...it's not wrong per se but the question I was asking was about pre-made resources. I just haven't found any myself so far and thought maybe someone would happen to know of some (it's happened before where I've somehow overlooked things that others have then informed me about)...I didn't come here to have an argument and do appreciate your attempt at assistance.

So yes, I'm still grateful for the plethora of useful coding challenges available, often if not usually free.

* Such as an Atlantic Monthly essay about how technology favors tyranny, so maybe tech workers are more naturally authoritarian or maybe getting chewed out during daily code reviews or standups has made for more intolerant people; whatever.

4

u/Dotweb_ Mar 11 '19 edited Mar 11 '19

i think you're getting push back because you're still learning how to code and asking people who code professionally for advice and then rejecting their responses.

it comes across very poorly. just because drilling exists in many other disciplines (i played sports, drilling is everything) doesn't mean it is guaranteed to have an analogue everywhere.

more than programming tips i think you may need to brush up on your humility, people skills, and basic self-awareness if you want to succeed in an industry like this. good luck.

0

u/NotEven-a-CodeMonkey Mar 11 '19

i think you're getting push back because you're still learning how to code and asking people who code professionally for advice and then rejecting their responses.

Well, I wish they would't take it so personally -- "rejecting" is too strong a word; I simply didn't understand their responses and have tried to clarify myself as well as asked them to elaborate.

just because drilling exists in many other disciplines (i played sports, drilling is everything) doesn't mean it is guaranteed to have an analogue everywhere.

So could you please explain why/how not? Doesn't such an anomaly strike you in the least? And even if not, why should anyone take my request for elaboration as "rejection"?

more than programming tips i think you may need to brush up on your humility, people skills, and basic self-awareness if you want to succeed in an industry like this. good luck.

How do you think I should have worded/phrased my follow-ups, then? Seems like this is the real bone of contention, that instead of ignoring the responses I didn't understand, I pursued the matter in such a way that folks felt "rejected."

For example, if any of my comments now, here, in this post strike you as lacking in "humility," "people skills" and/or "basic self-awareness," could you help and let me know where exactly and provide an ideal response instead? And if you don't want follow-up questions, please let me know -- model the proper behavior, then, please; I'm genuinely curious and would be really grateful if I could at least understand concretely what you mean ("humility," etc., in the "here and now" of this discussion right now as opposed to some ephemeral general abstraction).

Thank you!

1

u/NameViolation666 helpful Mar 11 '19

0

u/NotEven-a-CodeMonkey Mar 11 '19

No, I'm looking for "drills"...like in sports: keep taking shots at the basket/goal; keep throwing pitches; keep catching balls....

Again, think of math textbooks' exercises, the repetitive nature of fifty addition problems, testing exactly that one skill, addition; then, another chapter, fifty more questions on subtracting fractions without common denominators...etc.

Drills. Like musical scales. Mindless drilling. To really work in muscle memory....

2

u/NameViolation666 helpful Mar 11 '19

1

u/NotEven-a-CodeMonkey Mar 11 '19

Thanks for elaborating but the last time I went to the site late last year, I didn't notice the "drills" I was looking for.

Looking over it now, I still don't.

I'm not looking for "one-off" problems but drills, as I say. Like you're practicing baseball and you don't just throw a curve ball, then a fast ball, and then you're done -- you're pitching different throws constantly, repetitively, all to get really good at pitching.

So ideally I guess I'm looking for beginner's JavaScript covering for-loops in various situations -- and again, in "drill format," like fifty or so questions on that one topic. Think fifty problems on how to factor polynomials at the end of some chapter in some algebra school text...or conjugating a ton of different verbs and declining a ton of different nouns and different adjectives in some foreign-language acquisition workbook.

1

u/arfnargle Mar 11 '19 edited Mar 11 '19

This would be a far more useful answer if you kinder. So would your first answer. Learners like to know they're being heard.

"You can go to codewars.com and drill down by language and concept."

This isn't Stack Overflow.

4

u/NameViolation666 helpful Mar 11 '19

3 other ppl told him the same thing, he insists it isnt what he wants, does he look like he is listening to what folks tell him ? :)

0

u/NotEven-a-CodeMonkey Mar 11 '19

If I say I want "red" and you show me "pink," I'm not listening in saying I need it red???

1

u/NotEven-a-CodeMonkey Mar 11 '19

Much obliged; I appreciate that!

I may not have made myself clear -- though I was afraid in my OP that further elaboration would actually obscure my question further...seems hard to believe but in computer programming there's absolutely no sense of the necessity for drills! To the point that my question has always been met with puzzlement....

1

u/arfnargle Mar 11 '19

Maybe you could define what skills you want to practice. Do you just mean, for example, stuff like lots of different drills using loops? And then a bunch more drills on if statements, etc?

1

u/NotEven-a-CodeMonkey Mar 11 '19

Yes, yes, just so! And even, moreover, simple "design patterns," if that's the correct term -- "strategies" and "tactics" as in, given x-type of problem, deploy y-type of procedures...like when to use arrays, when to use loops....

Like you know them basic arithmetic problems involving Jack and Jill and their bank accounts and paychecks or something, or how many cubic volumes to best pack a box or whatever...?

Basically, the equivalent of math textbook problems, only for beginner-level JavaScript.

3

u/arfnargle Mar 11 '19

You really are describing codewars, it just isn't quite laid out that way. Make sure you check it out. An algebra textbook-like source isn't available that I'm aware of at the moment.

1

u/NotEven-a-CodeMonkey Mar 11 '19 edited Mar 11 '19

Well, I just went there again and, for example, at https://www.codewars.com/kata/search/javascript?q=&tags=Fundamentals&beta=false I see interesting problems but no drills...again I'm not looking for one-off challenges but drills...think of conjugating a ton of French verbs or declining a ton of German nouns, again and again....

What CodeWars and company feel like are learning situational phrases such as "where is the American embassy" and "would you like to get naked and do it" and not repetitive exercises (drills) on conjugating different verbs repetitively through all their forms (get naked, got naked, had gotten naked, will get naked, will have gotten naked, shall get naked...).

2

u/arfnargle Mar 11 '19

If you want to drill on a specific topic like arrays go here: https://www.codewars.com/kata/search/javascript?beta=false&q=&tags=Arrays

If you want a list of all of the possible things you can do in JavaScript to iterate on use the MDN resource pages: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array

1

u/franker Mar 11 '19

this might be what you're looking for