It's a statement that I agree with. There is just too much knowledge to know it all. These days there is a very real skill in knowing how to search i.e. a second order version of the above statement "you need to know where to find out how to look this up".
There are some really technical things ive done in the pasy that I couldn't do without a reference right now, but once I've got the reference I don't need to be reminded about low level details or edge cases or gotchas - it's all still there in my head I just need to see the road map and it will all come back to me.
Knowledge is so easily acquired these days that, while useful, it is not essential. I hire people with zero domain knowledge for that reason.
But more problematic is when people don’t know there’s a problem to google in the first place — it seems to do the job — which is usually resolved by both education and experience, but is ultimately a result if they don’t know what they don’t know.
The knowledge is generally out there, but you need to know you’re looking for it, and it’s only in the common/trivial problems that it’s so obvious that the compiler/tooling/customer just flat-out tells you you’ve missed something
Explain this to me by looking it up. https://imgur.com/Bj24AAR
I wouldn't want to go to doc that has to Google basic stuff.
Long term subconscious memory is where a lot of the connections happen. If your long term memory only knows where to find things without knowing them then that ability is stunted.
This is reasonable. E.g. sure a person can google how to build a house, but also sure that at planning phase they’ll mess and conflict with a half of good rules of thumb. Or forget them right after reading, because there is no habit nor knowledge in their head, and all that info is pretty transient. Pro is not the one who has read an article, but the one who can tell a couple of their own notes about it.
Otoh, gp is also correct that tests should check how you are doing in a real life situation. So maybe use both ways of testing?
This is how people become software engineers these days. They _constantly_ look stuff up, watch videos, and learn by doing that. Yes, you can still go to college and take tests that require you to "know" things, but honestly the vast majority of what I "knew" in college turned out to be short-term knowledge stored for tests.
By searching and learning, you
I learned by doing, initially, because I started learning programming with minimal resources before going to college and had to unlearn or restructure a lot of the knowledge I had gained up to that point once I did. I would probably have gotten there in the end, but it would have taken me a lot longer. The world was different then, though. Instead of easy access to info before going to college I was lucky to find a book somewhere that someone threw out that talked about things in a peripheral way that I needed to know, or ran into someone I could discuss things with that were as info-deprived as I was.
That's where my skepticism of this approach comes from, I guess. But I didn't live in a world where knowledge was at my fingertips from a very early age, so who knows?
Perhaps tests are to make sure that you are a going to be colleague worth consulting then? Yes, pure memorization and recall of facts is less valuable now than before, but knowing how to apply the facts available to you is still a skill worth having, and similarly worth testing. Those skills can also be assessed using written tests, and the potential for cheating is just as on memory tests.
what is the point in artificially creating a test situation where the student is isolated from resources she'll have at her disposal in real life
Let's take language learning as an example: do you consider a foreigner with a dictionary to be just as expressive as a native speaker? Perhaps there is value in testing the immediate knowledge of the student rather than their lookup skills?
Words are rarely restricted to their denotative (dictionary) meanings. There are often abstract, connotative meanings attached to them by speakers. For example, consider the following list of words.
Hello. Hi. Hey.
These words all have the same basic denotative meaning. They're all a greeting. Yet, there is a subtle connotation of formality which is rarely described in a dictionary.
These types of connotation are not often understood by beginning language learners. It's something they acquire with time and experience in using the language. While a teacher or search could share about the formalities, the language learner is still going to require time in applying those words in different contexts to fully understand these subtleties.
When I tell people a story about the history of the french revolution or something, I don't have the opportunity to go research it beforehand. I've already done that research, and I've already thought about those events for months or years, which gave me the opportunity to synthesize an insight or opinion I wish to share.
You don't get that if you don't know things in your head.
Yet I don't know a lick of Go. If I were to open up a Hello World tutorial for Go during the interview, would I honestly still have a shot?
You may be well aware of this, but you've essentially converged on the classical Chinese Room thought experiment [0]. It's usually applied to the philosophical question as to what does and does not constitute intelligence in the context of AI, but it's interesting how it is also applicable to what does and does not constitute knowledge in the context of learning.
I can envision many scenarios where a person needs to be quick on their feet and does not have time to look things up. Drivers, pilots, doctors, etc. Certification provides a lot of value to society.
The other point of testing is to separate wheat from chaff. To see if someone is disciplined enough to learn the material or see a task through. There are issues of going beyond the ideal amount of testing here, but not totally useless in my opinion.
But I'd argue that realistic test conditions correct for this automatically.
If your test is "write a program that does X within two hours" the programmer lacking core knowledge will fail.
If your test is "recite 20 programming paradigms from memory" you will have to check for "cheating"
> separate wheat from chaff
Wheat can demonstrate/use the knowledge, chaff can't. Why does it matter whether the knowledge is internal or external, assuming results are the same?
The point of a test is to check if you are capable on your own, and not piggybacking on someone elses intellect or hard work.
It is true, that in the real world, the resources available to use are infinitely larger than a classroom or a teaching setting. But your idea springs from lack of understanding about the true purpose of education, i.e, to groom children to think.
Alas, modern education has become a cesspool of rote learning, atleast in my country, India.
A big part of the valuable experience comes from having memories of similar situations, and thus a shortcut to the solution. In IT it can be similar to “indexing”, like I may remember reading a relevant stackoverflow question and I know how to find it again, but I don’t remember the exact solution.
But the catch is, to index something you first have to crawl through it. In medicine for example, there may not be much point in holding every single extreme-rare disease in memory, but having memorized them once and mostly forgotten them will lead a good doctor to know about it enough so that he/she can look it up on the odd chance it gets relevant. It will be only possible when he/she memorized it once back then.
My point is, there is a point in memorization (especially that it improves memory all-around - one will remember facts much easily after extensive learning), what should be better distinguished is facts that are to be learnt for life vs those that are only needed for a given test. It’s like unknowns vs unknown unknowns - the latter can be much worse and you don’t want someone like that as a colleague.
I'm going to claim that memory is only one part, maybe 1/3, of what I would like to examine for. Certainly in a job interview, but I also like university exams that include the parts below.
There's another huge part, *problem solving skills*. Working long enough to figure out which pieces of knowledge that you have apply to the situation.
There's another part, *making it work*. Software engineers deal with failures in practice (debugging) as well as theory (don't know how to do it). Sadly but interestingly, sometimes this is the point of failure for a student/examinee when they possess plenty of knowledge but don't know how to use it.
You can easily find an answer to "how do I enable file sharing on Windows." You cannot easily find an answer to "how do I design a website for an engineering firm which wants to increase it's inbound leads by 25%."
The former is a simple search away. The latter requires the integration of numerous abstract concepts which the shallows of a search engine cannot return.
Further, such an approach also limits our ability to create new knowledge.
As you can see, your argument is silly.
It's important to know things, in your head.
Of course I realize that you don't mean people shouldn't learn the alphabet or learn math, but where does one draw the line, where they don't have to learn stuff in their head?
But there are always holes in what one is even able to look up. Maybe not for everyone, but for most.
I just and a conversation the other day about this with someone and I was flabbergasted. The topic we discussed is that anyone can create a SQL database - anyone can. But do they normalize the database to 3rd or 4th normal form? He worked with a lot of corporations, and he said most companies don't have normalized databases. In university, that was a basic thing that they taught a semester course on that. An entire semester. Not to memorize anything, but just the general concepts.
Someone can learn how to create an incorrectly structured database easily, but they don't even know about normalization, so how can you even look it up in the first place? And even if you do, somehow, learn what it is and look it up, I took the class for an entire semester. How is someone going to learn it in 15 minutes by looking it up? I looked up stuff in the book, too, and got info from the professor, and it took me an entire semester, and everyone else in the class, too. Unless you're calling us all dummies.
There's all kinds of stuff like that. You don't know how to look up something if you don't even know it exists to look up, and it is not obvious.
Unfortunately, in order to progress to more advanced topics, you need to understand the basics yourself. It's not sufficient to just be able to research it online. This is true in every field I can think of. That's why you can't just give people online access for every kind of test.
In my opinion, cheating from internet access or outside resources is not the problem, cheating by gogling exact problems is.
Most of my upper classes were heavily weighted towards group projects anyway.
Teachers don't care about students looking into their books/pdf, what they want to prevent is them getting the answers from a snapchat group.
I definitely think that is a better way to test.
Our methods of teaching come from a worldview in which the information stored in your head is your only resource. That wasn't true in the past where you could consult colleagues, look things up in books or call experts - and it's certainly not true now that everyone carries the entire knowledge of humankind around in their pocket.
So what is the point in artificially creating a test situation where the student is isolated from resources she'll have at her disposal in real life? How about instead, we create (whatever the plural of curriculum is) that teach you how to use these resources efficiently and test you on how well you perform using all the tools that will be at your disposal in your actual job as well?