Wikipedia is unfortunately biased in many areas that have any kind of controversy/disagreement. Education is one other topic where Wikipedia has a lot of bias. Wikipedia's "neutral point of view" idea is not only false but unobtainable.
Persistence wins over logic or evidence.
Not sure how this would work, but I think it would be worth researching/testing:
* Essentially have regional or clustered versions of events/history
For example, Afghanistan will have a different perspective on the US invasion than the US, but I think there’s value in seeing what the other thinks. (Does *not* necessarily imply one is more correct than the other)
Then have some sort of ranking system where (not sure how this would happen) votes can be had on which perspective is more correct. This hopefully would weed out the intense/false perspectives, but still gives people the ability to see the different ones.
A core problem we have is what constitutes misinformation/disinformation/propaganda/truth
I think the incorrect approach we’ve tried to take is either having a vetting committee/website that evaluates what is true, or just outright censorship. This fuels the actual conspiracy theories because they can use this as grounds for their cause (since, at times these vetting bodies are verifiably wrong)
We cannot withhold information, it travels too quickly and is easy to circumvent without total authoritarian control.
And all it takes is a few “valid” cases for the authoritarian seeds to be sown in the soil of good intentions
But we can generate unending oceans of bullshit. If you can't stop the truth, then make up unnumbered truths that wear down the most avid learners. Democracies vote in tyrants all the time, votes are easily bought in any number of ways.
You could do a similar 4GB RAM server setup for around $7/month using the Yunohost server app manager (free) + a VPS server host like Hetzner (or see lowendbox for others).
Logseq is free and open source https://logseq.com/
You have to sync yourself though (for now).
You can also publish to github pages.
My only issues are: they are focusing more on the desktop and (now) mobile apps, instead of the web app.
You can't quickly share items to the app or web version to quickly save links, etc.
They did have github integration built into the web version but are abandoning that to work on their own paid sync solution that isn't out yet. But you can manually sync the files as I mentioned.
For now I'm mainly sticking with a wiki but keeping an eye on developments to logseq and similar open source apps like Athens Research, Bangle, etc. See this twitter list of different knowledge management tools: https://twitter.com/i/lists/1396562498002825240
This Falstad animated circuit simulation has been the best at conceptually understanding what's going on in circuits:
https://falstad.com/circuit
Click on the 'Circuits' menu to see dozens of example circuits.
One issue with the hydraulic/fluid analogy is the "empty pipe" misconception - we forget or don't know that in electrical circuits, the circuit is a closed loop. An example of this misconception is that beginners sometimes think the current "wears out" as it goes along the wire. The Falstad simulation shows a line of moving dots that move faster or slower depending on the current - a little more like a train moving in a pipe - which helps counter this misconception, although it, too, isn't perfect. As a next level, I like showing animations/simulations that show the role of charge on the 'outside' of the wire in steering current flow, as well as magnetic fields surrounding the wire.
Those are exceptional. I remember gaining really nice math and physics intuition from his "applets" years ago. Yes, those started as Java applets if anyone still remembers those.
I'm pretty sure this is the one that I found while in undergrad physics. That diagram helped me gain a level of visual understanding that I hadn't obtained from hobby DC circuit tinkering. I remember feeling very grateful to exist during a time when an interactive web app could show me what would have taken N hours in an electronics lab to see in years prior. Many thanks Paul Falstad.
A "closed" circuit is just an open circuit plus a pump (electron pump or water pump).
Open circuits work fine if there is a powerful source of electricity (like a a radio) and a sink (like the Earth), and same for water (an icy comet crashing into a cliff, making a waterfall).
An open water circuit is full of stationary water.
Of course we have limits to how much we can do at once, but learning isn't like filling a bucket. Learning takes active work, effort. An analogy would be like saying 'weight lifting is easier with tiny weights' or 'don't lift too much weight.' Yes, but that's obvious, useless, and forgets the presumed goal of weight lifting, which requires putting in some effort. Similarly, you wouldn't force kids to listen to lectures about baseball or other sports and memorizing all the rules before letting them play.
Some of the other things mentioned on the poster article are false or only apply to rote, trivial learning. Remember most of this type of traditional psych research “includes participants who have no specific interest in learning the domain involved and who are also given a very short study time.”
Worked examples, like other passive learning situations, can cause an 'illusion of knowledge' - feeling like you know and understand, but not really.
Look at pre-worked answers, build rote knowledge, etc, before trying to solve problems? We learn more doing the exact opposite - see research on 'productive failure'. We learn best in context, when we have a need to learn.
Our intuitions about learning, teaching, etc, are often the exact opposite of reality. Here are just a couple of examples:
> Worked examples, like other passive learning situations, can cause an 'illusion of knowledge' - feeling like you know and understand, but not really.
As a former educator, my experience is in opposition to this. Students who looked at worked examples and then did practice problems improved their learning rapidly but often felt like they weren't learning that much. Students who worked really hard to "figure it out" and failed often felt really intense feelings of gratification and deep understanding but, in fact, often had a worse understanding of material. I learned (as one of the studies you links indicates) that feelings of deep understanding or learning aren't very correlated with educational outcomes except insofar as they keep you motivated.
For any flaws CLT has I've never seen an alternative theory of learning that seems provide guidance that is even half as effective, both professionally and personally (I've A|B tested both myself and students a fair bit).
I read the linked blog post and had the same thoughts. The author points out that CLT has some issues and then ... suggests pedagogy based on embodied cognition instead? Come on. CLT may seem like a quasi-ad hoc explanation of certain empirical data, but at least that empirical data exists, replicates, and provides concrete guidance in the classroom. The embodied cognition literature is a mess.
Also, I think it's wrong to position CLT as opposed to active learning techniques. As long as students don't have to "discover" any essential knowledge, everything is kosher according to CLT. So e.g. peer instruction is fine (e.g. the Mazur paper under the other blog post "Evidence for Various Research-based Instructional Strategies: Countering Critiques").
Tackling problems you haven't seen before is a skill you need to practice, and probably by far the most important skill students can learn in college. Going the other way, giving them nicely packaged solutions that they then repeat robs them of this valuable practice forever, they can never go back and do those problems with a naive mind again, and there aren't that many good problems that are feasible for people to try to solve on their own like this.
Of course, since you mostly test them how good they are at repeating given solutions you wont see this difference in classes. But this difference is very apparent to how they perform after they graduate, there is a reason many people with stellar grades are horrible in practice and vice versa. If you never practiced working under conditions where you don't know exactly how to solve things then you are basically worthless at solving anything people care about.
Edit: I'd say that it is great to learn your tools that way, you don't need to understand them perfectly. But your core competence is worth investing the effort to practice solving novel problems. A physicist can learn math by just repeating solved examples, but a mathematician probably should practice solving things on his own. And solving things yourself is a lot easier in undergrad than waiting for your PHD studies etc, it is the same kind of practice just way easier since the material is easier.
>Of course, since you mostly test them how good they are at repeating given solutions you wont see this difference in classes.
Very few teachers do this in math/science/technology classes. Teachers in these subjects understand that it's the design/problem solving process that is being taught, not the particular details which are only retained on an as-needed basis.
The reality is that formalized education is rote by design. The reason many on HN were frustrated by formal education is because they are not the average student. When you are two standard deviations from the mean in ability (in either direction), school will feel like a very painful grind. Most on HN could do the entire K-12 curriculum in a fraction of the time that it takes the average student. However, the education system is designed for the average student, who by definition are the majority. Students who learn very rapidly tend to get tired of the "training wheels" which are employed in formal education. However, only once you have seen the full spectrum of student ability from the other side as an educator do you understand why they are necessary.
The real sad part of all this is that we lie to students and tell them that computer science, which is by far the most abstract and cognitively demanding subject taught in school/college, can be learned and even mastered by all. This demeans the field of computing, and often can make students feel inadequate, as they are told that everyone finds computer science very easy to understand. When faced with a challenging concept, they then immediately feel that they are stupid for not understanding it immediately.
Cognitive load theory helps with difficult subjects like CS, because it prepares the learner for intense effort. When I teach CS, the first sentence I utter to my students is: "This is going to be the hardest subject you've ever taken. Prepare yourself, and don't give up."
What I would say is that the thing that makes a lesson good for helping students handle unfamiliar problems well directly hamper the more concrete skill acquisition within the lesson and so you don't want to mix the two uncritically. Student outcomes are much better when teachers are deliberate about which lessons are about handling unfamiliar concepts and which are about more concrete skills like adding fractions.
