These qualities are extremely counter to a lot of corporate jobs, where development is a cost that should be cut, there's never enough time for anything (because, business!), and the work is CRUD-driven.
These qualities are extremely counter to a lot of corporate jobs, where development is a cost that should be cut, there's never enough time for anything (because, business!), and the work is CRUD-driven.
The only place I knew which didn't have any business pressure was the old Bell Labs. That's because of the AT&T was a monopoly and was allow a profit of 7%. That meant any expense can instantly be justified because no matter what AT&T would earn 7%.
End of the day, engineering is about compromises and tradeoffs. It's applied science. It's about being practical and sometimes that means we need to compromise on "quality". That's what makes good engineering culture. A product that ships and makes money is infinitely better than a product that doesn't ship. So, I don't think it's right to assume that the corporate approach is incorrect. In fact, it is better simply because once you get business involved, a lot of the decisions become impersonal.
When I try to explain to loved ones that research is a dying career path (which I sadly invested in by getting a PhD), I get pep talks saying that I should be more optimistic :-p