I'm running into an interesting phenomena, and thought someone else might benefit from it, or it's discussion.
For the first time in a while, I hit a brick-solid wall while coding. A feature I impletmented in an earlier version had all of a sudden stopped working, and I couldn't find the code that was causing the problem. Usually, this would have slowed me down considerably, as I went painstakingly through my code, trying to find the problem, or re-writing large chunks in order to try and restore functionality.
Luckily, this wasn't my first release. While multiple releases in the development process may be annoying to some people, in this case, it actually worked to my advantage. I had been nervous about doing so many releases so close together, but if I hadn't, I wouldn't be able to track back through my code, find the script that was causing the problem, and roll back to the earlier version.
So here's the debate, is it worth it to push out a release with every new feature in the game, or is it better to wait and get all your ducks in a row? I used to lean towards the latter, but now I'm starting to thank God I chose the former.
On The Backup
Forum rules
Ren'Py specific questions should be posted in the Ren'Py Questions and Annoucements forum, not here.
Ren'Py specific questions should be posted in the Ren'Py Questions and Annoucements forum, not here.
-
- Newbie
- Posts: 22
- Joined: Tue Jun 17, 2008 1:45 pm
- Projects: Consuming Flesh
- Location: New Orleans
- Contact:
On The Backup
Consuming Flesh - An epic story of war, zombies, survival, love, and more zombies.
Who is online
Users browsing this forum: No registered users