Sign In
Create Account
Follow Us on Twitter
Subscribe on Youtube
error........
..............
..............
3 replies to this topic
Back to top|
|
|
#2
Posted 30 October 2007 - 04:34 AM
kkelly
-
- Members
-
- 49 posts
Learning Programmer
Have you gone over Finite State Machines?
#3
Posted 30 October 2007 - 06:14 AM
Gabriel
-
- Members
-
- 39 posts
Learning Programmer
you know the point might be to to try and figure some other stuff outside of what the teacher has said... I've had that happen to me before. giving me a problem to solve but not being fully equiped. then again I"ve been FULLY equiped and still not understood what I had to get it to do what I wanted.
I'm an angel. I kill firstborns while their mamas watch. I turn cities into salt. I even, when I feel like it, rip the souls from little girls, and from now till kingdom come, the only thing you can count on in your existence is never understanding why.
-
Do you know how you got that dent, in your top lip? Way back, before you were born, I told you a secret, then I put my finger there and I said "Shhhhh!"
-
Quotes taken from The Prophecy (1995)
-
Do you know how you got that dent, in your top lip? Way back, before you were born, I told you a secret, then I put my finger there and I said "Shhhhh!"
-
Quotes taken from The Prophecy (1995)
#4
Posted 30 October 2007 - 08:03 AM
WingedPanther
-
- Moderators
-
- 16,831 posts
A spammer's worst nightmare
Step 1) Can you perform the actions described yourself? For example: can you keep track of drinks present, coins inserted, etc (with pen/paper handy)? Start the problem without even thinking about code, just behaviors.
Step 2) Can you sketch out these behaviors in pseudocode/flowchart form? If doing event-driven programming, make some basic screens.
Step 3) now worry about coding.
From what you've described, you need to slow down and think about the problem from a practical perspective, ignoring code for the moment.
Step 2) Can you sketch out these behaviors in pseudocode/flowchart form? If doing event-driven programming, make some basic screens.
Step 3) now worry about coding.
From what you've described, you need to slow down and think about the problem from a practical perspective, ignoring code for the moment.
