Yabasic - What next?

[Mainchip]

Hey guys,

As you all know I have been slowly learning Yabasic. Since I have start I have learned about Subroutines, Loops, Labels, Data, Print, Open, Variables, IF Statement, Labels. There's more but I can't be bothered to write a massive list.

I have no idea what I could learn to use next, if you have any suggestions could you please tell me and explain a little about how it works.

Thank you,

Mainchip.

[E.K.Virtanen]

Hi chip.

Good to hear you have learned much. Though there is so much to learn still
One very important thing is to program. What i mean with this?

You know the basics. Now go and code something. There you meet some obstacles, those will show you what you need to learn next. It might take a while until you get yourself in problems, but for sure you will do so.

Now plan a game/application what you want to make. Dont try to remake Quake, but snake game, simple music player, password reminder for multiple user or something like that.

[MystikShadows]

Yeah EK is right. 

Sicn eyou know the basics, start putting them to good use.   make programs or games that you want to make (always help when you make somethign you really need or really want, keeps the motivation to get it done).

Wiile creating this new project you're gonna start asking yourself questions.  Maybe instead of a standard "enter your choice: _" you'll want to make a highlighting menu, maybe you'll want your program or game to save something to file, as you program this project all types of questions like these will arise, now that you know the basics, the best thing to learn next is how to apply what you know the right way (the better, clearer, easier way, whatever you want) and the best way to start applying those things is to do a project you love and you'll see how fast your learn what you want to learn to make that darn program do what you want it to, the way you want it to.

Be sure to keep us updated and be sure to feel free to ask questions during that project, it's all about growing, you learn from everyone else knowledge, then you apply it to your project and depending on what it is, everyone else starts learning from you, it's a big wheel that started turining, now you just gotta make sure it keeps on turning (hmmm, big wheel keep on turnin, they should make a song about that.  oh wait, they did, C.C.R. Proud Mary. lol).

[Mainchip]

(hmmm, big wheel keep on turnin, they should make a song about that.  oh wait, they did, C.C.R. Proud Mary. lol).

LOL, This is some great advise I will begin this project soon and I will keep you up to date with how it's going and I have pretty sure I will come across some problems. So keep checking to forums often as I will probably be asking a hell of a lot of questions lol.

Thanks, Mystik & E.K.V

Mainchip.

[E.K.Virtanen]

Glad if we could help.

Anyway, one thing i need to say still. I am 101% positive that atleast one of your next few projects is out of your limits. When you find it, crash hard, get pissed, take a break and move on for something simpler

I know some peoples disagrees with me here, but i have 5 point guide here.

1. What ever it is, do what you started to do. Do not change simple worm project to multiplayer online snake game even when you think it is possible. (most likely it is not possible, trust me on this. Been there many many many times  )

2. Instead of producing valid code immediately, concencrate to just get it finished. Nothing feels better than a code that comes alive. It is no matter how gummy code it is, if it just "lives".

3. When your gummy code works, then start to study how to make it better. Dont shame to show your code. For sure every experienced coder has made as gummy code as you at start.

4. Dont get stuck in one project. Start projects which you can finish (in gummy level) in (max) few weeks. Plan three different games/applications and give yourself a two weeks per project.

5. Study codes and questions other peoples has made. There is nothing wrong to study how other peoples makes their codes. 80% of my skills should be credited to other peoples and their codes.

Extra. When you feel like nothing isnt moving on, your project sucks and whole programming is a stupid waste of time (aka programmer burnout) then close computer, go out, have fun (get a girl lol) and get back coding when you feel like it. It might take a days or months. But dont force yourself next to editor just because of unfinished code.

[MystikShadows]

Yo EK....I almost fell off my chair reading your 5 star...What a great concise and straightforward way to guide the newcomers.  Dude, make an article about it, and FAST! .

Good points, that all I have to say.  But you know, we can't brag about EK too much now.  Most of us follow this:

Cool
Cooler
Coolest

He follows

Cool
Cooler
Beer Cooler

And that has it's consequences and repercussions. . lol

Most importantly, have fun.

[E.K.Virtanen]

Yo EK....I almost fell off my chair reading your 5 star...

DAMN!!! Some day i will succes and you finally drop off..

Most importantly, have fun.

Oh yeah, most important thing definately.

[Mainchip]

Congratulations E.K.V on your 700th post

This is some good advice, I will keep this in mind. I also know I am not ready to create a snake like game as I have no idea how I would go about doing that. I going to start with some applications then maybe a Text Based Game.

Thanks guys.

Mainchip.

[Jacob]

Really agree with what the other guys are saying, also that, now that you know the basics of the language, start using it for some small projects, and with time, bigger ones.

And it's true that it's more important to get your code working, that will give you a lot of motivation for improving on it/producing more working code. I don't know if you've noticed with some of the 'demos' I've posted in the Yabasic part of the forum, usually I come up with a cool idea later, add that and with that I've usually done a bunch of improvements to speed that I didn't have in the beginning.

As for the Snake type game, if you want inspiration I've posted a simple version on here once, it works, but a lot of the code is kinda... Less good and probably slower than it should be.

Or do something simple, write a Brainfuck compiler, it can be done really REALLY simple, and as you get more creative and better, you can easily add more things to check for common errors, speed improvements in the compiled code etc... And the best thing is there's no strict standard, so you can add your own stuff also! (Someone is obviously working on a Brainfuck compiler in C)

Oh and btw, happy coding!

[Mainchip]

Hey guys,

I am just starting my new project, I have not planned it fully yet but I know I want it to have a highlighted menu like E.K mentioned. I think it is only possible in graphic mode am I correct?

I would like some help on this if possible, and I couldn't find any menu examples anywhere, maybe I am not looking harder enough.

Thank you,

Mainchip.

[Derek]

Hi,

menus can be written for the console as well. You can list options and enter a number to choose one. Highlight an option to choose it etc. Don't copy other people's work do it for yourself; it's much more satisfying.

I don't know what you're planning but the menu isn't the most important part of the program. If, for example, it's a music player then you have to work out how Yabasic, which doesn't have any sound capabilities, will play music (it's possible though).

Derek.