Scope highlighting is a great idea too - I tried teaching some people to code and scopes seem to be as difficult a concept as classes are. The UML view of the classes is a nice way to connect something very abstract with the actual code. I'd love to see some data, because my personal feelings probably aren't of much use.īlueJ does have a number of concepts that can be useful in the beginning. I'm not sure what the proper didactic concept is to teach programming.
#Writing java using netbeans vs bluej how to#
How to isolate specific issues, watches, off by one errors, byref/byval issues, top down order of operations issues, figuring out how a language handles a datatype mismatch etc. I think programming curriculums should include an entire section on debugging. edit- at least higher-ish level languages, variables, limits, etc, how things are passed around and referenced change, but the basic function and control structures if then else switch case, for,do,etc are all roughly the same. Once you get your first language under your belt the other languages come easier, as most of them are vastly similar. Having taken programming 2 in high school (java) then Liberty basic in freshman year in college and then back to c/c++ again in college I can say without a doubt programming classes massively undervalue debugging skills. I had already learned how to make my own "debugger" using console out, but being able to add watches and breakpoints and actually see the internals of my program shift about as I stepped through it was awesome.ĭespite having a proper IDE, my Programming 1 class spent all of 1 class period on how to use the debugger built into visual studio.
Programming 1 at my highschool was based on visual. The next year I took my first "formal" programming class. I started programming in high school, probably around 9th grade, I picked up a book on c at B&N, it was written with devC++ in mind as the IDE.
Use tab key for indentation, have the IDE insert whatever is configured for the project/org, be it tabs or spaces (e.g. To me code formatting feels about the same as the tabs vs spaces "debate": if you're having it in the first place, you're possibly doing something wrong. someone eventually putting running tests in Docker containers in there before you can commit your changes). You can technically achieve the same with something like Git hooks but setting those up is error prone and can be annoying once people get too trigger happy (e.g. Annoying at first, but I came to appreciate the idea.
I think that Go in Visual Studio Code did something like that by default, where you saved your changes and it also formatted everything. This is a good point and IMO "format code on save" should be the default in most IDEs and editors - that way if you need a specific set of formatting rules you can configure them, but you won't end up with no formatting (or different people having different ways of writing code) by default. > It does not enforce any syntax style or proper formatting which makes beginners learn that "it doesn't matter" which is wrong imo and leads to horrible looking code. Self-taught students are easy to teach (although they provide their own challenges), but you have to approach things much differently (and often slowly) for students that don't already "think like a programmer". Keep in mind, many of the students taking Computer Science in high school are not exactly the same students that would have taught themselves to program at 15 and 16. Getting students comfortable/competent with a language and then switching it mid year would be a tough ask for quite a few students. The difference between a math variable and a computer variable and how "x = x + 1" works can be difficult for some students to wrap their minds around. The concepts are what is really being taught. There are pros and cons for both options, but ultimately a language is just a language. My school has gone back and forth with starting with Python or Java in the Pre-AP course. The AP Exam covers Java and you have less than 180 days to cover everything from "what is a variable" to inheritance, recursion, and sorting algorithms.
0 kommentar(er)
