Pyweek Game Coding: Unterschied zwischen den Versionen
Oneup (Diskussion | Beiträge) ausgemistet. ein bisserl. als rückblick. oder so. |
Nex (Diskussion | Beiträge) →Lessons learned: hack coding, project mgmt, →mission accomplished |
||
Zeile 115: | Zeile 115: | ||
* We need a smaller vision | * We need a smaller vision | ||
** Or be more flexible about our vision | ** Or be more flexible about our vision | ||
* You can ignore the fact that the first release should be made no later than half time, but that doesn't make this fact go away. | |||
* Hack coding (as in "he's a hack", not "he's a hacker", though the two are related) works wonderfully shortly before the deadline, e.g. when you reaize that textures inexplicably stopped working and you resort to drawing individual pixels as OpenGL rectangles. | |||
** Hack coding sabotages the entire project when applied shortly after the project is launched and you're supposed to lay down a foundation on which the rest will be based. | |||
* Teams of two don't need project management | |||
** Teams of 8 do | |||
== Mission Accomplished == | |||
It's Easter Monday, and I could be watching LotR, or play Lumines, or do spring cleaning, but no, here I sit, working on the meta-game-engine. |