4/9/2024 0 Comments Synthesia 0.8.3I guess I have to admit that I am a bit selfish and would love to see this product move forward at a pace that only a grouping of people could attain: ie from a "for profit" company. How would you like that? I hope it sounds clear. They wouldn't like to degrade their own health and have no time to hang around with their friends and families. Most programmers who made other helpful applications to other people have adopted this kind of schedule. You don't have to stay on the 3 months or 4 months schedule, just slowly take your time and rest for a few days if necessary. The example above meant that you could change your schedule to either tight or loose. Later, just 2 weeks before the deadline, you realize there''s a hidden bug that forces Synthesia to do, you quickly postpone the deadline to another month in order to fix it. Quickly, you went on with the work ahead of you, re-scheduling the deadline to 4 months. Another 2 months had past, most of the bugs have been fixed, when all of a sudden, some idea struck your head, giving you more inspirations for Synthesia. After realizing there's not much left to do, as no more requests have been made by other users, you decided to shorten the release deadlines to a 2 months release schedule. Suppose you made your new release after 3 months of work. I didn't really have much planned for the 8's and 9's anyway. Instead of saying the "0.6.x" series, I would just say the "0.6.x through 0.7.x" series". (Oh yeah, and you're right that cutting the release time in half would double the rate the version number increases. Maybe when I hit 1.0, I'll take some time off, but I'm not even sure about that. It feels good to be working on something people enjoy, and I still have a ways to go before I'm satisfied with the state of the game. I don't even want to slow down or take time off from the project. That happy medium where everything kind of works: releases are happening quickly enough for you guys and I have enough time to get substantial features in. Otherwise, what you describe is what I'm looking for. From three to anywhere up to six or so is almost easy from that point on.) (On the other hand, going from two to three is smaller. It's a really big leap going from one to two developers. When you add even a single new developer, you have to spend a lot of time talking through the way things should be done. Right now I just have to make ideas clear in my own head and don't have to worry about communicating problems or solutions to anyone else working on the code. Those reasons aside, it gets a lot more complicated to communicate about the project. That effectively cuts the population down to nothing. And finally, they would have to be in it for long periods of time, for little or no money. Then, they'd have to follow whatever instructions I gave them without question. First, they have to both be a good programmer and be passionate about the project. So, bringing someone else onto the project is really hard.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |