Quote:
Originally Posted by Spitty
[You must be logged in to view images. Log in or Register.]
It's unbelievable that you live in a world where you think people will take you seriously given the content of what you're posting. You have no qualifying skills that give you the ability to armchair-manage a collection of dead newts, let alone talented programmers and developers.
The likely holdup with Velious is the tedious grunt-work done at the line level by those with programming talent. Those who oversee the project, those with administrative talent, literally can't do anything of value for Velious until tasks at that level are completed.
So, say Administrator A is waiting on a list of ten tasks from his developers before he goes in, does some validation and signs off on the work done. This administrator can do ANYTHING ON THE FUCKING PLANET that he wants without impeding on the best-case progress with Velious. He could go get shitfaced in Vegas, or look into a team PVP server. It doesn't matter. His time doesn't come into play until those ten tasks are completed, at which point a good administrator would validate the work and identify the next set of deliverables.
Plus, are you seriously suggesting he turn away a volunteer programmer that expresses interest in a team PVP environment just because there's another project at hand? What if this developer gets two weeks into team PVP and decides hey, Velious sounds more fun? You're the kind of person that might be able to recognize talent, but have absolutely no idea what to do with it. If you worked for my company and I found out you turned down a goldmine of programming ability simply because they didn't initially express interest on working on your pet project, I would fire your ass so hard you wouldn't find a job in a related sector for decades.
Story short, you want Velious but have no idea how to get it. That doesn't give you any right to boss around those who do know how to get Velious up and running. I've done workforce management for large companies under the directive that Project B needs to be completed but can, in no way, impede on Project A. There's no "things aren't what they seem" in this scenario - if hours aren't adding up and projects aren't moving according to cycle and deadline constraints, people (me) get fired and companies lose huge contracts.
It would help if you'd realize that your level of intellect isn't a concrete ceiling for human intelligence, and people find plenty of creative and executable ways to manage multiple projects congruently. Instead, you seem to be assuming that your worldview is the end-all of "How Things Are" and not only does that totally fuck up your own chances for personal progress and positive change, but makes you dead weight to any situation requiring creative solutions to achieve success.
|
You are missing my point. Admin A 'Could' actively look for more programmers for the Velious Project instead of turning his attention to a pvp server or getting shitfaced in vegas or ANYWHERE else. I am not saying he should. Im just saying that it is something that he could do if said Admin chose to that would eventually, no matter how little, move the Velious project forward. Am i saying this is the BEST way to do things all around? No. I'm just saying the statement that new red doesn't take away from velious isn't true. It will even if a tad.
And, it seems i need to point this out, again. I haven't said that the devs SHOULD do anything.
Now if we get on the topic of whether New red should or shouldnt be ... thats a different story.