State of the Game

Are you able to prove that stateement, or just uttering for the sake of it?

are you suggesting that the people employed to work on the game are just lazy, stupid and bad at both developing and game developing? Perhaps their managers force them to work poorly? add in random 1 month sla's for what appears to be obvious issues?

nah. i think there's a common factor at play and I dont think all of the comments left on places like glassdoor are myths and fabrications. Far more things point to the codebase than to anything else. At least the normal things... there's obviously still management issues at play.
 
are you suggesting that the people employed to work on the game are just lazy, stupid and bad at both developing and game developing? Perhaps their managers force them to work poorly? add in random 1 month sla's for what appears to be obvious issues?

nah. i think there's a common factor at play and I dont think all of the comments left on places like glassdoor are myths and fabrications. Far more things point to the codebase than to anything else. At least the normal things... there's obviously still management issues at play.
So, essentially, and in truth, you are just uttering for the sake of it then?

I guessed as much 🤷‍♂️
 
You make lot's of statements about the COBRA engine, are you an ex-employee , or is it total surmise? What makes you think it will be easier in a different engine?

Just because engine / language a etc is better known than another engine / language does not mean the staff available will be better skilled, or it is a better language / engine, it just means it is easier to learn the basics.
I've worked for companies who use vb.net (I know !)- There are a wealth of vb.net coders out their but as it's an 'easy' language to code in, a vast majority of 'devs' are just script kiddies, who think they are experts, their IT skills are shocking (Often well educated on paper, but still shocking)

Good dev staff are not just coders, they are people who can break complex problems down into simpler steps, and then resolve those issues.

I'm not sure where this post is going, but the quoted post was such drivel, it got me annoyed.

TLDR; Quoted post is utter drivel.

if you're paying for good developers ...they'll be good in any framework you put them in. but the difference is in training up in that framework. You end up saving months of ramp up time getting familiar with a framework if they've already done that on their own.

on top of that, you spend less money keeping up with technology and ui/tools for that engine by not having to develop that in-house. meaning not only do you re-purpose those people for other things (or not need to hire them at all) but you also have the opportunity to hire even better developers for the some overall cost you used to invest if you wanted to not just save money because those people will likely have such experience and be pursuing jobs that are looking for it vs not.
 
Last edited:
download.jpg
 
Back
Top Bottom