2 ms·
I've learned English trying to understand documentation for Turbo Pascal 7 :) That, and playing games. The first game I've made was written in Turbo Pascal in
by ajuc 15y ago
I've learned English trying to understand documentation for Turbo Pascal 7 :) That, and playing games.
The first game I've made was written in Turbo Pascal in 13h. It was 2d arcade shooter, witch "asteroids" physics, tiled terrain, and diablo-like system of better weapons and enhancements to buy to your ship. And it was under 600 kb (including graphic), because I didn't knew how to use extended memory from Pascal. It was procedural code with few global variables that contained whole state of game. Code was just many procedures calling each other, and I divided it all into 2 files, because TP had limit on code size to 65536 bytes or sth like that. So I just cut and pasted a few procedures to the second file.
It was horrible code, but it worked, and was quite easy to modify despite the lack of architecture, because it was small. And because adding hacks when you have global variables is easy.
And most importantly - the game was quite fun to play. Unfortunately I've lost it in hard disk accident a few years ago.
Anyway - constraints are good for you, because you have some hard decisions made for you. And caring over implementation details more than about the result is bad. Now I program with all the cool technologies, use oo principles, design patterns etc, but it's less fun, and the result is most often unfinished project. I just can't keep motivation all the way from buidling foundations to making it a finished game.
Maybe that's because now I have job and less time (and energy) for hobby, or the fact that I'm doing more ambitious projects now. But I think it's also because now I overengineer. Maybe it's time to try small and ugly coding once again?