a respec for vehicle users? you tell me since youve done respecs before... whats the problem now? your hands cramped or something for falling over?

if anything, there should be a respec for everyone. there were so many changes, it would just be fair (or atleast a respc when all racial suits, weapons and vehicles are ingame)

Would like to point out that CCP said no respecs, so respecs will take 0hrs cause you ain't getting one!

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...

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...

Out of curiosity, how long do you think each one of those line items would take in terms of man hours?

[quote=Severus Smith]I am studying to be a programmer, how do I go about getting into the kind of work you are doing?

[quote=Nguruthos IX]~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.

Well you know, all of those things could be possibly... if they didn't have just one man working on each category (e.g. vehicles, maps, weapons, dropsuits, etc.).
If CCP had a proper team with multiple members working on each, production of updates could speed up greatly.

Get a degree, or a bunch of certifications (degree for large companies, their HR departments will ignore your resume without one). Learn .NET MVC which is what is in demand right now, and consider adding emphasis on javascript libraries like JQuery, Breeze, Durandal and Knockout. Those are getting big, but could also bubble and die like previous web technologies (cough cough Silverlight). DB knowledge in SQL Server and Oracle always helps.

I am lucky and work in Houston, TX which isn't really known as a "Tech City". However, since we have a lot of the big oil / energy companies here (and more keep coming) there's as large amount of demand for software developers to overhaul their systems and reduce costs. Look for places like that to move to. Where demand for developers is growing quickly but supply is low. Avoid places like Silicon Valley because everyone and their mother who wants to be in software goes there (like Hollywood for actors and New York for MBAs). So you're fighting a lot of competition (but it could pay off handsomely).

Awsome, Im currently getting a degree, got 2nd class (2% of a 1st) last year, am doing mysql, and javascript.
Learning .NET MVC next year conveniently, and have a Cisco CCNA1 qualification already!!

I'm aiming to get into the inhouse development team forba larger corporation, where each soultion has its own intricate little factors!!

Good work, sounds like you have got a plan.

Study these design patterns. RIght now they may not help if concepts such as Interfaces, Abstract Classes, or the difference between Client and Server code are unknown to you (took me awhile). But once you get those concepts down these design patterns help land you big jobs (interviewers love to ask about the Factory Pattern or how to implement a Singleton) and make things a lot easier.

whatever you do dont waste your time listening to this guy dust does not need new vehicles it needs whats here to be fixed you cannot add things into a broken foundation and expect them to work. why on earth would ccp waste their time providing new vehicles and turret types when what we have is so destroyed. they need to sit down and dedicate they're time to eradicating blams blasphemy from new eden. add new vehicles, new turret types what are you thinking pfft you should just quit dust

don't really care.

out of curiosity how many wasted man hours have been spent on NOT fixing the previous man hours spent 'fixing' broken areas of this game?

the entire concept of required development time for 'NEW' content is just beyond me.

the man hours already spent in previous 'new' content or the time already spent addressing 'issues' I would hope would be a multiplier of the time required for new content, cause lets face it, it takes months to 'fix' something and many things STILL have not been addressed that have been around since May (and in some cases longer...)

wouldn't recommend opening this rabbit hole..

Out of curiosity, how long do you think each one of those line items would take in terms of man hours?

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...

It's not our job to figure out the man hours on this ... thats yours...everybody just wants you guys to keep your word....I'm A/V so i could care less what happens with the tanks..but you guys...CCP...talked up the viehicle 1.5 patch and everybody just jumped on your bandwagon...you guys built up everybody for this let down....just like your dated weekly forum dev updates post..that is religously late 5-10 days..actually often started with some sort of week excuse about a headache or a dog eating it or something...

There are far too many problems with this game that need to be adressed like-

Dying when you jump out of a dropship
the squads are super messed up, i havnt even seen a warroom in 2 days and played in matches that have 16 people each side with no squad anywhere
when in a tank you cant render crap from 20 meters
my 15 million sp character does about the same as my free militia alt
at least a half dozen glitch spots on the map where snipers sit every match that you cant hit
1 in 3 matches for me i end up playing nobody

Do i need to go on...there are tons more...this is all more important than you having a shiney proto tank and some racial bounses.....


And for the record....I feel like this comment from the Dev was a little rude...I might be the only one but, I feel that we are customers and you are selling a service..I know its hard sometimes but ...I manage a restaurant and If a guest asked me where his steak was, and i responded "do you know how long it takes to cook'? I would get fired....exspeacially if i told him it would take 10 minuites and he asked me 10 minuites later..like this senario

Smile and say sorry...even if you dont mean it...thats buisness..But I'm good t my job..everybody is not so lucky

You'll never see me complaining about something that gets added and "shouldn't have been released yet". Just saying. I think the majority of people are with me, that the risk of buggy or unpolished content is not nearly as bad as stagnation at this point. I'm not saying game crashing, PS3 melting bugs are okay, but there is a certain balance here where perfection is not worth the wait.

What if they had chosen not to release 1.4 because of the squad deployment bug? Imagining that they knew about it to some degree, would waiting till yesterday to release patch 1.4 really have been worth it? Or more likely another couple days to match their downtime schedules. I'd say probably not.

Get a degree, or a bunch of certifications (degree for large companies, their HR departments will ignore your resume without one). Learn .NET MVC which is what is in demand right now, and consider adding emphasis on javascript libraries like JQuery, Breeze, Durandal and Knockout. Those are getting big, but could also bubble and die like previous web technologies (cough cough Silverlight). DB knowledge in SQL Server and Oracle always helps.

I am lucky and work in Houston, TX which isn't really known as a "Tech City". However, since we have a lot of the big oil / energy companies here (and more keep coming) there's as large amount of demand for software developers to overhaul their systems and reduce costs. Look for places like that to move to. Where demand for developers is growing quickly but supply is low. Avoid places like Silicon Valley because everyone and their mother who wants to be in software goes there (like Hollywood for actors and New York for MBAs). So you're fighting a lot of competition (but it could pay off handsomely).

On topic: People, please stop whining at CCP. And offering solutions like "throw more money at it" or "code faster" just shows that you're ignorant to software development and need to stop commenting about it.

whatever you do dont waste your time listening to this guy dust does not need new vehicles it needs whats here to be fixed you cannot add things into a broken foundation and expect them to work. why on earth would ccp waste their time providing new vehicles and turret types when what we have is so destroyed. they need to sit down and dedicate they're time to eradicating blams blasphemy from new eden. add new vehicles, new turret types what are you thinking pfft you should just quit dust

Everyone has been yelling for information. "Tell us whats coming!", "Whats in the next patch?", "Why aren't you telling us things!?" and then when they do tell you and something happens we get people like you yelling "You built us up and lied!", "You're rude!", "Don't tell me how to do my job (manage a restaurant) here's how you should do your job (list of things to fix)"

Please, shut up.

Either ask for information and politely accept it when they give you further information about why it didn't work. Or be quiet and let them release things when they are ready.

I don't come into your restaurant and expect my steak to be in front of me in 1 minute. Nor do I go to the back and curse out your cook for "lying to me" when my steak comes out medium well instead of medium rare. I wait for my food, politely send it back, wait for the correction, and still pay at the end because I am an adult with intelligence and manners.

Point is, we're more efficient at finding bugs than CCP anyways.

If we wait for CCP to find and squash all bugs before a release, then we'd be waiting an extra month or more. Besides that, we're still going to get bugs anyways.


So, use the playerbase, AKA beta testers to test anything resembling functional and then patch it up after.

I used to think a separate, real, beta server would be a waste of resources. But at this point it's looking like the best idea.

NO, ill say what i want dummy

Actually we've been topping 4,500 nukerous times in the last week and month!!