2 ms·
I remember many years ago my father, who is very technical but not a programmer, writing a Lunar Lander-type game. He started off writing every message that th
by rwmj 9y ago
I remember many years ago my father, who is very technical but not a programmer, writing a Lunar Lander-type game. He started off writing every message that the program should print. It was along these lines:
10 LET m1$ = "The space craft has landed"
20 LET m2$ = "Descent rate is too high!"
(It was in some BASIC, probably ZX BASIC or GW-BASIC).
After writing a lot of these lines, he got stuck on how to make the computer print the messages at the right time. He had no idea how to continue. He'd mocked the game out on paper so knew what it should look like, but had no idea there is an internal world of state in a real program.
Thinking back to it now, it's rather like how people who aren't programmers mistake the user interface for the whole program. If you show them the mocked-up GUI, they'll think the program must be finished.
The follow up to this story is that with a bit of my help and many, many weeks of work he actually finished the game, although it retained this odd "message database" at the beginning of the code.
- pasbesoin 9y agoAnd if the UI doesn't (yet) look good, they think your development is crap. A problem I've run into. I wanted to get the guts working right. Then, I could make it look "pretty". Non-programmers are just looking for the pretty. Same problem that results in a lot of divorces, I guess... ;-)