Himiko Kuronaga wrote:CCP FoxFour wrote:Nguruthos IX wrote:~Racial variants of all vehicles.
~New turret types
~A respec for vehicle users
~Dropship cloaking
~A new vehicle type
~The promise that with each introduction of new racial variants, partial respecs will be offered since CCP decided to release Dust without over half of it's content.
These would be a good reason for having to wait another month.
Out of curiosity, how long do you think each one of those line items would take in terms of man hours?
If you have to ask that question, you need a bigger budget.
If you think that throwing more money at a coding problem will make it happen faster you need to get the f*** out of IT.
Listen, I am a software developer. I work on applications for oil companies, brokerage firms and large energy companies with project budgets larger than CCP's annual income. Coding accounts for <40% of our time. Most of it is is investigation, design, approval, mockup, approval, (then coding), then unit tests, then fixing, then unit tests again, then QA pass, then staging release, then more QA tests, then full integration tests, then production release planning, then the production mock release, then (finally) the production release.
They are on a 1 month agile release cycle which means 1 week of investigation, design, approval. Then a 2 week sprint of coding. Then 1 week of QA, integration testing and release. And that's if everything works out perfectly. If they find a nasty bug then they miss the release and make it to the next one.
Throwing money at a problem helps to bring on more resources to spread out work. But suddenly adding 10 more programmers wont speed things up, in fact (most times) it slows things down as you need to dedicate man hours to training the new resources and deal with the bugs they will introduce due to not being familiar with the code. Eventually they will get up to speed, but even then you'll probably run into the problem of "too many hands in the cookie jar" which causes you to have to divvy up tasks into micro-projects which causes a nightmare with code merges / task management.
- You yell when CCP doesn't tell you what's coming in the next patch.
- Then when they do tell you whats coming you yell when it's delayed due to it being buggy and scream "release it anyway".
- Then when they do release it anyway you yell that they don't know what they're doing and the new feature is broken and shouldn't have been released.
- Then they don't tell you **** and you yell but they ignore you because no matter what they do you're going to yell.
So for everyone commenting here who doesn't work as a programmer,
shut up. I don't come into your workplace and tell you how to flip burgers faster...