Unfortunately, the company I work for doesn't prioritize it much in practice: I've been working with them for 3.5 years now and the general feeling I get from folks at the top of the business is "good enough to work is good enough to ship." That said, most of the engineers I work with place a high value on code quality, since they are the ones that will have to understand and maintain it!
The biggest obstacle to code quality in my experience seems to be getting top-down support for spending more time/effort/resources on long-term success over short-term gains. I've been lucky to have had several good product managers who understand the impact code health and quality can have on their developers and, thus, the business. They have been instrumental at ensuring more project resources (time, budget, etc.) are allocated during design and development, which gives us engineers some more "room to breathe" and make better decisions.
support for spending more time/effort/resources on long-term success over short-term gains
Obviously, prioritizing short-term gains is sometimes necessary when running a business, especially if it is struggling. But I don't think it should be the default way to grow the business.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Unfortunately, the company I work for doesn't prioritize it much in practice: I've been working with them for 3.5 years now and the general feeling I get from folks at the top of the business is "good enough to work is good enough to ship." That said, most of the engineers I work with place a high value on code quality, since they are the ones that will have to understand and maintain it!
The biggest obstacle to code quality in my experience seems to be getting top-down support for spending more time/effort/resources on long-term success over short-term gains. I've been lucky to have had several good product managers who understand the impact code health and quality can have on their developers and, thus, the business. They have been instrumental at ensuring more project resources (time, budget, etc.) are allocated during design and development, which gives us engineers some more "room to breathe" and make better decisions.
Obviously, prioritizing short-term gains is sometimes necessary when running a business, especially if it is struggling. But I don't think it should be the default way to grow the business.