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
It happens: Coders don't always perfrom due diligence (although not a Steam coder, I am a coder—a properly-trained one, unlike some employed by not only Steam, but many other sompanies). Step one is to diagram / flowchart code changes. Step to is to write pseudocode. Step three is to write actual high-level language code. Step four is where they fall down on their faces—test the code, which involves error-checking for bad input. I don't care HOW smart a coder you think you are—mistakes get made, and if you don't adequately TEST your code (compile and run it), it's gonna bite you on the "ash."
So, some lazy dipsquat's screwup was fixed by some other guy who actually did his job the way he was PAID to. Problem solved.