Starting today August 7th, 2024, in order to post in the Married Couples, Courting Couples, or Singles forums, you will not be allowed to post if you have your Marital status designated as private. Announcements will be made in the respective forums as well but please note that if yours is currently listed as Private, you will need to submit a ticket in the Support Area to have yours changed.
the most basic aspects should be taught.
the major problem is that the technology changes so rapidly, that by the time they reach uni, what they've learned could very well be obsolete.
certain languages, such as C and C++, have withstood the tests of time, but others, such as BASIC has fallen by the wayside long ago.
new languages are constantly being introduced, python, java, etc.
the one thing that hasn't changed all that much is the basic operations, and mechanisms, of a computer.
they still employ memory, logic gates, registers, base 2 operation, program counters, fetch/ execute cycles.
they are still architecturally the same as the ones i cut my teeth on.
so, my opinion about all of this, is to teach the hardware aspects and how computers execute code, and leave the software to uni level.
of course teaching current software at primary would be ok, but it could very well be obsolete by the time the students got to uni.
Read "The shallows" by N Carr, which argues that internet and technological gadgets are making it harder for us to concentrate. Jakob Nielsen's research showed that people read Web pages in an F pattern, showing how the internet affects our reading habit.
Some educational researches concluded that computers do not improve student performance.
yes, if you are talking concepts such as flowcharting.The basic paradigms of programming haven't changed much in 30+ years, and the basics of designing a solution in c++, java, Basic and numerous other languages are all fairly similar.
i would leave that to uni.The big differences are in the syntax and in the specific features and shortcuts that are built into each language - differences which are all easy enough to adapt to once you know the basics. Proper teaching of programming should allow the student to hop between many languages rather easily.
yes, if you are talking concepts such as flowcharting. a single flowchart would be applicable to all the languages you listed. so maybe flowcharting could be one of the things taught in primary. as for languages being similar, i must disagree. i know BASIC quite well, but would be hard pressed to translate BASIC code into C++ without a flow chart. even then i couldn't do it, because i don't know the syntax of C++.
i've been out of the loop for years.If that's the case, then I'd humbly submit that your programming skills are either rusty or not comprehensive. Translating a BASIC program into C++ should be pretty easy, unless you're using BASIC to do something weird that isn't allowed in c++, but even then, there should be a way to do it.
i'm old school.There may be a somewhat bigger different between old-school BASIC and the C++-esque languages, but there's less of a difference between the more modern Visual Basic and the rest.
Some countries are not only introducing computer lessons in primary schools,
they are also pushing for computer programming lessons for school children.
Do you agree ?
/* HelloWorld.java */
public class HelloWorld
{
public static void main(String[] args) {
System.out.println("Programming is good for people of all ages");
}
}
yes, if you are talking concepts such as flowcharting.
a single flowchart would be applicable to all the languages you listed.
so maybe flowcharting could be one of the things taught in primary.
as for languages being similar, i must disagree.
i know BASIC quite well, but would be hard pressed to translate BASIC code into C++ without a flow chart.
even then i couldn't do it, because i don't know the syntax of C++.
i would leave that to uni.
computer architecture and flowcharting should be enough for primary
If that's the case, then I'd humbly submit that your programming skills are either rusty or not comprehensive. Translating a BASIC program into C++ should be pretty easy, unless you're using BASIC to do something weird that isn't allowed in c++, but even then, there should be a way to do it.
There may be a somewhat bigger different between old-school BASIC and the C++-esque languages, but there's less of a difference between the more modern Visual Basic and the rest.
No, I don't really see the point of that. The first question that comes to mind then is "which language?". In this day and age, I guess that would be javascript.
But when you say "java script", you also say "html". The learning curve to start with any programming language to do something half usefull is VERY steep.
No high school is going to go through all that trouble in order to have students write something that is half usefull.
So instead, they'll either have to do really really boring and useless things, or they'll have a bunch of code handed to them which they will not understand and where they will simply have to write a little subroutine, at which point they will fail to see the bigger picture.
See, this is what I mean....
Typically, when high-school students would get an "introductory" course into programming, they'll have it like...what...an hour per week? PERHAPS 2?
Let's consider the above block of code.
I easily see 20 hours worth of teaching in those 3 lines.
What is "public"?
What is a "class"?
What's the difference between the outer block of '{..}' and the inner block of '{..}'?
What is "static"?
What is "void"?
What is "String"?
What is "[]"?
What does the "." mean in "System.out.println"
Why is the System.out... line closed by a ";" but not the other textual lines?
Answering those questions alone will take up a full trimester in a 1-hour course.
This is why I don't see the point in teaching an actual language.
It comes with SO MUCH baggage that only distracts from the actual goal of the course.
Let's also not forget... in the quote above we have only a couple lines of text.
Those lines don't do anything if written in notepad. Nope. You need an actual IDE to compile that stuff. You need to learn that IDE as well. You need to know what "compile" means. You need to deal with compilation errors (and somewhat know what they are). You need to be able to create a new solution in the IDE and know wich options to choose and which not to.
Either it will become a parrotting game and the students will have no clue what they are doing (and thus just blindly copying the teacher)... or the year will be over by the time a student knows enough to write and understand the 3 lines posted in that quote.
One is procedural code and the other is object oriented.
They are very different.
Yes, you can technically write procedural code in an object oriented language.
Still, you'll be confronted with things that are entirely unfamiliar to you if you've never used object orientation.
Absolutely, yes.Some countries are not only introducing computer lessons in primary schools,
they are also pushing for computer programming lessons for school children.
Do you agree ?
And then tell you to re-boot.How many Microsoft engineers does it take to change a light bulb?
...
None, they simply define darkness as the new standard.
While that's a fair concern, it's also one faced by many other disciplines including math and the hard sciences. I'd argue that a fundamental part of good teaching (of any subject) is figuring out how to present those components in a way that makes them easy to understand while also maintaining the relevance of the big picture. For example: Physics teaches you which forces act on a body, and Math teaches you how to add those forces together, but without any real context, the lessons can get boring and seem irrelevant. But once you ask the student to calculate the trajectory needed to fire a bullet at a moving object or to build a bridge under certain design restrictions, then the real-world applications become clear.
You don't have to teach most of that. For an intro class, you just tell them "do it this way; you'll learn about why to do that (or not to do it) later."
I suggest you check out this series of tutorial videos. This guy manages to hit all of the things you're worried about, because he's a good teacher.
https://www.microsoftvirtualacademy...es/c-fundamentals-for-absolute-beginners-8295
But when you say "java script", you also say "html". The learning curve to start with any programming language to do something half usefull is VERY steep.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?