| Author |
Posted on 2015/09/01
#491
|
| Platinatic |
Since alot of you are programers here. I decided that it was time to learn programing myself. So, do any of you have any advice on where to start? What language? What tools? I already have Visual Studio installed. |
| Author |
Posted on 2015/09/01
#492
|
| MKGirlism |
Only Gericom, me, and (sort of) Ermelber are Programmers, actually. Where to start: The best advice in the World is: Try! Seriously, the only possible way to learn Programming, is by just doing it. When you get stuck, just Google the thing you want to know, and for the most of the time, you'll end up at StackOverflow. In the beginning, you'll likely do this every single minute, but it's all okay, I've been there also. What Language: What do you want to make? Mobile Apps? Desktop Apps? Web Apps? Games? What Tools: Same Question as above. |
| Author |
Posted on 2015/09/01
#494
|
| Platinatic |
Well, just kinda in the direction of what you guys are doing. I would like to make stuff like EFE, games (or blender scripts wich i know use python I know a bit of really basic programming thanks to Scratch and my graphic calculator, so that might help a bit. Also, does programming help in terms of "decoding" data in a hex-editor, Like for instance: Collision? Or do i need other skills for that. |
| Author |
Posted on 2015/09/01
#498
|
| szymbar |
"Also, does programming help in terms of "decoding" data in a hex-editor, " Nope, it doesn't work this way. Hex editing is something else, it's not the ability to invent something, it's the ability to read the numbers and thanks to them - read minds of these who created the original files :P You have to look at a lot of files that have been already documented, open them in Hex Editor, check every section, compare it to the documentation, then try to limit the documentation access and try to figure out things by yourself verifying it later with the documentation, ultimately take a chance at file that hasn't been documented at all yet. It's annoying, I get it, but it becomes fun :yay: "Since alot of you are programers here." If this was the case, we'd have a scene as big as MKWii's in MK7 right now, that unfortunately isn't the case because nobody is here to make tools ;_; Happily, thanks to Ermii learning stuff things start to change and Geri isn't the lone hacker. I'm not into MK7 hacking tools yet, there are too many others things I have to do at hand related to RL :okay: "So, do any of you have any advice on where to start? What language?" Basically wherever you want. All the languages are pretty similar and though the syntaxes might differ, all you need to do is develop a certain way of thinking. Like "Sigh, I can't do it. What if I did it the different way? How to do it simple? Is there any easier method of doing this?" You don't even have to know how to do it in a certain programming language. Think how you want to approach your problem, then write it on a sheet of paper, look at it, think, think, split your problem into a ton of small steps and use right Google queries to find a way to do it. Actually a good programmer is a programmer who knows how to use Google :P Like Yami said, you'll end up being at Stackoverflow A LOT. This site is basically essential for programming :P There's actually one good place to test things out and it's called Codecademy. There's a great Javascript course there with a nice learning curve, though stay alert, if you overthink some things, you might spend few hours on an exercise that probably has one simple solution in two-three lines :P But this is a great way to develop a programmer's thinking, the more mistakes you make, the stronger you become. And Codecademy's Javascript is a perfect place to start your adventure because it'll lead you by hand sometimes, it generates preview in real time and there's also a special section called Codebits, but I'll return to it in a while. There WILL be many times in every programming course when you'll turn off your PC, stay at your armchair a little longer than usual and then out of a sudden shout "THIS IS BORING, WHY AM I EVEN LEARNING THIS, I'M NEVER GOING TO USE IT!" ...that's a moment where a lot of people drop their programming studies, I almost did the same. But when you reach this moment, you can start a new Codebit on Codecademy. Think of something simple. I don't know, maybe a simple incremental game? Try to split it into the smallest and easiest elements and then just get to the work. When you make it, try doing another lesson of the course. And after a few lessons you'll scream "Holy crap I could make it 10 times easier and faster", go to the code, edit it with what you just learned and try to add some more simple features. Then return to the course. You'll quickly realise how many ways are there to make tools :P Javascript is nice for one more reason, HTML5 + CSS + JS are objective languages and since you want to do EFE, go for objective languages. You can obviously try things like C++, but this language is damn hard and you can't really make an EFE really quick in it. So Javascript is a way to go. Also remember, don't give up! "What tools?" Notepad. :heidy: Seriously, every code can be written in a notepad. You can't compile all codes though and some of the tools so called IDEs can make it easier to read hundreds of lines of code, but for HTML5 + CSS + Javascript Notepad is just enough :P Codebits at Codecademy is a good IDE with instant preview, you can see what you're changing all the time. Don't lose your way :yay: |
| Author |
Posted on 2015/09/01
#499
|
| Platinatic |
Wow, that is one hell of a reply! thank you! You are reading my mind! I am that person that gave up because it was boring. I was learning Python at CodeAcademy but i gave up at comparators. But now i really feel like learning how to code again. I have made basic games before on my calculator and with Scratch. So i know what you're talking about when you're saying that you discover better ways on how to code stuff. I literally just installed notepad, because i wanted to make a custom kart. So that was already done! Thanks once again for the reply (and for the song :) ) |