Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If you have over the recommended number for one and not the other, they won't finish at the same time and one will over-develop causing the quality to drop.
I've been playing under the assumption that if you have an employee that has 10% code and 100% art and you assign them to "any role" they'll ruin the code, but if you assign them to "Artist" they won't affect it.
I could be wrong, but I haven't had anyone ruin code/art except for when assigning everyone to "any role" to rush a software to release.
I've noted (on 2D editors espeically) that using just the Founder whom is maxed out in all fields, that he will usually get the Art to "9.0-10" faster than the code when he's assigned to any role.
Soooo as soon as you get to that stage switch him to "programmer" only and he will then stop adding to the art causing the quality to drop.
Ever heard the term Over engineered? :)
https://en.wikipedia.org/wiki/Overengineering
Note down when it gets to around 6.5/10 on a peer review, that's when you'll need to be keeping a better eye on it if you're assigning the recommended amount. For example, when developing an AntiVirus with all the features, submit a peer review around 600k lines of code - since that's when it starts to border on 6/10 with the recommended staff.
But that's "Good" anyway, so you could probably just promote it there if you're rushing.