I think one of the things that has really got me wondering is abstraction of problems
(from the Alexandria repository resource which we are using):
Coding is the task of translating the algorithm into the language that the computer can understand. Unlike coding, Computer Science is concerned with the algorithm itself, regardless of how it is expressed in a particular programming language.
Pseudocode, writing code with more English-like terms to express an algorithm, is independent of the language that you use.
What is an algorithm?
- a series of executable, well-defined steps that will solve a problem in a finite amount of time.
- it will produce the same output no matter who runs it
There are other parts about the top-down approach to problems that I think are fascinating, I am not so great at expressing it back though.
Here is just some code from Snap and Edgy that we have been doing, for @Stradyvarious
I admit I've been really excited about these because I have wondered about them in Hopscotch for a long time
Oooh now looking back again, there was an idea that we had a think about for website browser histories — when you press the forward/backward buttons on your web browser, or for the concept behind storing undo/redo actions.
We were looking at a concept of abstract data types (like in addition to integers, lists, arrays, there are stacks, queues which I had never heard of before.) more about those two here:
The code for it is here, you can import XML files into Edgy which is straightforward, but I'm just going to have this as a start before I start piling on heaps
(you just save this as a file then Import in Edgy)
and let me know if you want to have a look and/or run into any troubles.