> Government work is the worst example for quality. A monopoly without accountability having terrible practices doesn't surprise me. Exactly, the rules here ar

> Government work is the worst example for quality. A monopoly without accountability having terrible practices doesn't surprise me. Exactly, the rules here are different and there is monopoly involved. Accountability is dispersed. However, if you freck up here and it shows, you are in the news tomorrow. Good luck finding job after that. On company level, you can be banned for years in entire gov sector. The big problem with that stance is however, that government usually doesn't do that work, it typically outsources to private companies that work on behalf of mega corps like Oracle, IMB etc. And they produce that "worst example of quality". So, its not about the type of company its much more complicated. > In all the private companies I worked either software was maintained or the feature wasn't in use anymore or the entire engineering team was about to be fired or the company itself had 2 months of life. I am sure this is not the norm either. You say it like there is some kind of sensor telling you when "feature wasn't in use anymore" - for some domains it can be easy, for majority its not however. Its understandable that people minimize the complexity of things involved here but that doesn't reflect reality. > I agree on your point regarding security, closing every vulnerability is impossible or not economically sound for many realities. Indeed. People act here like I said 0 security but I didn't - every professional worth its salt should do common "best practices", but going more then that needs serious thought, budget, planning etc. and it all depends on type of thing you do.