Hacker News new | past | comments | ask | show | jobs | submit login

To be fair to those programmers, I've seen the same thing (or similar) in the US. It wasn't intentional bugs, but intentional delays in addressing them. That is, they sandbagged. They knew the fixes but didn't apply them so that they could hit monthly/quarterly/whatever targets. Or they knew they could knock out 100 features in a week, but that one feature would take 3 months. They'd mete out those 100 easy features over the three months so that they didn't appear stalled (they weren't, but management couldn't tell the difference between a stall and a hard problem).



Ok, another example: out famous "Cotton Scandal": http://shorturl.at/fzLPU

For more than 10 years thousands of party members from soviet republic of Uzbekistan were sending fake data to Moscow (this included corruption on many levels across the country) about production of cotton. Everyone was involved, from top to bottom, I don't see how creation of any network would help with that. In fact programmers across USSR were putting tools into the software for state companies to produce "fixed" results for central planning committee. And in central planning committee they were also corrupt :) (my relative worked there in 80s and I know how it was organized on basic level).




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: