Content added Content deleted
m (Added some introductory text to Learning to code) |
m (added some notes on how this should be written out. fixed some issues with the text.) |
||
| Line 13: | Line 13: | ||
This tutorial will provide you with a brief guide on programming and coding in-game. Namely; programming and coding are not the same, though they are often confused as such. Coding is just writing instructions to the computer (code), while programming is the engineering of software. A programmer creates algorithms and solves problems, and then codes them to create a fully-fledged software solution. |
This tutorial will provide you with a brief guide on programming and coding in-game. Namely; programming and coding are not the same, though they are often confused as such. Coding is just writing instructions to the computer (code), while programming is the engineering of software. A programmer creates algorithms and solves problems, and then codes them to create a fully-fledged software solution. |
||
Please do not feel intimidated by this, as if it something out of reach to you. Though serious programming is not |
Please do not feel intimidated by this, as if it something out of reach to you. Though serious programming is not everyone's cup of tea, you do '''not''' need to be an ''AAA++'' software engineer with 15 years of experience to code up your little idea. Everyone needs to start somewhere, even the pros; and Waste of Space is hardly a source of difficult problems. Perhaps, if after reading this tutorial you find out that you like programming, you may even become one of those pros one day. Even in the worst case though, you will have learned another, increasingly relevant skill, and will have developed your logical thinking. If you haven't already gotten the gist, this guide is aimed at newcomers to programming. |
||
If you |
If you aren't sure whether or not to commit to learning programming, perhaps a well-known example (it's on the game's thumbnail!) of programming in waste of space can tip you over to either side. |
||
{{#ev:youtube|https://yewtu.be/watch?v=waYNQq3f60Q|1000|center|Example description|frame}} |
{{#ev:youtube|https://yewtu.be/watch?v=waYNQq3f60Q|1000|center|Example description|frame}} |
||
| Line 27: | Line 27: | ||
Once you've set up a code editor, there's one more thing to do before you can start coding: setting up a '''runtime environment'''. As lua is a '''scripting''' language - a programming language in which the instructions to the computer are stored as '''source code''' (the code as you wrote it, in textual format) - it must be translated to the computer in real time because computers can only understand binary (0s and 1s). This is what a runtime environment is for (in this case); it allows for the execution of '''scripts''' (source code) by translating to '''machine code''' (instructions understandable to the computer) on the go. |
Once you've set up a code editor, there's one more thing to do before you can start coding: setting up a '''runtime environment'''. As lua is a '''scripting''' language - a programming language in which the instructions to the computer are stored as '''source code''' (the code as you wrote it, in textual format) - it must be translated to the computer in real time because computers can only understand binary (0s and 1s). This is what a runtime environment is for (in this case); it allows for the execution of '''scripts''' (source code) by translating them to '''machine code''' (instructions understandable to the computer) on the go. |
||
| ⚫ | |||
| ⚫ | |||
(Testing bla bla bla) |
|||
- Testing if everything works with print statements (Hello world!) |
|||
aaaa |
|||
- Use this as an introduction to basic code flow |
|||
- variables, global vs local |
|||
- types |
|||
- numerical operators, numerical operators on variables |
|||
- logical operators, scope |
|||
- tables, dictionaries |
|||
- loops - basic |
|||
- strings - basic operations |
|||
- more operators, operator shenanigans |
|||
- functions (basic. just an introduction;) |
|||
- tasks should be included for each of these. these tasks should be quizzed (use the quiz extension). |
|||
=== Computational thinking === |
=== Computational thinking === |
||
- problems, and how they are broken down into programmable steps. just a lot of problems. practice makes perfect |
|||
- small project at the end |
|||
=== Coding revisited === |
=== Coding revisited === |
||
- strings 2 |
|||
- basic OOP |
|||
- functions/methods 2 (stuff like recursion goes here) |
|||
- more complex collections (stacks, queues, etc. - with implementation details/a preprogrammed script available for these) |
|||
- built in functions (if possible in any way this should be introduced bit by bit through earlier sections) |
|||
- coroutines |
|||
- error handling |
|||
- quizzes after every smaller chunk. more than for learning to code as this is tougher. |
|||
=== The Microcontroller === |
=== The Microcontroller === |
||
- parts |
|||
- built in microcontroller functions |
|||
- add a quick little quiz and small project at the end |
|||
=== Programming === |
=== Programming === |
||
- everything put together and tested with practical projects |
|||
- thorough explanations and solutions should be given for each project. throw in some software engineering stuff here as well. |
|||
=== Afterword === |
=== Afterword === |
||
- buh bye |
|||
== Parts == |
== Parts == |
||