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
Employees with high specialization skills will have a bigger impact on quality as they can guide the lower skilled employees. Quality will decrease faster than it will increase, if possible. Leaving low skilled employees to work on a project on their own will have devastating consequences for the products quality, as no one will be there to help them. The design phase controls the starting quality of each specialization, among other things, so a good design will have a bigger chance of leading to a perfect quality end product.
I don't think this is like real life in that regard. You do not seem to lose skill as you age. There probably should be some loss of skill that you can make up with extra coursework. More than 95% of what I programmed was in BASIC (gasp). The technology was ancient but it was in place.
If you have experience there is a lot of code you can reuse in later projects as you do not have to rediscover the wheel each time.