I agree with pretty much you said. I'm pretty new to the tech scene and it's just mind-blowing. I previously worked in the Mech Engineering industry and it's co

I agree with pretty much you said. I'm pretty new to the tech scene and it's just mind-blowing. I previously worked in the Mech Engineering industry and it's completely different. Coworkers are respectful and care about each other. Management does their best to listen to staff. Trying to basically foster a proper community. (Albeit, the salaries was way way lower.) > I'll be gone in a year, so why bother writing software that's maintainable? It won't be my problem. I would say that's why it's so important to have a core of competent technical employeers. One thing that is so underrated is company culture. If your technical managers or supervisors enforce stricter code quality, naturally everyone will follow on. Culture trickles down not up. The result you're seeing is from the effects of bad management or bad technical leadership. >Also, as long as customers (including B2B customers) are happy with dreck, then dreck, they get. Why bother putting in the considerable extra cost for Quality, when the suc- um, customers, will be happy with garbage? That's the thing. No customer likes garbage. Garbage here defined as buggy, slow or unusable product. They make do either because there's no other alternatives and/or this product meets their needs or is the market leader. However, there is still always a tradeoff between quality and time to market. It's impossible to get perfection and sometimes good enough is well... good enough.