Page 1 of 1

How far should I be.

Posted: Thu Jan 06, 2011 5:46 pm
by THe Floating Brain
Without looking at my project ,SFML, C++, 6 months in making a RTS/Over Head Shooter Engine. How far should I be?

Re: How far should I be.

Posted: Thu Jan 06, 2011 5:52 pm
by ibly31
Unless I'm missing something, that is kind of an odd question. How do you define how "far" you should be?

You didn't give us context like age, intelligence, length of time spent programming, and other factors so its kind of hard to tell you exactly what you should have programmed. Programming is a tough thing to learn, and no one ever really completely learns it. Also, there isn't some set path that everyone learns - you have to learn your own way.

If I have interpreted your question wrong, please feel free to tell me. It just seemed like an odd question with such little context, you know?

Re: How far should I be.

Posted: Thu Jan 06, 2011 6:19 pm
by Ginto8
It doesn't seem like a valid question. If we were to say X amount and you were farther along, your head would inflate like a balloon entering a very low pressure area. If you were behind that, you'd be all sad, and I don't like sad people, they're annoying. You should set your own goals, and fail to meet them on time like a man. You'll start to realize that even when you think you aren't accomplishing a whole lot, you're usually learning a lot that can be applied in a lot of places. Don't be afraid to fail or go slow, just make sure you're challenging yourself and improving your technique. 5 years from now, your little RTS/Shooter game won't matter one bit. What WILL matter is what the project taught you about programming.

You seem to be a bit too concerned as to what you "should" do rather than what you actually do. Set goals, small ones are better, and just get it to work. If it takes a week, hey, that's great. If it takes a month, great. If it takes you four months, great. Don't be concerned as long as you make sure you don't stop learning. Getting to a point where you aren't learning anymore or aren't at least a bit challenged is BAD BAD BAD because that means you're just wasting time.

Re: How far should I be.

Posted: Thu Jan 06, 2011 7:23 pm
by THe Floating Brain
You didn't give us context like age, intelligence, length of time spent programming, and other factors so its kind of hard to tell you exactly what you should have programmed.
Il rephrase the question. I am within the range of 14 to 18, intelligents IQ > 120, A's, B's in school, almost constantly on honer roll (There is always that damn class with a 79 or 78 :evil: ), more logic then the avarage person but with less commen sence XD, Lenth of programming experance 3 - 3.5 years, Time spent on project 6 months, Avarage time spent every week, 20 - 30 hours about, about how far should I be while working on a Over Head Shooter/RTS engine?
Getting to a point where you aren't learning anymore or aren't at least a bit challenged is BAD BAD BAD because that means you're just wasting time.
Well it seems like I am 85% challange and I am 15% learning :lol:

P.s Should I work on it more?

Re: How far should I be.

Posted: Thu Jan 06, 2011 7:47 pm
by krilik
As far as you want to be.

This question is really unanswerable, unless you are trying to meet someone else's deadline and they tell you.

Re: How far should I be.

Posted: Thu Jan 06, 2011 8:10 pm
by THe Floating Brain
As far as you want to be.

This question is really unanswerable, unless you are trying to meet someone else's deadline and they tell you.
if you agree say "I".

Re: How far should I be.

Posted: Thu Jan 06, 2011 11:12 pm
by dandymcgee
Set goals for yourself, do your best to meet them. If you meet them successfully you're doing well, if not either try harder or create more achievable goals.

Re: How far should I be.

Posted: Sat Jan 08, 2011 10:37 am
by THe Floating Brain
Set goals for yourself, do your best to meet them. If you meet them successfully you're doing well, if not either try harder or create more achievable goals.
I did set simple goals for example to be able to left click on a apsace ship and right click somewhere else and have it go there took my 6 months. Im kinda wondering if A: I set my goals to high B: I am realy...realy...slow?

Re: How far should I be.

Posted: Sat Jan 08, 2011 10:52 am
by JesseGuarascia
Okay, umm... I'm not trying to be a troll, but... here goes. With all of that practice and smarts, you couldn't figure out how to do a basic "move to direction"? I'd just have all of the objects in the RTS, then when you click one, it points to a reference to an object, then that's the currently selected object. When you click somewhere else, set the object's angle, and make it move until it reaches it's destination.

Seriously though, 6 months with that much work? Was some of it drawing?

Re: How far should I be.

Posted: Sat Jan 08, 2011 11:14 am
by dandymcgee
JesseGuarascia wrote:Seriously though, 6 months with that much work? Was some of it drawing?
Again it's hard to judge based solely on a given timespan. It took me over a year of programming other things to even decide I was interested enough in C++ to stay with it. At least 2 years to gain a solid working understanding of SDL to the point where I could create just about anything given enough time and a good design. I'm still in the process of learning more advanced C++ concepts, and don't plan to ever stop learning. There's always something you don't know, no matter how expert you feel, you've just gotta figure out what it is and learn how to apply it.

Re: How far should I be.

Posted: Sat Jan 08, 2011 11:19 am
by JesseGuarascia
dandymcgee wrote:Again it's hard to judge based solely on a given timespan. It took me over a year of programming other things to even decide I was interested enough in C++ to stay with it. At least 2 years to gain a solid working understanding of SDL to the point where I could create just about anything given enough time and a good design. I'm still in the process of learning more advanced C++ concepts, and don't plan to ever stop learning. There's always something you don't know, no matter how expert you feel, you've just gotta figure out what it is and learn how to apply it.
I agree completely, I've been doing C++ for 4 - 5 years, and I still have tons to learn. Getting over the hurdle of SDL was a pain for a little, but once I leaped, I leaped far. It just sort of seems like this guy, with all of his outstanding background knowledge, and his fantastic grades, that he should at least have taken a little less time to do a character movement in a RTS (unless there was some A* path finding or something).

But, like some say, you learn at your own pace. For some, you WORK at your own pace. I wish the best for your RTS man, and hope you finish, and someday release it :D. I'm a big fan, but Starcraft II gets stale after 16 hours play times (hyperbole).

Re: How far should I be.

Posted: Sat Jan 08, 2011 11:38 am
by dandymcgee
Sure, I was just pointing out I'm doubtful he was actually starting at his IDE for 6 months straight. Often times while working on a project I'll discover a new concept and go off to learn about it while the idea is fresh, even though I might not directly relate it to my current project. Perhaps he was also learning other things at the same time.

Re: How far should I be.

Posted: Sat Jan 08, 2011 12:58 pm
by THe Floating Brain
Thank you guys fror sharing your expeances with me and all your gereat advice it realy helps :-D
I did get camra movement a test level and cursor working + learned alot to though :-)
Sure, I was just pointing out I'm doubtful he was actually starting at his IDE for 6 months straight.
Yes maybe I did go and be like... "man that would be cool to make in garrys mod" or somthing like that alot too :-P
But, like some say, you learn at your own pace. For some, you WORK at your own pace. I wish the best for your RTS man, and hope you finish, and someday release it :D.
ty :-)