KukY wrote:Devs not understanding that they have timelines, which, ironicaly, were placed by themselves.
More like someone setting a release date without telling me, with that date being way later than my plans. And regarding the roadmap, since usually the submitter sets the milestone and nobody changes it later, those tend to be not very meaningful.
KukY wrote:Devs not understanding that they have timelines, which, ironicaly, were placed by themselves.
Contrary to popular belief, there is more than one dev.
cybersphinx wrote:More like someone setting a release date without telling me, with that date being way later than my plans. And regarding the roadmap, since usually the submitter sets the milestone and nobody changes it later, those tend to be not very meaningful.
KukY wrote:Devs not understanding that they have timelines, which, ironicaly, were placed by themselves.
You are confusing timeline with schedule. Timeline is the order things happen in. Schedule is the date they are *supposed* to happen on. We have a timeline.
One of the great advantages open source projects have over commercial software development is that they are not driven by schedule. Once you set a schedule, the focus becomes meeting that date rather than making good software. The result is hacks, quick fixes, shortcuts and bad implementation - things we would prefer to avoid. I suspect a lot of ugly things in the code are due to the original schedule-driven game development environment. So don't start wanking over dates.
)
oh well)
