This does NOT WORK when the Developers themselves are simply checking in code without even testing it themselves first.Jimen wrote:QUOTE (Jimen @ Sep 15 2010, 09:34 AM) nobody cares how fast the Dev Zone moves...so long as it moves at the pace that the DEVELOPERS set.
When developers check in code without testing, it has the potential to "break the build" and make everyone's life very difficult due to introduced bugs, incomplete code is VERY BAD. I stopped my running tally on how many code checkins were followed minutes later by another checkin of code the SAME TICKET with a comment like "oops, forgot a closing bracket" or "that should have been in quotes" and nothing extra added with the extra checkin other than the requisite } or '
^ THAT IS ATROCIOUS CODING PRACTICE and will get you put on the programing equivalent of latrine duty each time you do it at any corporation with decent standards and practices.
Ever heard of "code review"?Jimen wrote:QUOTE (Jimen @ Sep 15 2010, 09:34 AM) The reason people get pissed off about the fact R6 has ground to a halt is that literally every single dev has complained at some point about progress being held up by administrative issues and outright mismanagement. Bard's become publicly branded as the bottleneck in development, and as you may recall from the last thread about you, PEOPLE HATE BOTTLENECKS.
When standards and practices are followed, it's quick and simple.
When they're not, and BOY were they not, it takes atrocious amounts of time.
I didn't break beta. It was largely broken early on by the timed cutoff of the build server so that I could upload files for ASGS users in Beta Mode because that often led to bugged versions being the "existing" one due to the aforementioned poor coding processes (I wanted a saturday cutoff so patches could be implemented, Imago wanted wednesday morning US time, we compromised at noon on tuesday which, as you can tell, still proved FAR too short a time period) and later by Imago's complete abandonment of his undocumented changes to the beta server (some of which involved reviving exe files that were deprecated YEARS AGO, not to mention linking several perl sripts to both service restarts and registry keys that ran process restarts automatically due to code commits, making them exceedingly difficult to hunt down and turn off).Jimen wrote:QUOTE (Jimen @ Sep 15 2010, 09:34 AM) Maybe if Bard would stop breaking beta already, we could beta test...
So the two major things I'm doing are cleaning up a gigantic undocumented mess so we can get the beta server up and running for everyone and finishing the code review so we can get a fully functional build of R6 up on the beta server for extended testing, at which point we can start voting about features. I'm simply not whining publicly about it while doing it.
Omnia Mutantur, Nihil Interit.
